Node Tracks - Revision history

Markdayel at 03:17, 6 May 2009

2009-05-06T03:17:34Z

Markdayel at 21:01, 5 May 2009

2009-05-05T21:01:16Z

Markdayel at 00:23, 20 April 2009

2009-04-20T00:23:52Z

Markdayel at 23:33, 17 April 2009

2009-04-17T23:33:39Z

Markdayel at 23:31, 17 April 2009

2009-04-17T23:31:56Z

Markdayel at 21:46, 11 April 2009

2009-04-11T21:46:52Z

Markdayel at 03:00, 11 April 2009

2009-04-11T03:00:49Z

Markdayel at 02:38, 11 April 2009

2009-04-11T02:38:45Z

Markdayel at 02:36, 11 April 2009

2009-04-11T02:36:41Z

Markdayel at 02:15, 11 April 2009

2009-04-11T02:15:00Z

@@ Line 39: / Line 39: @@
 If you want to restrict the choice of nodes to the symmetry breaking plane, set
-  NODE_TRACK_SELECT_Z_RANGE   2.5
+  NODE_TRACK_SELECT_Z_RANGE   1.5
 which restricts the nodes selected to +/- this distance from the bead center in the z direction

@@ Line 25: / Line 25: @@
   comet post 300:500
 would track nodes up to frame 500.  This creates new node tracks in a file <code>nodetracks.txt</code>, but ''only if this file doesn't already exist'' otherwise it just loads the existing tracks, so make sure to delete or rename this file if you want to calculate new tracks.  The node range given to the <code>comet post</code> command 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

@@ Line 1: / Line 1: @@
 ==Following the network motion==
-You can use node tracks to see where the network goes.  Turn on network tracks with BMP_TRACKS setting in cometparams.ini.  e.g.
+You can use node tracks to see where the network goes.  Turn on network tracks with the BMP_TRACKS setting in cometparams.ini.  e.g.
   BMP_TRACKS true        # turns on node tracking
   TRACK_MIN_RANGE 300.0  # select nodes created between this time...
@@ Line 24: / Line 24: @@
 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 creates new node tracks in a file <code>nodetracks.txt</code>, but ''only if this file doesn't already exist'' otherwise it just loads the existing tracks, so make sure to delete or rename this file if you want to calculate new tracks.  The node range given to the <code>comet post</code> command 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.
-−
-Distances between selected nodes are output in the file 'nodedistances.txt'.  Running the script 'comet_process_distances' processes these into a comma delimited (csv) file which can be loaded into Excel etc. to easily plot the distances as they change over time.
 Once this is done the tracks will be rendered onto the bitmaps, and can be viewed in 3d by setting
@@ Line 33: / Line 31: @@
   comet view 400:400
-Measures will be shown as lines, with associated numbers.  Depending on the purpose, you may want to exclude certain lines (e.g. if measuring the expansion and contraction of the shell, you probably want to remove any pairs that span the crack.  To remove particular measures, find the numbers using the 3D view, then set the track numbers to remove in the 'comet_remove_nodetracks' script, make a backup of the nodedistances.txt file and run the script.  This will edit the nodedistances.txt file and remove those measurements.  Note the numbering changes when you do this, so re-check with comet view nnn:nnn and re-run with the new numbers if you need to remove more.
+Measures will be shown as lines, with associated numbers.  Depending on the purpose, you may want to exclude certain lines (e.g. if measuring the expansion and contraction of the shell, you probably want to remove any pairs that span the crack.  To remove particular measures, find the numbers using the 3D view, then set the track numbers to remove in the 'comet_remove_nodetracks' script.  This will edit the nodetracks.txt and nodedistances.txt files and remove those measurements.  Note the numbering changes when you do this, so re-check with comet view nnn:nnn and re-run with the new numbers if you need to remove more.  Running the script 'comet_process_distances' processes these into comma delimited (csv) files for raw, normalized and averaged summaries which can be loaded into Gnuplot, Excel etc. to easily plot the distances as they change over time.
 ==Other Parameters==

@@ Line 24: / Line 24: @@
 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 creates new node tracks in a file <code>nodetracks.txt</code>, but 'only if this file doesn't already exist' otherwise it just loads the existing tracks, so make sure to delete or rename this file if you want to calculate new tracks.  The node range given to the <code>comet post</code> command 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.
+would track nodes up to frame 500.  This creates new node tracks in a file <code>nodetracks.txt</code>, but ''only if this file doesn't already exist'' otherwise it just loads the existing tracks, so make sure to delete or rename this file if you want to calculate new tracks.  The node range given to the <code>comet post</code> command 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.
 Distances between selected nodes are output in the file 'nodedistances.txt'.  Running the script 'comet_process_distances' processes these into a comma delimited (csv) file which can be loaded into Excel etc. to easily plot the distances as they change over time.

@@ Line 14: / Line 14: @@
 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
+  TRACKS_LENGTHS  true   # if false then tracks node movement, 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
@@ Line 24: / Line 24: @@
 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.
+would track nodes up to frame 500.  This creates new node tracks in a file <code>nodetracks.txt</code>, but 'only if this file doesn't already exist' otherwise it just loads the existing tracks, so make sure to delete or rename this file if you want to calculate new tracks.  The node range given to the <code>comet post</code> command 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.
 Distances between selected nodes are output in the file 'nodedistances.txt'.  Running the script 'comet_process_distances' processes these into a comma delimited (csv) file which can be loaded into Excel etc. to easily plot the distances as they change over time.

← Older revision		Revision as of 21:46, 11 April 2009
Line 39:		Line 39:
	If you want to restrict the choice of nodes to the symmetry breaking plane, set		If you want to restrict the choice of nodes to the symmetry breaking plane, set

−	~~SELECT_NODES_TO_TRACK_IN_2D true~~	+	NODE_TRACK_SELECT_Z_RANGE 2.5
		+
		+	which restricts the nodes selected to +/- this distance from the bead center in the z direction

← Older revision		Revision as of 03:00, 11 April 2009
Line 8:		Line 8:
	MAX_NODES_TO_TRACK 30 # how many nodes to track		MAX_NODES_TO_TRACK 30 # how many nodes to track

−	Set BMP_TRACKS to true, and set TRACK_MIN_RANGE and TRACK_MAX_RANGE to bracket the time range for the creation of nodes you want tracked. The program will look for a set of MAX_NODES_TO_TRACK nodes within those created in this time bracket. ~~You~~ probably also want to set BMP_FIX_BEAD_MOVEMENT to true so that the bitmap tracks aren't upset by the translation of the image.	+	Set BMP_TRACKS to true, and set TRACK_MIN_RANGE and TRACK_MAX_RANGE to bracket the time range for the creation of nodes you want tracked. The program will look for a set of MAX_NODES_TO_TRACK nodes within those created in this time bracket. If you want 2D tracks on the bitmaps, you probably also want to set BMP_FIX_BEAD_MOVEMENT to true so that the bitmap tracks aren't upset by the translation of the image.

← Older revision		Revision as of 02:36, 11 April 2009
Line 34:		Line 34:

	Measures will be shown as lines, with associated numbers. Depending on the purpose, you may want to exclude certain lines (e.g. if measuring the expansion and contraction of the shell, you probably want to remove any pairs that span the crack. To remove particular measures, find the numbers using the 3D view, then set the track numbers to remove in the 'comet_remove_nodetracks' script, make a backup of the nodedistances.txt file and run the script. This will edit the nodedistances.txt file and remove those measurements. Note the numbering changes when you do this, so re-check with comet view nnn:nnn and re-run with the new numbers if you need to remove more.		Measures will be shown as lines, with associated numbers. Depending on the purpose, you may want to exclude certain lines (e.g. if measuring the expansion and contraction of the shell, you probably want to remove any pairs that span the crack. To remove particular measures, find the numbers using the 3D view, then set the track numbers to remove in the 'comet_remove_nodetracks' script, make a backup of the nodedistances.txt file and run the script. This will edit the nodedistances.txt file and remove those measurements. Note the numbering changes when you do this, so re-check with comet view nnn:nnn and re-run with the new numbers if you need to remove more.
		+
		+	==Other Parameters===
		+
		+	set
		+
		+	SELECT_NODES_TO_TRACK_IN_2D true
		+
		+	if you want to restrict the choice of nodes to the symmetry breaking plane