- Timestamp:
- Dec 12, 2008 3:14:07 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
sans/Dev/trunk/NCNR_User_Procedures/Reduction/SANS/MultScatter_MonteCarlo_2D.ipf
r459 r465 11 11 // 12 12 // - Why am I off by a factor of 2.7 - 3.7 (MC too high) relative to real data? 13 // I need to include efficiency (70%?) - do I knock these off be 13 // I need to include efficiency (70%?) - do I knock these off before the simulation or do I 14 14 // really simulate that some fraction of neutrons on the detector don't actually get counted? 15 // Is the flux estimate up-to-date? 15 // Is the flux estimate up-to-date? !! Flux estimates at NG3 are out-of-date.... 16 // - my simulated transmission is larger than what is measured, even after correcting for the quartz cell. 17 // Why? Do I need to include absorption? Just inherent problems with incoherent cross sections? 18 16 19 // - Most importantly, this needs to be checked for correctness of the MC simulation 17 20 // X how can I get the "data" on absolute scale? This would be a great comparison vs. the ideal model calculation 18 21 // X why does my integrated tau not match up with John's analytical calculations? where are the assumptions? 19 22 // - get rid of all small angle assumptions - to make sure that the calculation is correct at all angles 20 // - my simulated transmission is larger than what is measured, even after correcting for the quartz cell. 21 // Why? Do I need to include absorption? Just inherent problems with incoherent cross sections? 23 22 24 // 23 25 // X at the larger angles, is the "flat" detector being properly accounted for - in terms of … … 50 52 // 51 53 // X why is "pure" incoherent scattering giving me a q^-1 slope, even with the detector all the way back? 52 // - can I speed up by assuming everything interacts? This would compromise the ability to calculate multiple scattering54 // -NO- can I speed up by assuming everything interacts? This would compromise the ability to calculate multiple scattering 53 55 // X ask John how to verify what is going on 54 56 // - a number of models are now found to be ill-behaved when q=1e-10. Then the random deviate calculation blows up. 55 57 // a warning has been added - but some models need a proper limiting value, and some (power-law) are simply unuseable 56 58 // unless something else can be done. 59 // - if the MC gags on a simulation, it often gets "stuck" and can't do the normal calculation from the model, which it 60 // should always default to... 57 61 // 58 62 //
Note: See TracChangeset
for help on using the changeset viewer.