Necessary Maintenance #18478

Names associated to pdg codes in Style.cxx (in lareventdisplay) are out of date?

Added by Tracy Usher almost 3 years ago. Updated over 2 years ago.

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


Estimated time:


It has been noted that the event display can give some interesting products in neutrino interactions in argon. For example:

      1    0       0      #nu_{#mu}    794    794     -1 primary
      1    1       1        ^{56}Fe      0      0     -1 primary
      1    4       4            #mu    328    239      0 primary
      1    8       8              p    686    224      6 primary
      1    9       9        #pi^{+}     50      8      7 primary
      1   10      10              p    319     52      7 primary

Where it seems rather odd to expected an iron nucleus to be associated with a neutrino interaction in argon (right?).
These names are implemented in the Style.cxx file which does not appear to have been updated in eons leading to the question as to whether there have been changes in pdg codes which may be causing this problem? Conjecture on my part...


#1 Updated by Lynn Garren almost 3 years ago

Have you checked the PDG Monte Carlo numbering scheme page?

#2 Updated by Tracy Usher almost 3 years ago

Yes, hence the question mark on the subject line. While it seems that 1000260560 is, by pdg definition, Fe, it was pointed out to me by the person reporting this that it seemed an odd product from this interaction. So that begs the question if the code is consistent with the generators. If the answer is "yes" then happy to close the topic.

#3 Updated by Robert Hatcher almost 3 years ago

Looking at lareventdisplay / EventDisplay / Style.cxx LatexName() I don't see how it could get things "wrong" in the mapping from PDG code to name (to the limited extent that it does translations). Ion/isotope naming hasn't changed in many, many years (long ago it was A,Z rather than Z,A).

Well, actually there is a way to go wrong with this, but only if it falls through to the default case of using the static buffer and generating a "X_{..pdg..}" and there are multiple call that trigger that in the same "write". But that doesn't seem to be the case here.

Perhaps, it would be better to look at the event itself in the MCTruth & Geant4 particle list structures to understand what is going on.
Are we sure that the volume that GENIE event generation was restricted to was in fact pure Argon and there wasn't the presence of other elements such as an APA frame or something made from Fe that the scatter could have occurred off of.

#4 Updated by Gianluca Petrillo almost 3 years ago

  • Description updated (diff)

Is this the norm, or do you get iron only rarely?
Maybe that is iron, if your detector geometry is ironic enough.
Also: is that GENIE that you are printing?

#5 Updated by Lynn Garren almost 3 years ago

  • Status changed from New to Feedback

Are you able to follow up Robert's recommendation to figure out where this problem occurs?

#6 Updated by Katherine Lato over 2 years ago

  • Assignee set to Tracy Usher

Also available in: Atom PDF