Bug #15034

Event failure in MCC 0.5 (Preliminary MCC)

Added by Dominic Brailsford over 3 years ago. Updated over 2 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
First Occurred:
Occurs In:


There was exactly one job failure in the entirety of MCC 0.5.
This failure happened in the reconstruction stage of the prodsingle_gamma_100-2250MeV_fixposcontained_fixangle sample.
The job was held after passing its maximum time, suggesting an event got stuck.

As the job ran out of time, nothing was copied back to dcache so there is no output to check. However, the input detsim file is available, which is located here:


The sbndcode version is v05_12_01, however the development head was used for the MCC as there was no tag available. The tar file containing the sbndcode install passed to each job is located here:

Michelle, I'm not 100% sure if it is even your job to look at this but last I knew you were acting reconstruction convenor.
I guess this issue submission sets the precedent... sorry everyone!


#1 Updated by Dominic Brailsford over 3 years ago

  • Subject changed from Event failure in the MCC 0.5 (Preliminary MCC) to Event failure in MCC 0.5 (Preliminary MCC)

#2 Updated by Gianluca Petrillo over 2 years ago

Is this ticket obsolete by now?

#3 Updated by Dominic Brailsford over 2 years ago

  • Status changed from New to Closed

Gianluca Petrillo wrote:

Is this ticket obsolete by now?

I think so.
Given that it was a single issue in the preliminary MCP, the software version was v05_12_01 and that the ticket is basically a year old, I don't think it's worth dwelling on the matter.
I'm closing this ticket. We can reopen it later if we want to (we won't).

Also available in: Atom PDF