|Message: Re: Problem with rdecay02 example||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hi, I am not a very experienced user, but I had the same error when trying to simulate a radioactive decay of Na22 in GATE (a toolkit for medical physics simulations based on Geant4). I don't think this is the best solution, but I managed to fix the issue like this:
In your geant4 install folder you should have this file:
The error is thrown by that file, after looking for the cross section in the database, in these lines:
190 G4cout << "G4CrossSectionDataStore::GetCrossSection ERROR: " 191 << " no isotope cross section found" 192 << G4endl; 193 G4cout << " for " << part->GetDefinition()->GetParticleName() 194 << " off Element " << elm->GetName() 195 << " in " << mat->GetName() 196 << " Z= " << Z << " A= " << A 197 << " E(MeV)= " << part->GetKineticEnergy()/MeV << G4endl; 198 throw G4HadronicException(__FILE__, __LINE__, 199 " no applicable data set found for the isotope"); 200 return 0.0; 201 //return dataSetList[idx]->ComputeCrossSection(part, elm, mat); 202 }
As I understand it, lines 190-200 just give information about the error. What I did was comment all those lines and uncomment line 201 which, I think, then computes a new Cross Section even if it isn't in the database.
Someone more experienced would be more suitable to give a proper answer, but for now this did the trick for my simulation. Hope this is helpful to you!