Routine creates subTree for each tracking object and removes tracking objects on process which do not include any elements to track
Identify, how many and which elements exist on my local process and are requested from the trackers Empty tracking entities are removed, so the track(:) might be re-allocated
Type | Intent | Optional | Attributes | Name | ||
---|---|---|---|---|---|---|
type(tem_tracking_type), | intent(inout) | :: | me | tracking entities |
||
type(treelmesh_type), | intent(in) | :: | tree | Global mesh from which the elements are identified and then stored to sub-meshes inside the trackers |
||
type(tem_solveHead_type), | intent(in) | :: | solver | Global solver information |
||
type(tem_BC_prop_type), | intent(in) | :: | bc_prop | bc property that used to identify elements of certain BCs |
||
type(tem_stencilHeader_type), | intent(in), | optional | :: | stencil | stencil used to create subTree of boundary type |
|
character(len=labelLen), | intent(in), | optional | :: | prefix | Prefix for output filename Usually: solver%simName |
Type | Visibility | Attributes | Name | Initial | |||
---|---|---|---|---|---|---|---|
integer, | private | :: | iLog | ||||
integer, | private | :: | nActive | ||||
type(tem_tracking_instance_type), | private, | allocatable | :: | tempTrack(:) | |||
character(len=pathLen), | private | :: | prefix_loc | ||||
character(len=pathLen), | private | :: | basename |