Much of the control and bookkeeping advantages are built-in by KUIP, discussed above. But there are also DASH commands that allow you to set up and monitor your analysis.
Using RUNLIST/INCLUDE or RUNLIST/EXCLUDE, you can set up a job to skip or jump to certain runs, events or blocks of events. You can also use the SKIP command to skip a certain number of events, without regard to the exact run and event numbers. One possible use is to make up a KUIP macro file, GOODRUNS.KUMAC, that picks ``good runs'' out of a directory of all runs, such as this exerpt shows:
INPUT WSGS03$DKA100:[MACRODATA.DST]RUN005530.DSTE ; ANA
INPUT WSGS03$DKA100:[MACRODATA.DST]RUN005531.DSTE ; ANA
INPUT WSGS03$DKA100:[MACRODATA.DST]RUN005532.DSTE ; ANA
Note that we have taken advantage of KUIP's feature allowing multiple commands to be put on one line if separated by a semi-colon.
When running over a large number of events, it is reassuring to have some sort of notification at regular intervals. The COUNT commands give you many ways to accomplish this. See the examples in the command reference 8 for suggestions. In addition, the STATUS command will report how many events were analyzed at each module in the analysis path (as well as giving other descriptive information about the modules linked and in the path).