Problem 1165 - G4BinaryLightIonReaction no final state
Summary: G4BinaryLightIonReaction no final state
Status: RESOLVED FIXED
Alias: None
Product: Geant4
Classification: Unclassified
Component: processes/hadronic/models/binary_cascade (show other problems)
Version: 9.3
Hardware: All Mac OS X
: P5 normal
Assignee: Gunter.Folger
URL:
Depends on:
Blocks:
 
Reported: 2011-01-27 13:27 CET by Ricol
Modified: 2012-11-21 15:41 CET (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description Ricol 2011-01-27 13:27:49 CET
Hi,
I received this error message enough times to think I should submit it as a bug report as required :


G4BinaryLightIonReaction no final state for:
 Primary 0x11292f280, (A,Z)=(2,1) , kinetic energy 5955.44
 Target nucleus (A,Z)=(12,6
 if frequent, please submit above information as bug report


The program doesnt crash so I dont really see this as a big problem, but who knows ...

I use QGSP_BIC physics list adding extra physics through

theSihverCrossSection = new G4IonsSihverCrossSection();

G4int nParticles = 5;

G4String processName[ = {"dInelastic","tInelastic","He3Inelastic","alphaInelastic","ionInelastic"};

G4String particleName[]={"deuteron","triton","He3","alpha","GenericIon"};

G4double Emin[]={1.*TeV,1.*TeV,20.*GeV,1.*TeV,20.*GeV};

G4ProcessTable* processTable=G4ProcessTable::GetProcessTable();

for (G4int i=0; i< nParticles; i++) {
 G4BinaryLightIonReaction *theGenIonCascade = new G4BinaryLightIonReaction;
 G4HadronInelasticProcess* hadi =  (G4HadronInelasticProcess*)processTable->FindProcess(processName[i],particleName[i]);
 if (hadi != 0) {
  hadi->AddDataSet(theSihverCrossSection);
  theGenIonCascade->SetMinEnergy(Emin[i] - MeV);
  theGenIonCascade->SetMaxEnergy(100*TeV);
  hadi->RegisterMe(theGenIonCascade);
 }
}


Let me know if it a known problem (I couldnt find any reference to it in the other bugs) or if I do something wrong (or if I should not worry about it).

Cheers

Jean-stephane Ricol
Comment 1 Gunter.Folger 2011-03-18 15:18:32 CET
Thanks for this report. It is not a bug, just a warning.
I will try to reproduce this, and see why this happens.
Comment 2 Gunter.Folger 2012-11-21 15:41:53 CET
This was difficult due to a confusing error message, guiding me to a wrong cause. 

I fixed the problem causing this message, fix will be in release Geant4.9.6.