Page History

...

• G4 propagator error. If recon dies complaining about g4propagator, we can't fix it. If this happens, email Heather (heather625{at}gmail) and Anders (borgland{at}slac) (and possibly Warren (focke{at}slac) and Maria Elena (monzani{at}slac)). Include a link to the log file, which will tell them where the core file is.
• Overlapping chunks. If findChunks complains about overlapping chunks, tell Bryson; if trending merges complain, tell Bryson and datamonlist@glast2.Stanford.EDU. Rollback won't help.
• Too few events in the run - can lead to an FT2 failure. Email Andrea (tramacer{at}slac) regarding any problems with FT2.
• Deliveries arriving too closely will mangle the display. The underlying processes are fine, but email obsproblist{at}glast2.stanford.edu, Jim (jchiang{at}slac) or Bryson (blee{at}slac) to fix the display.

...

What to do in case of permanent failures: contact the appropriate people above, if you are sure you know what happened. Otherwise, page Warren and/or Maria Elena (see L1 shift schedule). If there is another part of the run waiting, the run lock (see below) will have to be removed by hand; page unless you're really sure of what you're doing.

Other failures

This is a comprised list of failures that don't really fit into the other major three ones

• Too few events in the run, or gaps - can lead to too few events in the magic7 file FT2 failure. Try to copy the /afs/slac/g/glast/ground/PipelineStaging6/halfPipe/XXX/magic7_XXX.txt (where XXX is the run number) to /afs/slac/g/glast/ground/PipelineStaging6/YYY/magic7_YYY.txt (where YYY is the run where fakeFT2 failed ... remember to change XXX to YYY on the magic7 file name). Then rollback fakeFT2. If this fails, email Andrea (tramacer{at}slac) for additional information regarding problems with FT2.

Everything to know about the Rollback

...