[Halld-offline] pythia-geant.map, back to basics

[Mark Ito]

Kei,

On 12/18/2013 11:53 AM, Kei Moriya wrote:
> I assume this proposed change affects the geantId code that you
> checked in?
This does not effect that change. Also note that geantId is a mis-nomer 
for the change checked in. That was appropriate for the previous 
abandoned approach.
> At the very least we can assume that the REST not stopping
> problem is solved.
Good news!
>
> In previous batch runs most of the failures I saw were from
> either REST getting stuck at one event or not finishing,
> which I assumed to be a database connection problem,
> but that seems to be gone.
A database connection problem would stop a job at the very beginning. It 
would also be obvious in the log file; there would be a complaint about 
getting some sort of constants.
>
> I can start analyzing the bggen events I currently have,
> or if there will be significant changes to the geantId
> due to the new changes, I can wait to generate/simulate
> a new batch.
I would wait for me to check in the new changes. Alternately you can use 
the revision of
pythia-geant.map attached to my last message, or check out the version 
from revision 3195.

   -- Mark

-- 
Mark M. Ito, Jefferson Lab, (757)269-5295, marki at jlab.org