== How to rerun stuff for Mops ==

Mops likes their data to appear on their datastore, and they like quads to be reprocessed.  This is Heather's list of steps:

1. queue with chiptool.  defaults usually work fine, but use your judgement here.

2. queue the quads. They preferably like 1 - 2 and 3 - 4.  You can trick out difftool to do it in 2 commands:

{{{
difftool -definewarpwarp -input_comment '%visit 2' -template_comment '%visit 1' -input_label 'czw.mopstest.rerun' -template_label 'czw.mopstest.rerun' -dbname gpc1 -set_workdir neb://@HOST@.0/czw/mopstest.rerun -set_label 'czw.mopstest.rerun'
	
difftool -definewarpwarp -input_comment '%visit 4' -template_comment '%visit 3' -input_label 'czw.mopstest.rerun' -template_label 'czw.mopstest.rerun' -dbname gpc1 -set_workdir neb://@HOST@.0/czw/mopstest.rerun -set_label 'czw.mopstest.rerun'

}}}

3. publishing- they like stuff to be put in client_id 14, ie, ipp_mops_dev
{{{
pubtool -dbname gpc1 -set_label czw.mopstest.rerun -client_id 14 -definerun -label czw.mopstest.rerun
}}}
and add that label to publishing pantasks. note that if you omit -label it queues everything to be published. do not do that.

That should be it!