Page History

...

From the front end it's trivial, but from the command line it's a bit more tricky:
/afs/slac.stanford.edu/u/gl/glast/pipeline-II/prod/pipeline \-m PROD rollbackStream \--minimum 'L1Proc\[90117001\]/doRun\[253889937\]' 

Remember to escape the square brackets if you are in tcsh.

...

• From the glast-ground page, click "Logging" (about 1/3 of the way down left side)
• Click "Selection" (upper right)
• Click "More Selections" (lower right)
• In the "Select Program" field, enter "mergeStuff.py"
• In the "Select Target" field, enter the run number.
• Click "Table" (upper right)
• Now you should have a list of complaining about not being able to find input files. If any of the complaining merges are downstream of a failed process, you can ignore them. This is usually the case. But if they are not downstream from a failure, it means there was a disk read error while setting up the merge. Look at the logfile for that merge, it will say what files are missing. If they are really there, the merge can be rolled back and will probably work the second time. If they are not there, there's a bigger problem, and this should be considered a "permanent failure".

...