Error in Calculation of absolute Flux (Source_flux) ???
Dr. Georg Artus
Georg_Artus at Physik.TUMuenchen.DE
Fri Jan 22 14:21:26 CET 1999
Hello,
> I think you have a typo here (or else I did not understand you
> properly). The guide entrance is 10cm high, but the exit is 1cm.
Ooops! I checked the real input file and there the numbers were correct!
Probably I copied wrong files from another directory or so. Nevertheless
I checked the input files again, compiled and started them with correct
heights and the results are still those I wrote in my last mail.
> Hm. I am starting to think that I may have mislead you about fluxes in
> McStas. The ONLY place the notion of flux is used in McStas is in the
> "flux" parameter of Source_flux. All the monitors simulate real
> monitors/detectors, and compute neutron counts, not neutron fluxes.
> Depending on your viewpoint, you can say that you are simulating a one
> second experiment; then the monitors count neutrons per second.
This starts clearifying things. The misleading thing was in fact the
answer to my question,

V
"
> What are the units of I and M2 for any monitor when I use source_flux?
> I assume it is n/cm**2/s/AA?
It is n/cm**2/time/st/AA, where the 'st' means steradian (units of solid
angle), and 'time' is the same unit as the one supplied for the 'flux'
parameter of the component (McStas does not really have any comcept of
the duration of an experiment).
"
> What this means is that if you want the flux in n/cm**2, you need to
> divide by the area of the monitor. Since the flux will probably depend
> on the position, you really need to use a positionsensitive detector
> and divide each bin by the pixel area. I suspect that the McStas flux
> values given above are in fact the "raw" counts in monitor2.
> When I divide by the monitor area, I get the following numbers:
>
> Flux [neutrons/cm**2]
> straight 3.43 1.71E7
> focusing 2.87 1.79E7
>
> These numbers match well with the Beamline results when compared relatively.
>
> To get the units in neutrons/AA, it would be necessary to use an energy
> sensitive detector and divide each bin by its wavelength range.
Now this all sounds very logical. The latter sounds not easy. What is
the wavelength range when you don't have an even distribution (as you
have it at the source)? This distribution of course changes after any
component.
> I hope this clarifies matters? Otherwise, please ask again. Do you think
> the way the monitors in McStas work should be changed to handle flux
> like in Beamline, and if so, why?
It would be extremely useful to have monitors which calculate flux
densities! If one (as we have to do it here) wants to compare different
complicated guide systems (primary guide, monochromator, secondary
guide, sample) the only measure for comparison is absolute flux density.
Anything like transmission or n/time doesn't help, since we have to
alter all entrance and exit heights, monochromator heights, sample sizes
and so on. It would be extremely tedious to get the flux densities by
hand! I had about 500 numbers in the last weeks I would have to treat
like this! Doing All these calculations by hand is just impossible.
If one wants to compare different real instruments, different
simulations or the results of different simulation software the three
most important numbers are transmission, flux and flux density. May be
it would be a good idea to give not only the numbers in the output file
but also the according units.
If you see the chance of writing a monitor, which computes flux
densities automatically, it would be of really great help to us!
Many thanks!
Georg

*********************************************
Dr. Georg Artus
Technische Universitaet Muenchen
FRMII Reaktorstation
D85747 Garching
Tel: +49 (0)89/28914675
Fax: +49 (0)89/28914666 or 12112
Email: gartus at ph.tum.de
More information about the mcstasusers
mailing list