Skipping And Waiting

It is possible to instruct a trajectory to intentionally skip a point, skip the count portion of a point or to perform arbitrary waits. This is controlled by setting various variables in the trajectory namespace:

• skipPoint - A boolean value, which if true, at the beginning of a point, will cause the entire motion and count to be skipped. Additionally, nothing will be written to the data file for this point.
• skipCount - A boolean value, which if true, at the beginning of a count, will cause the entire count to be skipped. Additionally, nothing will be written to the data file for this point.
• waitPoint - A double value, which if non-zero, will cause a wait between the point's movement and count. The value of this variable is the time to wait, in seconds.

These variables can be modified, like any other value, during a trajectory. However, before every trajectory they are initialized to a constant starting value representing the default behavior people normally expect (ie. you don't skip any points and no wait occurs). As an example, you could add the following loop to a trajectory to move a motor through a range but only count at every other point:

Range: motorX goes from 20 to 40 in steps of 1

Expression: skipCount: (motorX%2)==1