-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in G4 and INCL++ cascades due to wrong physics #305
Comments
INCL++ shows the same behaviour. Output before adding O11:
after adding oxigen 11:
|
This is exotic event and exotic final state. Is it just luck? see https://www.nndc.bnl.gov/nudat3/. O12 has very short halflife. O11 is proposed but not seen. It would be 8p and 3n, very exotic. I think you did right thing. We are using other people's code in new situation. Do we need an error condition for such an event? |
Hi Steve, as mentioned above the event is wrong because O11 should not be there. Also notice that the same error is obtained using both INCL and G4 (different codes). I am investigating this further for now, I want to understand how often these kind of events occur. For now I have some questions unsolved:
|
INCL:
|
Hi Julia, My opinion is that if we add some isotopes in genie_pdg_table.txt we should do it in consistent way, namely, check whether that happen with other nuclei, and if yes, add corresponding isotopes for them too. |
Hi all, I'm chipping in as I think things are getting confused. The problem is not that O11 is created. We know it is a valid isotope that it is documented in nuclide tables. And of course if we think we need, we can add it to the table. Indeed it is what she did in order to generate a complete file that we can analise. The problem is that in events like the one Julia reported, simply for pure charge and baryon conservation, that Oxigen should be a Nitrogen. I hope to have a discussion about this on the next Core developer meeting (14 August) assuming the necessary players will be able to connect, despite summer and possible vacations. If not, please send some notes, either here or with an email. |
even 196 out of 400k still seems like a lot to me. Important question - does INCL or GENIE calculate final state? As you say, event printout is apparently wrong. I see final nucleus is C12 missing a neutron which is C11. Nothing there says it should be O11. |
According to data, O11 has not been seen! Surely, someone could calculate its mass so we can include in our tables if needed. |
Richie Diurba also recovered the same error running |
I was generating events for studies to tune hA2018 and develop systematics for it. This was a replication of the studies documented here: https://github.com/GENIE-MC/Generator/blob/master/src/Physics/HadronTransport/HAIntranuke2018.cxx#L739. I was generating HINCL and hG4BertCasc events for piplus and piminus. I then would get errors for carbon and iron. The carbon error was for the same isotope above (O11) and this command gives me an error for Rhenium-199:
|
@rdiurba can you to find a way to put the whole event on here? I think it's clear that the problem is not the missing nucleus in our table (that an always be added if necessary), but rather the wrong accounting that the external code does when more than one particle is propagated. |
Unfortunately, it always exits ungracefully and spits out an empty ghep tree. Here is the printout though. Let me know if you meant something different.
|
in order to have the full print, Julia locally added the missing isotope in order for the event and the file to be completed. Then, she printed the full event using gevdump. |
Ok, thanks. I am running this as a dunegpvm ups product and have never actually built with Geant4 or INCL++. If you can give me a couple days, I will try to do the same. |
You can use this script to build GENIE locally using G4: Simply do: from the gpvms |
Using:
|
THe fix is in #360 |
I am running e-+C12 events using G18_10d (G4 FSI). The event generation crashes due to an unexpected isotope in the final state.
The crash observed is the following:
The event 3568 is not successfully generated due to this error:
You are attempting to insert particle with PDG code = 1000080110 into the event record.
. As a consequence, you cannot see the event record (notice the one you can see is from the previous event).You can recover the crash with the following command:
The trick we followed to debug this further is to add the Oxigen 11 isotope in the corresponding GENIE file:
$GENIE/data/evgen/catalogues/pdg/genie_pdg_table.txt
. In that way we can recover the event record for this specific event:Issues with the event:
The text was updated successfully, but these errors were encountered: