I have another question. When calculating the cross-section of 225Ra and 223Ra produced by ion bombardment of a uranium target, I noticed a sudden change in the data at 150 MeV/n, which is clearly due to the model transition. Therefore, below 150 MeV/n, I would like to use the RQMD model entirely to compare the differences with the BME model.
I added PHYSICS cards(QMDTJRES and RQMD) according to the manual, but it doesn’t seem to work. Could you tell me how to use the RQMD model entirely? Thank you!!
According to the manual, to this purpose you should use the PHYSICS card with SDUM= DPMTHRES and lower the model switch energy in WHAT(3) (minimum acceptable value is 0.050 GeV/n). Moreover, the BME-RQMD smearing interval plays also a role and can be adjusted through another PHYSICS card with SDUM= QMDTHRES by means of WHAT(6).
By default, BME and RQMD overlap over the 100 to 150 MeV/n energy range, being the switch energy 125 MeV/n (where they are alternatively invoked with equal probability) and the smearing of ±25 MeV/n.
Thank you for your detailed response.
1." The PHYSICS card with SDUM= DPMTHRES and lower the model switch energy in WHAT(3) (minimum acceptable value is 0.050 GeV/n)". Does this mean that ion interactions below 50 MeV/n can only use BME?
2. I added the physics cards as you suggested, and the results seem to be fine. However, I encountered a new issue during parallel computation. When I submit 20 spawned jobs, each with 5 cycles, only fewer than 5 end up with results, while the others terminate. The error message is "Abort called from start reason wrong energy Run stopped!"What is causing this?
Here are my input card and error file.
With SDUM= DPMTHRES you will still have an overlap with the default smearing of 25 MeV/n, so both models have a chance to be activated (but this leads to your error, see next point).
I see that you put the smearing to be 0 via SDUM= QMDTHRES which actually will still leave the default value of 25 MeV/n, which sets energy for RQMD to be below 50 MeV/n (not allowed by FLUKA) and leads to this error message. To make it work, set WHAT(6) to -1, which will set smearing to 0.
