Question about counting rate in a detector

AI Thread Summary
The discussion focuses on simulating a Cesium-137 source with specific parameters in a detector context. It clarifies that the "T" card in the simulation is primarily for defining time intervals for tallying events rather than for determining how long it will take for the detector to count a specific number of particles. Users are advised to use the tally result (F4 multiplied by activity) to calculate the flux rate in Bq/cm².s for time determination. The importance of understanding the detector's response to different energies is emphasized, particularly if using a scintillator or germanium crystal, suggesting the use of an F8 tally for accurate results. Overall, the discussion highlights the complexities of timing and counting in detector simulations.
Alexander Camargo
Messages
33
Reaction score
10
Hello everyone. I am simulating a Cesium-137 source with an energy of 0.662 MeV and an activity of 225 mCi. When I use the "T: tally time bins" card, for example:

F24:P 1
E24 20
T24 0 1000 25I 3600 196I 200600

I understand that I am asking the program to give me the average flux in this cell, for an energy of 20 MeV, over the defined time intervals (Tremor). My question is: can this time be used to determine how long it will take for my detector to count a certain number of particles? Or is this time on the T card only used for the simulation time?

Would it make more sense to use the tally result (F4 * activity) to obtain the flux rate (Bq/cm².s) to determine the time?
 
Engineering news on Phys.org
MCNP doesn't really understand macroscopic time in a simulation. It keeps track of flight time, and the BURN card understands MW.days but I don't think there is any way of telling it the activity of a source. Most tally results are per source particle, so multiplying by the source activity afterwards is the normal process (and you can multiply by arbitrary values so you can force the program to do the maths for you if you want). T card is in shakes, so it's counting time between the emission of the particle and the event being tallied. This is really useful if the simulation is of a time of flight spectrometer, for example.

E24 20, btw, would be a single bin including everything from 0 to 20 MeV.

F4 can work but then you need to determine flux response for different energies if you want to know what a detector would do. I'm assuming that is the goal because it's in the title of the thread. If your detector is a scintillator, or a germanium crystal, I would put that in the simulation and use an F8 tally. I don't know if F8s are per volume or not by default so I would be sure to check that. If this is a scintillator without an MCA you can still use energy bins to simulate the threshold setting.
 
  • Like
Likes Salman Khan, Alexander Camargo and Astronuc
Hello everyone, I am currently working on a burnup calculation for a fuel assembly with repeated geometric structures using MCNP6. I have defined two materials (Material 1 and Material 2) which are actually the same material but located in different positions. However, after running the calculation with the BURN card, I am encountering an issue where all burnup information(power fraction(Initial input is 1,but output file is 0), burnup, mass, etc.) for Material 2 is zero, while Material 1...
Hi everyone, I'm a complete beginner with MCNP and trying to learn how to perform burnup calculations. Right now, I'm feeling a bit lost and not sure where to start. I found the OECD-NEA Burnup Credit Calculational Criticality Benchmark (Phase I-B) and was wondering if anyone has worked through this specific benchmark using MCNP6? If so, would you be willing to share your MCNP input file for it? Seeing an actual working example would be incredibly helpful for my learning. I'd be really...
Back
Top