Difference between revisions of "Node Tracks"
From CometWiki
m (Created page with 'You can use node tracks to see where the network goes. Turn network tracks with the following setting in cometparams.ini. e.g. BMP_TRACKS true # turns on node tracking ...') |
m |
||
Line 16: | Line 16: | ||
Node tracks are added separately after the initial calculation run, e.g. running | Node tracks are added separately after the initial calculation run, e.g. running | ||
comet post 300:500 | comet post 300:500 | ||
− | would track nodes up to frame 500. This range must include TRACK_MIN_RANGE, TRACK_MAX_RANGE and TRACK_MIN_RANGE2 and TRACK_MAX_RANGE2 if they are being used. Note: the program will automatically try to select nodes distributed evenly across the bead, but | + | would track nodes up to frame 500. This range must include TRACK_MIN_RANGE, TRACK_MAX_RANGE and TRACK_MIN_RANGE2 and TRACK_MAX_RANGE2 if they are being used. Note: the program will automatically try to select nodes distributed evenly across the bead, but needs enough nodes within the frame range given. |
+ | |||
Once this is done the tracks will be rendered onto the bitmaps, and can be viewed in 3d by setting | Once this is done the tracks will be rendered onto the bitmaps, and can be viewed in 3d by setting |
Revision as of 18:02, 10 April 2009
You can use node tracks to see where the network goes. Turn network tracks with the following setting in cometparams.ini. e.g.
BMP_TRACKS true # turns on node tracking TRACK_MIN_RANGE 300.0 # select nodes created between this time... TRACK_MAX_RANGE 305.0 # ...and this time (in frames) TRACKFRAMESTEP 5 # number of frames between each point in the track when plotted
In addition, node tracks can be used to measure stretching of the shell or tail:
TRACKS_LENGTHS false # if false then tracks nodes, if true then tracks pairs and measures the distances between them TRACK_TARGET_DIST 2.5 # tells code to select node pairs aiming for about this distance between them SECOND_SHELL false # if SECOND_SHELL is false, tracks circumferential lengths in one shell # if SECOND_SHELL is true, tracks radial lengths between two shells TRACK_MIN_RANGE2 10 # select nodes created between this time... TRACK_MAX_RANGE2 30 # ...and this time for the second shell
Node tracks are added separately after the initial calculation run, e.g. running
comet post 300:500
would track nodes up to frame 500. This range must include TRACK_MIN_RANGE, TRACK_MAX_RANGE and TRACK_MIN_RANGE2 and TRACK_MAX_RANGE2 if they are being used. Note: the program will automatically try to select nodes distributed evenly across the bead, but needs enough nodes within the frame range given.
Once this is done the tracks will be rendered onto the bitmaps, and can be viewed in 3d by setting
VIS_TRACKS true
then running
comet view 400:400