[Halld-offline] MC myid bug?

[Paul Mattione]

I see three very weird things when I print the DMCThrown objects on the first event of the rest_500001.hddm data challenge file to screen via hd_dump: 

 - I see a particle with myid = 0.  
 - I see two particles with the same myid (402), yet they come from different parent particles.  
 - I see two particles with a parentid (427) of a particle not listed in the output (no DMCThrown object corresponds to the particle they decayed from).  

The first two are problems because each particle should have a unique, non-zero "myid" so that the "parentid" points to the "myid" of the parent in a non-ambiguous way.  The third may not be a problem, but I'm not sure about it.  

Does anyone have time to look into hdgeant and see what is happening here?  Since this is data challenge REST data, this should be reproducible using the "500001" as the random seed in bggen.  Thanks.  

 - Paul