Dear community, I will be happy to get your advice on the following problem: I am simulating a 12MeV proton beam on a Beryllium target for neutron generation. The target is surrounded by a vacuum chamber, which is surrounded by polyethylene and lead shielding. From the shielding, I have 3 pipes th…

Dear Rubi, In your case — as Francesco mentioned — there is no real geometry error in your model, the issue is related to numerical precision, as a particle moving tangentially with the beampipe wall. Since FLUKA can recover from this kind of error, it should not slow down your simulation though. …

Dear Rubi, if you get the GEOFAR error, you usually have a (tiny) geometry error. Try finding it as it is shown on slide 28 of this lecture: 17_Standard_output_Common_errors_2024_INTA.pdf When you change the physics of the simulation then the generated particle…

I’d like to underline that actually the problem does not necessarily imply a factual error in the geometry definition by the user. These error messages are not lethal (unless the simulations stops due to their excess). Even with a formally correct geometry, the tracking algorithm can meet precisio…

David Thank you very much for your answer. I checked the geometry in all possible ways (like in the slides) but did not find the problem. The run does not stop but is slower because of the problem. So, I will be happy to avoid these errors. How can I prevent it?

Thank you very much for the help! So, to define the beam correctly, I have to add the BEAMAXES card, right? I changed this setting: [image] to this [image] Is that correct?

Dear Rubi, yes, this looks correct. You can see the beam direction in the Geometry window by selecting the BEAM under Objects in the list on the left. Cheers, David

FLUKA User Forum

Geofar error + biasing

Running and Runtime Errors

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled