From L.C.Chapon at rl.ac.uk Wed Jul 23 17:33:28 2003 From: L.C.Chapon at rl.ac.uk (Chapon, LC (Laurent) ) Date: Wed, 23 Jul 2003 16:33:28 +0100 Subject: [neutron-mc] Powder sample Message-ID: <37CAC51AC5C1D211966100A0C9ED000A0310E4A1@exchange07.rl.ac.uk> Dear McStas users, At the moment I am using the Powder1 component for simulations of tof powder diffractometers. That works ok but it allows only one scattering vector. I was wondering if a more general version of powder1.comp is available (typically where a set of reflections with associated intensities are read from a separated file). Thanks in advance for your help. ______________________________________ Dr Laurent Chapon Instrument Scientist ISIS department Bldg R3 Rutherford Appleton Laboratory Chilton, Didcot OX11 0QX UK -------------- next part -------------- An HTML attachment was scrubbed... URL: From R.L.McGreevy at rl.ac.uk Thu Jul 24 09:02:35 2003 From: R.L.McGreevy at rl.ac.uk (McGreevy, RL (Robert) ) Date: Thu, 24 Jul 2003 08:02:35 +0100 Subject: [neutron-mc] Powder sample Message-ID: <37CAC51AC5C1D211966100A0C9ED000A031630C0@exchange07.rl.ac.uk> Laurent, I believe that Thomas Hansen at ILL has such a component. Robert -----Original Message----- From: Chapon, LC (Laurent) [mailto:L.C.Chapon at rl.ac.uk] Sent: 23 July 2003 16:33 To: 'neutron-mc at risoe.dk' Subject: [neutron-mc] Powder sample Dear McStas users, At the moment I am using the Powder1 component for simulations of tof powder diffractometers. That works ok but it allows only one scattering vector. I was wondering if a more general version of powder1.comp is available (typically where a set of reflections with associated intensities are read from a separated file). Thanks in advance for your help. ______________________________________ Dr Laurent Chapon Instrument Scientist ISIS department Bldg R3 Rutherford Appleton Laboratory Chilton, Didcot OX11 0QX UK -------------- next part -------------- An HTML attachment was scrubbed... URL: From farhi at ill.fr Thu Jul 24 10:54:48 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Thu, 24 Jul 2003 10:54:48 +0200 Subject: [neutron-mc] Powder sample References: <37CAC51AC5C1D211966100A0C9ED000A031630C0@exchange07.rl.ac.uk> Message-ID: <3F1F9ED8.1AEACCF4@ill.fr> Hello Laurent, Indeed, the Powder0.comp component in the MCSTASLIB/obsolete directory is a multiple scattering vector powder model. It works ok, even if the code and usage is not absolutely clear. Type in 'mcdoc Powder0' to access online help (better when your BROWSER is defined as e.g. netscape, mozilla, msie, ...). More evolved powder sample models under development here at the ILL/ESRF are being tested, but they are not validated yet. Good luck with McStas. Emmanuel. "McGreevy, RL (Robert)" wrote: > Laurent, > > I believe that Thomas Hansen at ILL has such a component. > > Robert > > -----Original Message----- > From: Chapon, LC (Laurent) [mailto:L.C.Chapon at rl.ac.uk] > Sent: 23 July 2003 16:33 > To: 'neutron-mc at risoe.dk' > Subject: [neutron-mc] Powder sample > > Dear McStas users, > > At the moment I am using the Powder1 component for simulations of tof > powder diffractometers. That works ok but it allows only one > scattering vector. I was wondering if a more general version of > powder1.comp is available (typically where a set of reflections with > associated intensities are read from a separated file). > > Thanks in advance for your help. > > ______________________________________ > > Dr Laurent Chapon > > Instrument Scientist > > ISIS department > > Bldg R3 > > Rutherford Appleton Laboratory > > Chilton, Didcot > > OX11 0QX > > UK > -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Timur.Elzhov at jinr.ru Thu Jul 31 11:23:55 2003 From: Timur.Elzhov at jinr.ru (Timur Elzhov) Date: Thu, 31 Jul 2003 13:23:55 +0400 Subject: [neutron-mc] detector output files Message-ID: <20030731092355.GA15765@nf034.jinr.ru> Dear McStas experts! Sorry, but I couldn't understand the `N' colon from the subj. From Timur.Elzhov at jinr.ru Thu Jul 31 11:39:39 2003 From: Timur.Elzhov at jinr.ru (Timur Elzhov) Date: Thu, 31 Jul 2003 13:39:39 +0400 Subject: [neutron-mc] Re: detector output files In-Reply-To: <20030731092355.GA15765@nf034.jinr.ru> References: <20030731092355.GA15765@nf034.jinr.ru> Message-ID: <20030731093939.GB15765@nf034.jinr.ru> oops, the messaage has run away ... :-) so, I use Source_Maxwell source to generate neutrons, and detect them with 1D detector. And, I couldn't understand the imeaning of `N' colon from the detector out file. `I' shows the actual distribution - that's what I want. I believe that detector catches less neutrons for one bin and more for another bin, in accordance for the maxwell distribution. But I found in the manual: One-dimentional histogran detectors: ... Each line contains a number identifying the bin followed by three numbers: the simulated intensity, an estimate of the SE, and the number of neutron events for this bin. And the last, "number of neutron events for the bin", is _constant_ for the maxwell source distribution (I guess for any other distribution either). Could anybody explain me what the `N' colon means? At first time I pointed that this colon looked like transmission function for netron guides. But then I calculated I(after_guide)/I(before_guide) and found result _quantatively_ different from N(after_guide). Thank you! -- WBR, Timur. From Timur.Elzhov at jinr.ru Thu Jul 31 12:08:06 2003 From: Timur.Elzhov at jinr.ru (Timur Elzhov) Date: Thu, 31 Jul 2003 14:08:06 +0400 Subject: [neutron-mc] Re: detector output files In-Reply-To: <20030731093939.GB15765@nf034.jinr.ru> References: <20030731092355.GA15765@nf034.jinr.ru> <20030731093939.GB15765@nf034.jinr.ru> Message-ID: <20030731100806.GA16110@nf034.jinr.ru> On Thu, Jul 31, 2003 at 01:39:39PM +0400, Timur Elzhov wrote: > Could anybody explain me what the `N' colon means? At first time > I pointed that this colon looked like transmission function for > netron guides. But then I calculated I(after_guide)/I(before_guide) > and found result _quantatively_ different from N(after_guide). oh I'm mistaken - I mean _qualitatively_ of course. -- WBR, Timur. From farhi at ill.fr Thu Jul 31 12:26:47 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Thu, 31 Jul 2003 12:26:47 +0200 Subject: [neutron-mc] Re: detector output files References: <20030731092355.GA15765@nf034.jinr.ru> <20030731093939.GB15765@nf034.jinr.ru> Message-ID: <3F28EEE7.6F005026@ill.fr> Hello Timur, The 'N' data has no physical sense. It is a number of simulation events for a given data bin. You basically should not use that data, except if you wish to study the simulation statistics and efficiency (see Manual, p 41). In McStas, a simulation event may be regarded as a pack of neutrons, containing 'p' particules. When this event propagates, its 'filling' decreases, and the total weight of the pack is the intensity 'I' when stored in monitor bins, even if the event is still there (and counts for '1' in 'N'). I also remember that some e-mails about this are in the neutron-mc archive. Browse it to find comments from Kristian Nielsen, probably in 2000. Good luck with Mcstas, Emmanuel. Timur Elzhov wrote: > oops, the messaage has run away ... :-) > > so, I use Source_Maxwell source to generate neutrons, and detect > them with 1D detector. And, I couldn't understand the imeaning of `N' > colon from the detector out file. `I' shows the actual distribution - > that's what I want. I believe that detector catches less neutrons for > one bin and more for another bin, in accordance for the maxwell > distribution. But I found in the manual: > > One-dimentional histogran detectors: ... > Each line contains a number identifying the bin followed by three > numbers: the simulated intensity, an estimate of the SE, and the > number of neutron events for this bin. > > And the last, "number of neutron events for the bin", is _constant_ for > the maxwell source distribution (I guess for any other distribution > either). > > Could anybody explain me what the `N' colon means? At first time > I pointed that this colon looked like transmission function for > netron guides. But then I calculated I(after_guide)/I(before_guide) > and found result _quantatively_ different from N(after_guide). > > Thank you! > > -- > WBR, > Timur. > _______________________________________________ > neutron-mc mailing list > neutron-mc at neutron.risoe.dk > http://neutron.risoe.dk/mailman/listinfo/neutron-mc -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Timur.Elzhov at jinr.ru Fri Aug 1 12:03:26 2003 From: Timur.Elzhov at jinr.ru (Timur Elzhov) Date: Fri, 01 Aug 2003 14:03:26 +0400 Subject: [neutron-mc] detector output files In-Reply-To: <3F28EEE7.6F005026@ill.fr> References: <20030731092355.GA15765@nf034.jinr.ru> <20030731093939.GB15765@nf034.jinr.ru> <3F28EEE7.6F005026@ill.fr> Message-ID: <20030801100326.GA7629@nf034.jinr.ru> On Thu, Jul 31, 2003 at 12:26:47PM +0200, Emmanuel Farhi wrote: > The 'N' data has no physical sense. It is a number of simulation events > for a given data bin. You basically should not use that data, except if > you wish to study the simulation statistics and efficiency (see Manual, p > 41). > In McStas, a simulation event may be regarded as a pack of neutrons, > containing 'p' particules. When this event propagates, its 'filling' > decreases, and the total weight of the pack is the intensity 'I' when > stored in monitor bins, even if the event is still there (and counts for > '1' in 'N'). OK! Bu, let's have a look at the exec string of my program: ./dn2-guide.out --ncount=1e+06 S=3.0 R0=1.00 ... and at the output: Detector: detect_inc_I=6.77255e+09 detect_inc_ERR=1.1166e+07 detect_inc_N=999931 "inc0003.0.dat" Detector: detect_out_I=1.98277e+08 detect_out_ERR=856286 detect_out_N=446104 "out0003.0.dat" "detect_inc" is detector at the guide entrance, and all the incoming neutrons are directed to them. But, "detect_inc_N" is likely to correspond to the total counts of neutrons, not "detect_inc_I". "detect_inc_I" expressed in the strange units and have values of order of 7-8, while I've simulated 1e+6 neutrons... I obviosly misunderstand something, excuse me please :-) -- WBR, Timur. From farhi at ill.fr Fri Aug 1 13:45:03 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Fri, 01 Aug 2003 13:45:03 +0200 Subject: [neutron-mc] detector output files References: <20030731092355.GA15765@nf034.jinr.ru> <20030731093939.GB15765@nf034.jinr.ru> <3F28EEE7.6F005026@ill.fr> <20030801100326.GA7629@nf034.jinr.ru> Message-ID: <3F2A52BF.D6DB0C1B@ill.fr> Hello Timur, When you simulate -n 1e6 neutrons, these are not exactly neutrons, but neutron packs, associated to a weight which is given usually by the source. The weight IS the intensity. DO NOT use the number of events. It has NOTHING to do with the neutron flux or intensity, nor with the transmission. The 'strange units' you are talking are the intensities. If you want to simulate the transmission, place a monitor before and after a section, and look for the intensity ratio (not N). Bye, Emmanuel. Timur Elzhov wrote: > On Thu, Jul 31, 2003 at 12:26:47PM +0200, Emmanuel Farhi wrote: > > > The 'N' data has no physical sense. It is a number of simulation events > > for a given data bin. You basically should not use that data, except if > > you wish to study the simulation statistics and efficiency (see Manual, p > > 41). > > In McStas, a simulation event may be regarded as a pack of neutrons, > > containing 'p' particules. When this event propagates, its 'filling' > > decreases, and the total weight of the pack is the intensity 'I' when > > stored in monitor bins, even if the event is still there (and counts for > > '1' in 'N'). > OK! Bu, let's have a look at the exec string of my program: > > ./dn2-guide.out --ncount=1e+06 S=3.0 R0=1.00 ... > > and at the output: > > Detector: detect_inc_I=6.77255e+09 detect_inc_ERR=1.1166e+07 detect_inc_N=999931 "inc0003.0.dat" > Detector: detect_out_I=1.98277e+08 detect_out_ERR=856286 detect_out_N=446104 "out0003.0.dat" > > "detect_inc" is detector at the guide entrance, and all the incoming neutrons > are directed to them. But, "detect_inc_N" is likely to correspond to the total > counts of neutrons, not "detect_inc_I". "detect_inc_I" expressed in the > strange units and have values of order of 7-8, while I've simulated 1e+6 > neutrons... I obviosly misunderstand something, excuse me please :-) > > -- > WBR, > Timur. > > _______________________________________________ > neutron-mc mailing list > neutron-mc at neutron.risoe.dk > http://neutron.risoe.dk/mailman/listinfo/neutron-mc -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From D.Champion at rl.ac.uk Wed Aug 6 13:25:59 2003 From: D.Champion at rl.ac.uk (Champion, JDM (Dickon) ) Date: Wed, 06 Aug 2003 12:25:59 +0100 Subject: [neutron-mc] Chopper_fermi arguments Message-ID: <37CAC51AC5C1D211966100A0C9ED000A035D6BA5@exchange07.rl.ac.uk> Hi i am testing the soon to be officially released ISIS moderator modules with the Chopper_fermi module of Andrew Garrett. I was wondering how the Phase Angle is precisely defined? I have been looking at the code but it is not obvious to me. i can get reasonable results if i put the time of the selected energy to reach the far wall of the cylinder in the x=0 plane, but i would like to know what the module is expecting. thank you for any help in this matter dickon Dr Dickon Champion ISIS Facility R3 Room 1-49 Rutherford Appleton Laboratory Chilton OX11 0QX Tel : 01235 446043 (Office) 07939 084159 (Mobile) Fax : 01235 445720 From PWilk-neutron at zenspider.com Wed Aug 6 16:39:01 2003 From: PWilk-neutron at zenspider.com (Philip Wilk) Date: Wed, 06 Aug 2003 07:39:01 -0700 Subject: [neutron-mc] Trace on Win32 with the Vanadium example In-Reply-To: <37CAC51AC5C1D211966100A0C9ED000A035D6BA5@exchange07.rl.ac.uk> References: <37CAC51AC5C1D211966100A0C9ED000A035D6BA5@exchange07.rl.ac.uk> Message-ID: <20030806143901.GA93949@greed.zenspider.com> I am trying to get a Trace of my simulation to work with Mcstas 1.7 on win2k box. It does not work. If I try to Trace the Vanadium example, it also does not work. It produces a .sci file, but when I try to run this file in SciLab I get this error: -->exec('C:\mcstas\examples\mcdisplay_output.sci');disp('exec done'); Warning :redefining function: isempty !--error 4 undefined variable : clf at line 3 of function PlotInstrument3D called by : line 32 of function endtrace called by : endtrace(); line 46 of exec file called by : exec('C:\mcstas\examples\mcdisplay_output.sci');disp('exec done'); Am I doing this wrong? After choosing Trace, PlotResults, and Run in McGui is something graphical supposed to automatically happen like with a normal simulation? Regards, Philip From farhi at ill.fr Wed Aug 6 17:08:57 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Wed, 06 Aug 2003 17:08:57 +0200 Subject: [neutron-mc] Trace on Win32 with the Vanadium example References: <37CAC51AC5C1D211966100A0C9ED000A035D6BA5@exchange07.rl.ac.uk> <20030806143901.GA93949@greed.zenspider.com> Message-ID: <3F311A09.C7BFEB7@ill.fr> Hello Philip, I think the problem comes from the fact that mcdisplay/Scilab needs the Plotlib Scilab library, which you may get at , or following the links from . This library is very easy to install. mcplot does not require this library. Good luck. Emmanuel. Philip Wilk wrote: > I am trying to get a Trace of my simulation to work with Mcstas 1.7 on win2k box. It does not work. If I try to Trace the Vanadium example, it also does not work. It produces a .sci file, but when I try to run this file in SciLab I get this error: > > -->exec('C:\mcstas\examples\mcdisplay_output.sci');disp('exec done'); > Warning :redefining function: isempty > > !--error 4 > undefined variable : clf > at line 3 of function PlotInstrument3D called by : > line 32 of function endtrace called by : > endtrace(); > line 46 of exec file called by : > exec('C:\mcstas\examples\mcdisplay_output.sci');disp('exec done'); > > Am I doing this wrong? After choosing Trace, PlotResults, and Run in McGui is something graphical supposed to automatically happen like with a normal simulation? > > Regards, > Philip > _______________________________________________ > neutron-mc mailing list > neutron-mc at neutron.risoe.dk > http://neutron.risoe.dk/mailman/listinfo/neutron-mc -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From granrothge at ornl.gov Mon Aug 11 19:30:49 2003 From: granrothge at ornl.gov (Granroth, Garrett E.) Date: Mon, 11 Aug 2003 13:30:49 -0400 Subject: [neutron-mc] Chopper_fermi arguments Message-ID: Dickon, For simulating the SNS Fermi chopper instruments ARCS and SEQUOIA, I have found that I get the correct phasing for phase=(L1)/(sqrt(E)*SE2V)+toffset; Where L1 is the distance from the moderator to the chopper, E is the energy of desired neutron, and toffset accounts for the time difference between t=0 and the time when the moderator has the highest probability of emitting a neutron of energy E. Hopefully this helps. Garrett Garrett Granroth Instrument Scientist Spallation Neutron Source Oak Ridge National Laboratory P.O. Box 2008 MS 6474 Oak Ridge TN 37831 Phone: 865-576-0900 Fax: 865-241-5177 email: granrothge at ornl.gov -----Original Message----- From: Champion, JDM (Dickon) [mailto:D.Champion at rl.ac.uk] Sent: Wednesday, August 06, 2003 7:26 AM To: 'neutron-mc at neutron.risoe.dk' Subject: [neutron-mc] Chopper_fermi arguments Hi i am testing the soon to be officially released ISIS moderator modules with the Chopper_fermi module of Andrew Garrett. I was wondering how the Phase Angle is precisely defined? I have been looking at the code but it is not obvious to me. i can get reasonable results if i put the time of the selected energy to reach the far wall of the cylinder in the x=0 plane, but i would like to know what the module is expecting. thank you for any help in this matter dickon Dr Dickon Champion ISIS Facility R3 Room 1-49 Rutherford Appleton Laboratory Chilton OX11 0QX Tel : 01235 446043 (Office) 07939 084159 (Mobile) Fax : 01235 445720 _______________________________________________ neutron-mc mailing list neutron-mc at neutron.risoe.dk http://neutron.risoe.dk/mailman/listinfo/neutron-mc From farhi at ill.fr Tue Aug 26 15:17:57 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Tue, 26 Aug 2003 15:17:57 +0200 Subject: [neutron-mc] Re: sqrt: DOMAIN error References: <001801c36bd1$249cd260$4e68bb81@rad.chemie.tumuenchen.de> Message-ID: <3F4B5E05.F52FF7A9@ill.fr> Hy Philip, You probably have some zero velocity neutrons or such huge velocities that the square gets hawfull (before getting the sqrt), else I can not figure out how the 'sqrt' can fail in the speed in L_monitor.comp. You may copy this component locally and change the line #76 so that it tests the speed norm to be non zero or reasonable value (not huge). You may also try replacing with the Monitor_nD(options="auto lambda", filename="...") Cheers, Emmanuel. Philip Wilk wrote: > Hi, > > I am using the new version 1.7 > > I keep getting "sqrt: DOMAIN error" > > Just like I was getting with version 1.6.4 , should I be worried about this? > It seems to be associated with the wavelength detector component. > > See example output: > > Detector: psd_begin_I=75.9887 psd_begin_ERR=0.0701353 > psd_begin_N=3.65191e+06 "p > sd1.dat" > Detector: lambda_begin_I=75.9887 lambda_begin_ERR=0.0701353 > lambda_begin_N=3.651 > 91e+06 "erg1.dat" > Detector: psd_middle_I=6.2552 psd_middle_ERR=0.017862 > psd_middle_N=1.68387e+06 " > psd2.dat" > > sqrt: DOMAIN error > Detector: lambda_middle_I=6.2552 lambda_middle_ERR=0.017862 > lambda_middle_N=1.68 > 387e+06 "erg2.dat" > Detector: psd_middle2_I=1.20321 psd_middle2_ERR=0.00418768 > psd_middle2_N=1.08584 > e+06 "psd3.dat" > Detector: lambda_middle2_I=1.20321 lambda_middle2_ERR=0.00418768 > lambda_middle2_ > N=1.08584e+06 "erg3.dat" > Detector: psd_end_I=0.65266 psd_end_ERR=0.002805 psd_end_N=389221 "psd4.dat" > Detector: lambda_end_I=0.65266 lambda_end_ERR=0.002805 lambda_end_N=389221 > "erg4 > .dat" > > Cheers, > Philip -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From farhi at ill.fr Wed Aug 27 11:07:42 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Wed, 27 Aug 2003 11:07:42 +0200 Subject: [neutron-mc] Generate a source spectra from exp. file References: <002401c36bd8$a7c43eb0$4e68bb81@rad.chemie.tumuenchen.de> Message-ID: <3F4C74DE.5B2B1AAA@ill.fr> Yes, there is a solution to use an experimental profile for the simulation source. First position a normal source (Source_flat or Source_gen, or ...). Then, you may use the Filter_gen component (in the optics) to read the contents a a file, with options="lambda, set weight". Then the first column of the table is assumed to be the wavelength, and the second should be the flux to set. A rebinning/interpolation is done when loading the table. This will set the weight of neutrons. You may also choose to multiply or add to the existing weight. The Filter_gen (McStas v1.7) is a replacement to the old Flux_adapter. Just look at the MCSTASLIB/optics/Filter_gen component (or 'mcdoc Filter_gen'). pwilk wrote: > Thanks for the quick reply! I'll give that a go.I think you are right > about the zero velocity neutrons.I have another quick question for > you: Is there an easy way to simulate a source from a 2D file of > (measured) Intensity vs. Wavelength ?Cheers,Philip > > -----Original Message----- > From: farhi at ill.fr [mailto:farhi at ill.fr] > Sent: Tuesday, August 26, 2003 3:18 PM > To: pwilk-radiochem at hahnium.com; neutron-mc at risoe.dk > Subject: Re: sqrt: DOMAIN error > Hy Philip, > > You probably have some zero velocity neutrons or such huge > velocities that the square gets hawfull (before getting the > sqrt), else I can not figure out how the 'sqrt' can fail in > the speed in L_monitor.comp. > You may copy this component locally and change the line #76 > so that it tests the speed norm to be non zero or reasonable > value (not huge). > > You may also try replacing with the Monitor_nD(options="auto > lambda", filename="...") > > Cheers, Emmanuel. > > Philip Wilk wrote: > > > Hi, > > > > I am using the new version 1.7 > > > > I keep getting "sqrt: DOMAIN error" > > > > Just like I was getting with version 1.6.4 , should I be > > worried about this? > > It seems to be associated with the wavelength detector > > component. > > > > See example output: > > > > Detector: psd_begin_I=75.9887 psd_begin_ERR=0.0701353 > > psd_begin_N=3.65191e+06 "p > > sd1.dat" > > Detector: lambda_begin_I=75.9887 > > lambda_begin_ERR=0.0701353 > > lambda_begin_N=3.651 > > 91e+06 "erg1.dat" > > Detector: psd_middle_I=6.2552 psd_middle_ERR=0.017862 > > psd_middle_N=1.68387e+06 " > > psd2.dat" > > > > sqrt: DOMAIN error > > Detector: lambda_middle_I=6.2552 > > lambda_middle_ERR=0.017862 > > lambda_middle_N=1.68 > > 387e+06 "erg2.dat" > > Detector: psd_middle2_I=1.20321 psd_middle2_ERR=0.00418768 > > > > psd_middle2_N=1.08584 > > e+06 "psd3.dat" > > Detector: lambda_middle2_I=1.20321 > > lambda_middle2_ERR=0.00418768 > > lambda_middle2_ > > N=1.08584e+06 "erg3.dat" > > Detector: psd_end_I=0.65266 psd_end_ERR=0.002805 > > psd_end_N=389221 "psd4.dat" > > Detector: lambda_end_I=0.65266 lambda_end_ERR=0.002805 > > lambda_end_N=389221 > > "erg4 > > .dat" > > > > Cheers, > > Philip > > -- > What's up Doc ? > -------------------------------------------- > Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ > CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ > 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ > Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ > > > -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From pwilk at zenspider.com Fri Aug 29 12:21:42 2003 From: pwilk at zenspider.com (Philip Wilk) Date: Fri, 29 Aug 2003 12:21:42 +0200 Subject: [neutron-mc] Generate a source spectra from exp. file References: <002401c36bd8$a7c43eb0$4e68bb81@rad.chemie.tumuenchen.de> <3F4C74DE.5B2B1AAA@ill.fr> Message-ID: <006101c36e17$573944e0$4e68bb81@rad.chemie.tumuenchen.de> It is not working for me. It seems to add to it, rather then set it. I just put this at the top of the file right? # lambda set and it sets the options? Regards, Philip ----- Original Message ----- From: Emmanuel Farhi To: pwilk at zenspider.com ; neutron-mc at risoe.dk Sent: Wednesday, August 27, 2003 11:07 AM Subject: [neutron-mc] Generate a source spectra from exp. file Yes, there is a solution to use an experimental profile for the simulation source. First position a normal source (Source_flat or Source_gen, or ...). Then, you may use the Filter_gen component (in the optics) to read the contents a a file, with options="lambda, set weight". Then the first column of the table is assumed to be the wavelength, and the second should be the flux to set. A rebinning/interpolation is done when loading the table. This will set the weight of neutrons. You may also choose to multiply or add to the existing weight. The Filter_gen (McStas v1.7) is a replacement to the old Flux_adapter. Just look at the MCSTASLIB/optics/Filter_gen component (or 'mcdoc Filter_gen'). pwilk wrote: Thanks for the quick reply! I'll give that a go.I think you are right about the zero velocity neutrons.I have another quick question for you: Is there an easy way to simulate a source from a 2D file of (measured) Intensity vs. Wavelength ?Cheers,Philip -----Original Message----- From: farhi at ill.fr [mailto:farhi at ill.fr] Sent: Tuesday, August 26, 2003 3:18 PM To: pwilk-radiochem at hahnium.com; neutron-mc at risoe.dk Subject: Re: sqrt: DOMAIN error Hy Philip, You probably have some zero velocity neutrons or such huge velocities that the square gets hawfull (before getting the sqrt), else I can not figure out how the 'sqrt' can fail in the speed in L_monitor.comp. You may copy this component locally and change the line #76 so that it tests the speed norm to be non zero or reasonable value (not huge). You may also try replacing with the Monitor_nD(options="auto lambda", filename="...") Cheers, Emmanuel. Philip Wilk wrote: Hi, I am using the new version 1.7 I keep getting "sqrt: DOMAIN error" Just like I was getting with version 1.6.4 , should I be worried about this? It seems to be associated with the wavelength detector component. See example output: Detector: psd_begin_I=75.9887 psd_begin_ERR=0.0701353 psd_begin_N=3.65191e+06 "p sd1.dat" Detector: lambda_begin_I=75.9887 lambda_begin_ERR=0.0701353 lambda_begin_N=3.651 91e+06 "erg1.dat" Detector: psd_middle_I=6.2552 psd_middle_ERR=0.017862 psd_middle_N=1.68387e+06 " psd2.dat" sqrt: DOMAIN error Detector: lambda_middle_I=6.2552 lambda_middle_ERR=0.017862 lambda_middle_N=1.68 387e+06 "erg2.dat" Detector: psd_middle2_I=1.20321 psd_middle2_ERR=0.00418768 psd_middle2_N=1.08584 e+06 "psd3.dat" Detector: lambda_middle2_I=1.20321 lambda_middle2_ERR=0.00418768 lambda_middle2_ N=1.08584e+06 "erg3.dat" Detector: psd_end_I=0.65266 psd_end_ERR=0.002805 psd_end_N=389221 "psd4.dat" Detector: lambda_end_I=0.65266 lambda_end_ERR=0.002805 lambda_end_N=389221 "erg4 .dat" Cheers, Philip -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From PWilk-neutron at zenspider.com Mon Sep 1 15:44:31 2003 From: PWilk-neutron at zenspider.com (Philip Wilk) Date: Mon, 01 Sep 2003 06:44:31 -0700 Subject: [neutron-mc] Generate a source spectra from exp. file In-Reply-To: <006101c36e17$573944e0$4e68bb81@rad.chemie.tumuenchen.de> References: <002401c36bd8$a7c43eb0$4e68bb81@rad.chemie.tumuenchen.de> <3F4C74DE.5B2B1AAA@ill.fr> <006101c36e17$573944e0$4e68bb81@rad.chemie.tumuenchen.de> Message-ID: <20030901134431.GA92825@greed.zenspider.com> Ok, I figured it out. The instructions in the Filter_gen.comp header were a little cryptic and there is zero documentation on the component in the lib/doc/mcstas-components.pdf file. The options are set at the top of the data file with a comment-line (starts with #) and can be: "k", "q", "wavevector", "omega", "e", "energy", "lamda" or "wavelength"; followed by "set", "add", or "multiply". You can separate the options with a space. You can also add "verbose" if you want. See the lib/data/HOPG.trm file line 7 as an example. The Filter_gen.comp has a typo of "lib/data/HOPG.trs" where it should be "lib/data/HOPG.trm", and also says: * options: string that can contain (str) * "[ k p ]" or "wavector" for file type * "[ omega p]" or "energy" * "[ lambda p ]" or "wavelength" * "set" to set the weight according to the table * "multiply" to multiply (instead of set) the weight by factor * "add" to add to current flux * "verbose" to display additional informations This seems to indicate you can also set the options from where you call the component. I do not fully understand what the "p" is for in "[ k p ]", "[ omega p]", and "[ lambda p ]". Cheers, Philip Thus spake Philip Wilk (pwilk at zenspider.com): > It is not working for me. It seems to add to it, rather then set it. > I just put this at the top of the file right? > > # lambda set > > and it sets the options? > > Regards, > Philip > > ----- Original Message ----- > > From: [1]Emmanuel Farhi > > To: [2]pwilk at zenspider.com ; [3]neutron-mc at risoe.dk > > Sent: Wednesday, August 27, 2003 11:07 AM > > Subject: [neutron-mc] Generate a source spectra from exp. file > > Yes, there is a solution to use an experimental profile for the > simulation source. > > First position a normal source (Source_flat or Source_gen, or ...). > Then, you may use the Filter_gen component (in the optics) to read > the contents a a file, with options="lambda, set weight". Then the > first column of the table is assumed to be the wavelength, and the > second should be the flux to set. > A rebinning/interpolation is done when loading the table. This will > set the weight of neutrons. You may also choose to multiply or add > to the existing weight. > The Filter_gen (McStas v1.7) is a replacement to the old > Flux_adapter. > > Just look at the MCSTASLIB/optics/Filter_gen component (or 'mcdoc > Filter_gen'). > > pwilk wrote: > > Thanks for the quick reply! I'll give that a go.I think you are > right about the zero velocity neutrons.I have another quick > question for you: Is there an easy way to simulate a source from a > 2D file of (measured) Intensity vs. Wavelength ?Cheers,Philip > > -----Original Message----- > From: farhi at ill.fr [[4]mailto:farhi at ill.fr] > Sent: Tuesday, August 26, 2003 3:18 PM > To: pwilk-radiochem at hahnium.com; neutron-mc at risoe.dk > Subject: Re: sqrt: DOMAIN error > > Hy Philip, > > You probably have some zero velocity neutrons or such huge > velocities that the square gets hawfull (before getting the sqrt), > else I can not figure out how the 'sqrt' can fail in the speed in > L_monitor.comp. > You may copy this component locally and change the line #76 so that > it tests the speed norm to be non zero or reasonable value (not > huge). > > You may also try replacing with the Monitor_nD(options="auto > lambda", filename="...") > > Cheers, Emmanuel. > > Philip Wilk wrote: > > Hi, > > I am using the new version 1.7 > > I keep getting "sqrt: DOMAIN error" > > Just like I was getting with version 1.6.4 , should I be worried > about this? > It seems to be associated with the wavelength detector component. > > See example output: > > Detector: psd_begin_I=75.9887 psd_begin_ERR=0.0701353 > psd_begin_N=3.65191e+06 "p > sd1.dat" > Detector: lambda_begin_I=75.9887 lambda_begin_ERR=0.0701353 > lambda_begin_N=3.651 > 91e+06 "erg1.dat" > Detector: psd_middle_I=6.2552 psd_middle_ERR=0.017862 > psd_middle_N=1.68387e+06 " > psd2.dat" > > sqrt: DOMAIN error > Detector: lambda_middle_I=6.2552 lambda_middle_ERR=0.017862 > lambda_middle_N=1.68 > 387e+06 "erg2.dat" > Detector: psd_middle2_I=1.20321 psd_middle2_ERR=0.00418768 > psd_middle2_N=1.08584 > e+06 "psd3.dat" > Detector: lambda_middle2_I=1.20321 lambda_middle2_ERR=0.00418768 > lambda_middle2_ > N=1.08584e+06 "erg3.dat" > Detector: psd_end_I=0.65266 psd_end_ERR=0.002805 psd_end_N=389221 > "psd4.dat" > Detector: lambda_end_I=0.65266 lambda_end_ERR=0.002805 > lambda_end_N=389221 > "erg4 > .dat" > > Cheers, > Philip > > -- > What's up Doc ? > -------------------------------------------- > Emmanuel FARHI, [5]http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ > CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ > 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ > Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ > > > > -- > What's up Doc ? > -------------------------------------------- > Emmanuel FARHI, [6]http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ > CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ > 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ > Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ > > References > > 1. mailto:farhi at ill.fr > 2. mailto:pwilk at zenspider.com > 3. mailto:neutron-mc at risoe.dk > 4. mailto:farhi at ill.fr > 5. http://www.ill.fr/tas/people/Farhi.html > 6. http://www.ill.fr/tas/people/Farhi.html From srio at esrf.fr Tue Sep 9 10:27:03 2003 From: srio at esrf.fr (Manuel Sanchez Del Rio) Date: Tue, 09 Sep 2003 10:27:03 +0200 Subject: [neutron-mc] NOP Message-ID: <3F5D8ED7.105@esrf.fr> Dear McStas users we have released a new version of XOP2.1, the package of X-ray Oriented Programs. It now includes the NEUTRON OPTICS PACKAGE NOP and can be freely downloaded from the XOP site (it requires two installations, first the xop main package and second the NOP extension): http://www.esrf.fr/computing/scientific/xop2.1/ NOP includes: NSOURCES simple calculation of neutron reactor spectra. NMIRROR material cross-sections, attenuation coefficients, refractive indices, reflectivities. IMD (Windt) with a database of neutron refractive indices. This allows for the calculation of neutron reflectivities by multilayer using IMD. (IMD for neutrons is included in the NOP distribution). MAMON indexing and intensity of multiple Bragg diffraction by crystals. NCRYSTAL perfect and mosaic crystal reflectivity and transmissivity. Works also for asymmetric geometry. Computes other interesting parameters like structure factors, Bragg angles, primary and secondary extinction coefficients and others. DABAX a databases of: neutron scattering lengths and cross-sections, crystal structures and crystal cell parameters, compounds related quantities. XOP2.1 with its NOP extension is already available for Unix (Linux and Solaris) and Windows computers. Lucia & Manolo +----------------------------------------------------------------------+ |Manuel Sanchez del Rio |Tel +33-476 882513 (direct) | |European Synchrotron Radiation Facility| +33-476 882000 (switchbrd)| |BP 220 |Fax +33-476 882542 | |38043 Grenoble-Cedex (France) |e-mail srio at esrf.fr | |_______________________________________|______________________________| |http://www.esrf.fr (ESRF Home Page)| |http://www.esrf.fr/computing/scientific/ (Group Home Page)| |http://www.esrf.fr/computing/scientific/people/srio/ (Personal)| +----------------------------------------------------------------------+ From pwilk at zenspider.com Fri Sep 12 09:11:09 2003 From: pwilk at zenspider.com (Philip Wilk) Date: Fri, 12 Sep 2003 09:11:09 +0200 Subject: [neutron-mc] DOMAIN error with Monitor_nD component References: <001801c36bd1$249cd260$4e68bb81@rad.chemie.tumuenchen.de> <3F4B5E05.F52FF7A9@ill.fr> Message-ID: <001501c378fd$0b921d50$4e68bb81@rad.chemie.tumuenchen.de> Dear Emmanuel, I have also found the same error when using the Monitor_nD component. The output from the monitor looks fine and seems to be accurate, but the DOMAIN error is troubling. The monitor dimentions are small in this example, but I get the error with a larger monitor as well. I call the component with the following code (one example): ----- begin ------- COMPONENT lambda_end2 = Monitor_nD( xmin = -0.002, xmax = 0.002, ymin = -0.002, ymax = 0.002, options="lambda bins=50 auto limits", filename="erg5.dat") AT (0, 0, 3.05) RELATIVE cguide ROTATED (0, 0, 0) RELATIVE cguide ----- end ------- And the following is the output to the screen while running a simulation with 10^9 neutrons and a series of 8 wavelength monitors via the Monitor_nD component: ----- begin ------- sqrt: DOMAIN error Detector: lamda_begin_I=3.11197e+17 lamda_begin_ERR=1.92993e+13 lamda_begin_N=3. 63473e+08 "erg1.dat" Detector: lambda_middle_I=3.95513e+16 lambda_middle_ERR=6.03749e+12 lambda_middl e_N=1.68336e+08 "erg2.dat" Detector: lambda_middle2_I=1.43218e+16 lambda_middle2_ERR=3.13988e+12 lambda_mid dle2_N=1.08399e+08 "erg3.dat" Detector: lambda_end1_I=3.4155e+14 lambda_end1_ERR=4.58569e+11 lambda_end1_N=1.6 5878e+06 "erg4.dat" sqrt: DOMAIN error Detector: lambda_end2_I=3.87996e+14 lambda_end2_ERR=4.8729e+11 lambda_end2_N=1.8 729e+06 "erg5.dat" Detector: lambda_end3_I=4.37953e+14 lambda_end3_ERR=5.27462e+11 lambda_end3_N=1. 39967e+06 "erg6.dat" sqrt: DOMAIN error Detector: lambda_end4_I=3.60408e+14 lambda_end4_ERR=5.30696e+11 lambda_end4_N=75 1711 "erg7.dat" sqrt: DOMAIN error Detector: lambda_end5_I=2.45439e+14 lambda_end5_ERR=4.64571e+11 lambda_end5_N=44 5504 "erg8.dat" ----- end ------- Regards, Philip ----- Original Message ----- From: Emmanuel Farhi To: pwilk-radiochem at hahnium.com ; neutron-mc at risoe.dk Sent: Tuesday, August 26, 2003 3:17 PM Subject: Re: sqrt: DOMAIN error Hy Philip, You probably have some zero velocity neutrons or such huge velocities that the square gets hawfull (before getting the sqrt), else I can not figure out how the 'sqrt' can fail in the speed in L_monitor.comp. You may copy this component locally and change the line #76 so that it tests the speed norm to be non zero or reasonable value (not huge). You may also try replacing with the Monitor_nD(options="auto lambda", filename="...") Cheers, Emmanuel. Philip Wilk wrote: Hi, I am using the new version 1.7 I keep getting "sqrt: DOMAIN error" Just like I was getting with version 1.6.4 , should I be worried about this? It seems to be associated with the wavelength detector component. See example output: Detector: psd_begin_I=75.9887 psd_begin_ERR=0.0701353 psd_begin_N=3.65191e+06 "p sd1.dat" Detector: lambda_begin_I=75.9887 lambda_begin_ERR=0.0701353 lambda_begin_N=3.651 91e+06 "erg1.dat" Detector: psd_middle_I=6.2552 psd_middle_ERR=0.017862 psd_middle_N=1.68387e+06 " psd2.dat" sqrt: DOMAIN error Detector: lambda_middle_I=6.2552 lambda_middle_ERR=0.017862 lambda_middle_N=1.68 387e+06 "erg2.dat" Detector: psd_middle2_I=1.20321 psd_middle2_ERR=0.00418768 psd_middle2_N=1.08584 e+06 "psd3.dat" Detector: lambda_middle2_I=1.20321 lambda_middle2_ERR=0.00418768 lambda_middle2_ N=1.08584e+06 "erg3.dat" Detector: psd_end_I=0.65266 psd_end_ERR=0.002805 psd_end_N=389221 "psd4.dat" Detector: lambda_end_I=0.65266 lambda_end_ERR=0.002805 lambda_end_N=389221 "erg4 .dat" Cheers, Philip -- From farhi at ill.fr Fri Sep 12 10:12:29 2003 From: farhi at ill.fr (Emmanuel Farhi) Date: Fri, 12 Sep 2003 10:12:29 +0200 Subject: [neutron-mc] Re: sqrt: DOMAIN error References: <001801c36bd1$249cd260$4e68bb81@rad.chemie.tumuenchen.de> <3F4B5E05.F52FF7A9@ill.fr> <001501c378fd$0b921d50$4e68bb81@rad.chemie.tumuenchen.de> Message-ID: <3F617FED.444BDBA2@ill.fr> Hy Philip, I have looked at that 'sqrt: DOMAIN error' error printed while running your simulation. I could not reproduce it on my Dec Compaq computer, but I think I know what is the reason for the error. Indeed, it may come from the lib/share/mcstas-r.c:mcestimate_error function while computing the intensity error estimate. If your computer does not handle 'double' numbers with enough digits (64 bytes), then an error is reported when computing the sqr and then the sqrt. This is, I think, a numerical over or under flow depending on the number accuracy of your system. To test that, you may, for instance, divide your source flux by, say 10^10. Cheers, Emmanuel. Philip Wilk wrote: > Dear Emmanuel, > > I have also found the same error when using the Monitor_nD component. The > output from the monitor looks fine and seems to be accurate, but the DOMAIN > error is troubling. > > The monitor dimentions are small in this example, but I get the error with a > larger monitor as well. I call the component with the following code (one > example): > > ----- begin ------- > COMPONENT lambda_end2 = Monitor_nD( > xmin = -0.002, xmax = 0.002, > ymin = -0.002, ymax = 0.002, > options="lambda bins=50 auto limits", > filename="erg5.dat") > AT (0, 0, 3.05) RELATIVE cguide ROTATED (0, 0, 0) RELATIVE cguide > ----- end ------- > > And the following is the output to the screen while running a simulation > with 10^9 neutrons and a series of 8 wavelength monitors via the Monitor_nD > component: > > ----- begin ------- > sqrt: DOMAIN error > Detector: lamda_begin_I=3.11197e+17 lamda_begin_ERR=1.92993e+13 > lamda_begin_N=3. > 63473e+08 "erg1.dat" > Detector: lambda_middle_I=3.95513e+16 lambda_middle_ERR=6.03749e+12 > lambda_middl > e_N=1.68336e+08 "erg2.dat" > Detector: lambda_middle2_I=1.43218e+16 lambda_middle2_ERR=3.13988e+12 > lambda_mid > dle2_N=1.08399e+08 "erg3.dat" > Detector: lambda_end1_I=3.4155e+14 lambda_end1_ERR=4.58569e+11 > lambda_end1_N=1.6 > 5878e+06 "erg4.dat" > > sqrt: DOMAIN error > Detector: lambda_end2_I=3.87996e+14 lambda_end2_ERR=4.8729e+11 > lambda_end2_N=1.8 > 729e+06 "erg5.dat" > Detector: lambda_end3_I=4.37953e+14 lambda_end3_ERR=5.27462e+11 > lambda_end3_N=1. > 39967e+06 "erg6.dat" > > sqrt: DOMAIN error > Detector: lambda_end4_I=3.60408e+14 lambda_end4_ERR=5.30696e+11 > lambda_end4_N=75 > 1711 "erg7.dat" > > sqrt: DOMAIN error > Detector: lambda_end5_I=2.45439e+14 lambda_end5_ERR=4.64571e+11 > lambda_end5_N=44 > 5504 "erg8.dat" > ----- end ------- > > Regards, > Philip > > ----- Original Message ----- > From: Emmanuel Farhi > To: pwilk-radiochem at hahnium.com ; neutron-mc at risoe.dk > Sent: Tuesday, August 26, 2003 3:17 PM > > Hy Philip, > You probably have some zero velocity neutrons or such huge velocities that > the square gets hawfull (before getting the sqrt), else I can not figure out > how the 'sqrt' can fail in the speed in L_monitor.comp. > You may copy this component locally and change the line #76 so that it tests > the speed norm to be non zero or reasonable value (not huge). > You may also try replacing with the Monitor_nD(options="auto lambda", > filename="...") > Cheers, Emmanuel. > > Philip Wilk wrote: > Hi, > I am using the new version 1.7 > I keep getting "sqrt: DOMAIN error" > Just like I was getting with version 1.6.4 , should I be worried about this? > It seems to be associated with the wavelength detector component. > See example output: > Detector: psd_begin_I=75.9887 psd_begin_ERR=0.0701353 > psd_begin_N=3.65191e+06 "p > sd1.dat" > Detector: lambda_begin_I=75.9887 lambda_begin_ERR=0.0701353 > lambda_begin_N=3.651 > 91e+06 "erg1.dat" > Detector: psd_middle_I=6.2552 psd_middle_ERR=0.017862 > psd_middle_N=1.68387e+06 " > psd2.dat" > sqrt: DOMAIN error > Detector: lambda_middle_I=6.2552 lambda_middle_ERR=0.017862 > lambda_middle_N=1.68 > 387e+06 "erg2.dat" > Detector: psd_middle2_I=1.20321 psd_middle2_ERR=0.00418768 > psd_middle2_N=1.08584 > e+06 "psd3.dat" > Detector: lambda_middle2_I=1.20321 lambda_middle2_ERR=0.00418768 > lambda_middle2_ > N=1.08584e+06 "erg3.dat" > Detector: psd_end_I=0.65266 psd_end_ERR=0.002805 psd_end_N=389221 "psd4.dat" > Detector: lambda_end_I=0.65266 lambda_end_ERR=0.002805 lambda_end_N=389221 > "erg4 > .dat" > Cheers, > Philip > -- -- What's up Doc ? -------------------------------------------- Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html \|/ ____ \|/ CS-Group ILL4/156, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~ 6 rue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\ Work :Tel (33/0) 4 76 20 71 35. Fax (33/0) 4 76 20 76 48 \__U_/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From srio at esrf.fr Tue Sep 9 10:27:03 2003 From: srio at esrf.fr (Manuel Sanchez Del Rio) Date: Tue, 09 Sep 2003 10:27:03 +0200 Subject: [neutron-mc] NOP Message-ID: <3F5D8ED7.105@esrf.fr> Dear McStas users we have released a new version of XOP2.1, the package of X-ray Oriented Programs. It now includes the NEUTRON OPTICS PACKAGE NOP and can be freely downloaded from the XOP site (it requires two installations, first the xop main package and second the NOP extension): http://www.esrf.fr/computing/scientific/xop2.1/ NOP includes: NSOURCES simple calculation of neutron reactor spectra. NMIRROR material cross-sections, attenuation coefficients, refractive indices, reflectivities. IMD (Windt) with a database of neutron refractive indices. This allows for the calculation of neutron reflectivities by multilayer using IMD. (IMD for neutrons is included in the NOP distribution). MAMON indexing and intensity of multiple Bragg diffraction by crystals. NCRYSTAL perfect and mosaic crystal reflectivity and transmissivity. Works also for asymmetric geometry. Computes other interesting parameters like structure factors, Bragg angles, primary and secondary extinction coefficients and others. DABAX a databases of: neutron scattering lengths and cross-sections, crystal structures and crystal cell parameters, compounds related quantities. XOP2.1 with its NOP extension is already available for Unix (Linux and Solaris) and Windows computers. Lucia & Manolo +----------------------------------------------------------------------+ |Manuel Sanchez del Rio |Tel +33-476 882513 (direct) | |European Synchrotron Radiation Facility| +33-476 882000 (switchbrd)| |BP 220 |Fax +33-476 882542 | |38043 Grenoble-Cedex (France) |e-mail srio at esrf.fr | |_______________________________________|______________________________| |http://www.esrf.fr (ESRF Home Page)| |http://www.esrf.fr/computing/scientific/ (Group Home Page)| |http://www.esrf.fr/computing/scientific/people/srio/ (Personal)| +----------------------------------------------------------------------+ From D.Champion at rl.ac.uk Tue Sep 16 15:43:28 2003 From: D.Champion at rl.ac.uk (Champion, JDM (Dickon) ) Date: Tue, 16 Sep 2003 14:43:28 +0100 Subject: [neutron-mc] V_sample.comp Message-ID: <37CAC51AC5C1D211966100A0C9ED000A035D6C86@exchange07.rl.ac.uk> Hello after tearing my hair out for a couple of days i would like to make a comment on this module if you wish to make a cuboid sample you MUST make the counter-intuitive declaration of radius_o=0.0 or h=0. the radius and height of a cylindrical sample are set by default, therefore the first check in the INITIALIZE section " if (!radius_o || !h) " will never get a true response and it will never consider the possibility of a cuboid sample. a fix for this problem and to prevent the future confusion of others might be a check for the declaration of the xwidth, yheight, zthick etc.... instead dickon Dr Dickon Champion ISIS Facility R3 Room 1-49 Rutherford Appleton Laboratory Chilton OX11 0QX Tel : 01235 446043 (Office) 07939 084159 (Mobile) Fax : 01235 445720 From peter.willendrup at risoe.dk Wed Sep 17 10:18:30 2003 From: peter.willendrup at risoe.dk (Peter Kjaer Willendrup) Date: Wed, 17 Sep 2003 10:18:30 +0200 (CEST) Subject: [neutron-mc] V_sample.comp In-Reply-To: <37CAC51AC5C1D211966100A0C9ED000A035D6C86@exchange07.rl.ac.uk> Message-ID: Hi Dickon, On Tue, 16 Sep 2003, Champion, JDM (Dickon) wrote: > and it will never consider the possibility of a cuboid sample. True... :( > a fix for this problem and to prevent the future confusion of others might > be a check for the declaration of the xwidth, yheight, zthick etc.... > instead Thanks for pointing the problem out! We will include relevant modifications in the next release - I will also go through related components to check for similar flaws. Thanks again, Peter -- ------------------------------------- Peter Kjaer Willendrup, Cand. Scient Phone: (+45) 46 77 58 62 email: peter.willendrup at risoe.dk -------------------------------------