From paul.henry at esss.se Wed Oct 15 11:46:05 2014 From: paul.henry at esss.se (Paul Henry) Date: Wed, 15 Oct 2014 09:46:05 +0000 Subject: [mcstas-users] McStas 2.1 upgrade issues from McStas 2.0 Message-ID: Dear McStas team, I have just upgraded from McStas 2.0 to 2.1 in order to use the new ESS source information. I run everything through the mcgui interface and everything loads normally and I tested with my existing files and got the same results as previous version. However, if I implement the new ESS source in a simulation file I get a whole of errors when I try to compile. It appears that the source component is not there as it questions a lot of the variables as not existing ? examples in screen grab attached. When I use the run command button it starts reading the configuration information as follows: mcrun: reading local mcstas configuration from /Users/paulhenry/.mcstas/mccode_config.perl /usr/local/bin/mcrun-2.0: reading local mcstas configuration from /Users/paulhenry/.mcstas/mccode_config.perl Running simulation '/Users/paulhenry/McStas/ESSinstrument/20140318_ESS_fulldetector.out' ? Looking at my preferences I see that the runtime tool options still uses the mcrun-2.0 command. If I change this to mcrun-2.1 and try to compile I get an error that the execution of mcrun-2.1 failed. I assume this means that I am not actually using the Mcstas2.1 components or libraries as a result. How do you suggest I get around this? Regards, Paul Machine is a Macbook Pro 2.7GhZ running OSX10.9.5 I have Xquartz version 2.7.6 ______________________________________ Prof. Paul Henry Instrument Scientist - Diffraction European Spallation Source ESS AB P.O Box 176, SE-221 00 Lund, Sweden Visiting address: Tunav?gen 24, Lund Switchboard: +46 46 888 00 00 Phone: +46 46 888 30 82 Mobile: +46 721 79 20 82 E-mail: paul.henry at esss.se www.esss.se Adjungerad professor i Neutronspridning (Adjunct Professor in Neutron scattering - Diffraction) [cid:E0E91C9F-7928-49BD-9241-4634170BD1AD] Chalmers tekniska h?gskola, Institutionen f?r kemi- och bioteknik, Kemig?rden 4, SE-412 96 G?teborg, Sweden https://www.chalmers.se/chem/SV/ ______________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 7EE23DA1-72CB-4F80-B9DC-58C5E179DA0F[43].png Type: image/png Size: 2674 bytes Desc: 7EE23DA1-72CB-4F80-B9DC-58C5E179DA0F[43].png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mcstas_error.tiff Type: image/tiff Size: 186266 bytes Desc: Mcstas_error.tiff URL: From pkwi at fysik.dtu.dk Wed Oct 15 12:03:17 2014 From: pkwi at fysik.dtu.dk (=?Windows-1252?Q?Peter_Kj=E6r_Willendrup?=) Date: Wed, 15 Oct 2014 10:03:17 +0000 Subject: [mcstas-users] McStas 2.1 upgrade issues from McStas 2.0 In-Reply-To: References: Message-ID: <2420DBDB-DCEC-41B7-AF61-91A491128988@fysik.dtu.dk> Dear Paul, Due to changes in the tool-layer structure (again, sorry!!) we are back to using commands without version-number suffix, i.e.: McStas itself: mcstas Perl tool layer: mcrun, mcplot, mcdisplay, mcdisplay Python tool layer: mcrun-py mcplot-matplotlib-py mcplot-chaco-py mcdisplay-matplotlib-py mcdisplay-vtk-py mcdisplay-r-py mcdisplay-x3d-py Everything should be OK if you either a) Modify your local mccode_config.perl to use mcrun, mcplot, mcdisplay b) Simply move the mccode_config.perl out of the way - then the system-wide defaults should work. Most sorry for the inconvenience! Best and hope this helps? Peter On 15 Oct 2014, at 11:46 , Paul Henry > wrote: Dear McStas team, I have just upgraded from McStas 2.0 to 2.1 in order to use the new ESS source information. I run everything through the mcgui interface and everything loads normally and I tested with my existing files and got the same results as previous version. However, if I implement the new ESS source in a simulation file I get a whole of errors when I try to compile. It appears that the source component is not there as it questions a lot of the variables as not existing ? examples in screen grab attached. When I use the run command button it starts reading the configuration information as follows: mcrun: reading local mcstas configuration from /Users/paulhenry/.mcstas/mccode_config.perl /usr/local/bin/mcrun-2.0: reading local mcstas configuration from /Users/paulhenry/.mcstas/mccode_config.perl Running simulation '/Users/paulhenry/McStas/ESSinstrument/20140318_ESS_fulldetector.out' ? Looking at my preferences I see that the runtime tool options still uses the mcrun-2.0 command. If I change this to mcrun-2.1 and try to compile I get an error that the execution of mcrun-2.1 failed. I assume this means that I am not actually using the Mcstas2.1 components or libraries as a result. How do you suggest I get around this? Regards, Paul Machine is a Macbook Pro 2.7GhZ running OSX10.9.5 I have Xquartz version 2.7.6 ______________________________________ Prof. Paul Henry Instrument Scientist - Diffraction European Spallation Source ESS AB P.O Box 176, SE-221 00 Lund, Sweden Visiting address: Tunav?gen 24, Lund Switchboard: +46 46 888 00 00 Phone: +46 46 888 30 82 Mobile: +46 721 79 20 82 E-mail: paul.henry at esss.se www.esss.se Adjungerad professor i Neutronspridning (Adjunct Professor in Neutron scattering - Diffraction) <7EE23DA1-72CB-4F80-B9DC-58C5E179DA0F[43].png> Chalmers tekniska h?gskola, Institutionen f?r kemi- och bioteknik, Kemig?rden 4, SE-412 96 G?teborg, Sweden https://www.chalmers.se/chem/SV/ ______________________________________ _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkwi at fysik.dtu.dk Mon Oct 20 20:19:09 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Mon, 20 Oct 2014 18:19:09 +0000 Subject: [mcstas-users] Mac OS X Yosemite and McStas: Hold your horses! Message-ID: <42C85C95-639D-4675-BB42-504F8D4BA750@fysik.dtu.dk> !! This email is relevant for Mac OS users of McStas only!! Dear all, As at least one unfortunate McStas user (besides myself ;-) ) has experienced, upgrading to Mac OS X Yosemite 10.10 removes Perl 5.12, which the Perl tools in McStas 2.1 distributed for Maverics rely on... The only way to get the Perl-tools working again is to recompile both perl-Tk, perl-pgplot, PDL and pgplot? Not a completely trivial exercise, but can be done... I am in the process of putting together a ?plug and play' solution, but it may take one or two weeks. In conclusion: If you need a fully functional McStas, please do not upgrade to Yosemite just yet... :-) All the best, Peter Willendrup Peter Kj?r Willendrup Senior Research Engineer, Special Advisor DTU Physics Technical University of Denmark [cid:image002.gif at 01CCCAF1.5E6331F0] Department of Physics Fysikvej Building 307 DK-2800 Kongens Lyngby Direct +45 2125 4612 Mobil +45 2125 4612 Fax +45 4593 2399 pkwi at fysik.dtu.dk -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 58 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1055 bytes Desc: image002.gif URL: From pkwi at fysik.dtu.dk Wed Oct 22 12:51:13 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Wed, 22 Oct 2014 10:51:13 +0000 Subject: [mcstas-users] Mac OS X Yosemite and McStas: Hold your horses! In-Reply-To: <42C85C95-639D-4675-BB42-504F8D4BA750@fysik.dtu.dk> References: <42C85C95-639D-4675-BB42-504F8D4BA750@fysik.dtu.dk> Message-ID: <2A507D05-EA47-4D60-A622-2F57C4251BA5@fysik.dtu.dk> Dear all, A tested download bundle for Mac OS X 10.10 Yosemite has been uploaded to http://downloads.mcstas.org/mcstas-2.1/mac/ The enclosed McStas has a limited set of differences/bugfixes wrt. the official McStas 2.1 released in september, but should generally behave the same. A few details are pointed out in the README.TXT of the tar.gz archive, listed below. Best, Peter Willendrup Peter Kj?r Willendrup Senior Research Engineer, Special Advisor DTU Physics Technical University of Denmark [cid:image002.gif at 01CCCAF1.5E6331F0] Department of Physics Fysikvej Building 307 DK-2800 Kongens Lyngby Direct +45 2125 4612 Mobil +45 2125 4612 Fax +45 4593 2399 pkwi at fysik.dtu.dk ____________________________________________________________________________ Installation README for McStas 2.1 on Mac OS X 10.10 Yosemite (This is a "respin" of McStas 2.1 done 40 days later than the other 2.1 installation packages after Yosemite arrival...) A) ESSENTIAL PREREQUISITES: Xcode from Apple, either installed via DVD or from the App Store Xquartz from http://xquartz.macosforge.org/landing/ B) Run the metapackage for installing the package - the defaults provide the essential bits to run McStas with the Perl tools as well as the gcc and gfortran compilers from hpc.sourceforge.net, installed to /usr/local. Optionally select openmpi for installation, this will also be installed to /usr/local. NOTE: The included pgplot / mcplot only produces PostSript graphics, sorry! This may be remedied in connection with the next McStas release... Follow the URL at the end of this document for information on the Python tools McStas-2.1 is now available in /Applications/McStas-2.1.app - and can be removed by dragging that bundle to the trash For installing Python-tools and their dependencies, please follow instructions at http://www.mcstas.org/download/install_mac_os_x/ On 20 Oct 2014, at 20:19 , Peter Kj?r Willendrup > wrote: !! This email is relevant for Mac OS users of McStas only!! Dear all, As at least one unfortunate McStas user (besides myself ;-) ) has experienced, upgrading to Mac OS X Yosemite 10.10 removes Perl 5.12, which the Perl tools in McStas 2.1 distributed for Maverics rely on... The only way to get the Perl-tools working again is to recompile both perl-Tk, perl-pgplot, PDL and pgplot? Not a completely trivial exercise, but can be done... I am in the process of putting together a ?plug and play' solution, but it may take one or two weeks. In conclusion: If you need a fully functional McStas, please do not upgrade to Yosemite just yet... :-) All the best, Peter Willendrup Peter Kj?r Willendrup Senior Research Engineer, Special Advisor DTU Physics Technical University of Denmark Department of Physics Fysikvej Building 307 DK-2800 Kongens Lyngby Direct +45 2125 4612 Mobil +45 2125 4612 Fax +45 4593 2399 pkwi at fysik.dtu.dk _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 58 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1055 bytes Desc: image002.gif URL: From anna.fedrigo at fi.isc.cnr.it Wed Nov 19 15:49:07 2014 From: anna.fedrigo at fi.isc.cnr.it (Anna Fedrigo) Date: Wed, 19 Nov 2014 15:49:07 +0100 Subject: [mcstas-users] thermal moderator Message-ID: Dear mcstas users, I finally moved to the new mcstas version and I have problems with the moderator. For the selection of the thermal source is this command (sourcedef="TDR") enough? I managed to get only a cold source. Which parameters should I use? Sorry but it's not very clear from the manual to me. Best regards, Anna *___**___**___**_**__**_**__**__**__**__**__**__**__**__**__**___* *Anna Fedrigo* PhD Student Consiglio Nazionale delle Ricerche Istituto dei Sistemi Complessi Via Madonna del Piano, 10 50019 Sesto Fiorentino (Italy) Phone: +39 055 522 6631 E_mail: anna.fedrigo at fi.isc.cnr.it -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkwi at fysik.dtu.dk Thu Nov 20 10:48:37 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Thu, 20 Nov 2014 09:48:37 +0000 Subject: [mcstas-users] thermal moderator In-Reply-To: References: Message-ID: <5A9FB196-E2DE-4B15-8CCC-898DA8B0B942@fysik.dtu.dk> Dear Anna, Sorry for the delay in responding - I had other urgent matters to attend. My first comment is that the ?TDR? formulation is no longer very relevant. The ?2014? realises the brilliances as function of height between 1 and 12 cm, including both the ?pancake? and ?volume? moderator - and gives BOTH the cold and thermal spectra with tunable statistics, i.e. - cold_frac=1 gives cold only - cold_frac=0 gives thermal only - 0 < cold_frac < 1 chooses the any fraction in between Please note however that the proposed ?lower moderator? is NOT described in McStas yet, but the upper moderator at a relevant height should give a good approximation. Please find attached the instrument file ESS_Brilliance_2014.instr which shows how to run the ?2014? source. The instrument is also - available within McStas 2.1 - released separately for use with older versions of the code on July 17th, 2014, see http://www.mcstas.org/download/share I also attach a presentation from the ICANS conference by Troels Sch?nfeldt who did all the hard work of characterising the ESS source and extracting parameters for McStas. (Troels is cc: here, jointly employed at DTU Nutech & ESS neutronics group) Troels is in the process of preparing a paper with detailed information. You are welcome to also ask him in case of questions or for further information. Best, Peter Peter Kj?r Willendrup Senior Research Engineer, Special Advisor DTU Physics [cid:c99f6005-a56f-4672-bfe8-f6c6cbc364ef at win.dtu.dk] Technical University of Denmark [cid:ae7dea5d-27e2-4933-8ae9-fcea404be25a at win.dtu.dk] Department of Physics Fysikvej Building 307 DK-2800 Kongens Lyngby Direct +45 2125 4612 Mobil +45 2125 4612 Fax +45 4593 2399 pkwi at fysik.dtu.dk On 19 Nov 2014, at 15:49 , Anna Fedrigo > wrote: Dear mcstas users, I finally moved to the new mcstas version and I have problems with the moderator. For the selection of the thermal source is this command (sourcedef="TDR") enough? I managed to get only a cold source. Which parameters should I use? Sorry but it's not very clear from the manual to me. Best regards, Anna __________________________________ Anna Fedrigo PhD Student Consiglio Nazionale delle Ricerche Istituto dei Sistemi Complessi Via Madonna del Piano, 10 50019 Sesto Fiorentino (Italy) Phone: +39 055 522 6631 E_mail: anna.fedrigo at fi.isc.cnr.it _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 58 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1055 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ESS_Brilliance_2014.instr Type: application/octet-stream Size: 6518 bytes Desc: ESS_Brilliance_2014.instr URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Troels_schonfeldt_ICANS2014.pdf Type: application/pdf Size: 919644 bytes Desc: Troels_schonfeldt_ICANS2014.pdf URL: From sylvain.desert at cea.fr Tue Nov 25 10:49:30 2014 From: sylvain.desert at cea.fr (DESERT Sylvain) Date: Tue, 25 Nov 2014 09:49:30 +0000 Subject: [mcstas-users] Making a component GROUP-compatible Message-ID: Hi, I am using the contributed component Guide_four_side from T. Panzner of PSI which doesn't support the GROUPing method. My need is to simulate an elliptic guide where both vertical walls don't share the same focal point. Guide_anyshape is also not a solution since it's not possible to get different m-values for each side of the guide. Any idea how to make the component GROUP compliant? Any other idea how to simulate such a guide? Best wishes, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkwi at fysik.dtu.dk Tue Nov 25 11:07:06 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Tue, 25 Nov 2014 10:07:06 +0000 Subject: [mcstas-users] Making a component GROUP-compatible In-Reply-To: References: Message-ID: Dear Sylvain, I would suggest you take a look at Elliptic_guide_gravity by Henrik Bo Hoffmann Carlsen and Mads Bertelsen from Uni Copenhagen. If I remember correctly, it has exactly the properties you are looking for (and further takes gravity into account). It is used in the following example instruments included with the last McStas release: Reflectometer.instr Test_Guides.instr Test_Guides_Curved.instr Mads is the ?expert? on using this component for various complex arrangements, I am putting him cc: here in case you need further, specific help. Best, Peter On 25 Nov 2014, at 10:49 , DESERT Sylvain > wrote: Hi, I am using the contributed component Guide_four_side from T. Panzner of PSI which doesn?t support the GROUPing method. My need is to simulate an elliptic guide where both vertical walls don?t share the same focal point. Guide_anyshape is also not a solution since it?s not possible to get different m-values for each side of the guide. Any idea how to make the component GROUP compliant? Any other idea how to simulate such a guide? Best wishes, Sylvain _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.dalgliesh at stfc.ac.uk Tue Nov 25 12:13:24 2014 From: robert.dalgliesh at stfc.ac.uk (robert.dalgliesh at stfc.ac.uk) Date: Tue, 25 Nov 2014 11:13:24 +0000 Subject: [mcstas-users] mantid output test Message-ID: <9FD256ED3764AA40BD335311A4123FA0457941D4@EXCHMBX03.fed.cclrc.ac.uk> Hi, I've been brave and tried the Mantid output option in mcstas this morning. I'm using mcstas 2.1 and mantid 3.2.1 on a Redhat 6.4 box. There seems to be no problem with the installed NeXus and hdf libraries the simulation runs fine. The problem comes when I try following the instructions to generate the IDF file. This is the simple instrument I've tried some of the variables would be picked up in later components. /* Change name of instrument and input parameters with default values */ DEFINE INSTRUMENT test(s1=0.03,s2=0.02,s3=0.008,bs=0.05,cdel=0.0,sampdet=4.406,lmin=0.5,lmax=13.0,dang=0.0) DECLARE %{ %} INITIALIZE %{ %} TRACE COMPONENT Origin = Progress_bar() AT (0,0,0) ABSOLUTE COMPONENT sourceMantid = ISIS_moderator( Face = "hydrogen", Lmax = lmax, Lmin = lmin, dist = 3.7, focus_xw = 0.03, focus_yh = 0.03, xwidth = 0.083, yheight = 0.033, CAngle = 0.0, SAC = 1) AT (0.0, 0.0, 0.0) RELATIVE PREVIOUS COMPONENT guide1 = Guide( w1 = 0.03, h1 = 0.03, w2 = 0.03, h2 = 0.03, l = 5.3, m = 3.0) AT (0.0, 0.0, 3.7) RELATIVE Origin COMPONENT disk1 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = 10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.689) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT disk2 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = -10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.739) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT nD_Mantid_0 = Monitor_nD( options ="mantid square x limits =[-0.0155 0.0155] bins=1 y limits =[-0.0155 0.0155] bins=1, neutron pixel t, list all neutrons", xmin = -0.0155, xmax = 0.0155, ymin = -0.0155, ymax = 0.0155, restore_neutron = 1, filename = "monitor1Events.dat") AT (0, 0, 9.8195) RELATIVE sourceMantid The xml file resulting from this when I run the command mcdisplay --format=Mantid Test_Mantid.instr -n0 after compiling chucks out this message Illegal division by zero at /usr/local/bin/mcdisplay line 391, line 73. And proceeds to dump an enormously long xml file with a huge number of weird repeated components. Any hints as to what is messing things up would be greatly appreciated. Thanks Rob =================================== Dr. Robert Dalgliesh ISIS STFC Rutherford Appleton Laboratory R3 1.29 Harwell Oxford Didcot OX11 0QX Office Tel: +44 (0) 1235 445687 or OffSpec Instrument: +44 (0) 1235 567045 Internal Mobile Extension: 1176 e-mail: robert.dalgliesh at stfc.ac.uk -- Scanned by iCritical. -------------- next part -------------- An HTML attachment was scrubbed... URL: From farhi at ill.fr Tue Nov 25 12:33:35 2014 From: farhi at ill.fr (Emmanuel FARHI) Date: Tue, 25 Nov 2014 12:33:35 +0100 (CET) Subject: [mcstas-users] Making a component GROUP-compatible In-Reply-To: References: Message-ID: Hello Sylvain and Peter, I think the only requirement for the GROUP to work is 1- to ensure that all component internal variables (those in DECLARE) are also in OUTPUT PARAMETERS. 2- to ensure that in case of interaction, the SCATTER macro is used to indicate 'this is the one to use in the GROUP'. You may, I think, fix these in the code. If it works, think to send back the corrected component so that next time you and other users can employ the component directly. Emmanuel. On Tue, November 25, 2014 11:07, Peter Kj??r Willendrup wrote: > Dear Sylvain, > > I would suggest you take a look at Elliptic_guide_gravity by Henrik Bo > Hoffmann Carlsen and Mads Bertelsen from Uni Copenhagen. If I remember > correctly, it has exactly the properties you are looking for (and further > takes gravity into account). > > It is used in the following example instruments included with the last > McStas release: > > Reflectometer.instr > Test_Guides.instr > Test_Guides_Curved.instr > > Mads is the ???expert??? on using this component for various complex > arrangements, I am putting him cc: here in case you need further, specific > help. > > Best, > > Peter > > > > On 25 Nov 2014, at 10:49 , DESERT Sylvain > > wrote: > > Hi, > I am using the contributed component Guide_four_side from T. Panzner of > PSI which doesn???t support the GROUPing method. > My need is to simulate an elliptic guide where both vertical walls don???t > share the same focal point. > Guide_anyshape is also not a solution since it???s not possible to get > different m-values for each side of the guide. > Any idea how to make the component GROUP compliant? > Any other idea how to simulate such a guide? > Best wishes, > Sylvain > > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > -- FARHI Emmanuel Groupe DS/CS, ILL4/156, Tel 04 76 20 71 35 ILL, Grenoble From mads.bertelsen at gmail.com Tue Nov 25 12:57:08 2014 From: mads.bertelsen at gmail.com (Mads Bertelsen) Date: Tue, 25 Nov 2014 12:57:08 +0100 Subject: [mcstas-users] Making a component GROUP-compatible In-Reply-To: References: Message-ID: Dear Sylvain I do not believe it will be easy to modify the code so that it can be used in a group for your purpose. Henrik Carlsen wrote the component, while I have tested it. The initial ambition was to allow for transparent walls, but it proved quite difficult with the way he set up the code, so I think it was abandoned, I was never asked to test it anyway. In order to make it work in a group, this transparent option would have to work. I do however see a lot of traces of this transparent option in the code, but not in the documentation, so it may be possible to get it working. I will ask Henrik the next time I see him. The remaining option is to modify the component directly to use different focal points for each wall actually seems easier, as the code is nicely split up for interactions with the 4 different sides of the ellipse. Using this method would require the left and right side of the ellipse to start at the same z coordinate. I am looking at the version I believe is the newest called 89beta.comp. McStas 2.0 contains an old version, was it updated for McStas 2.1? Best regards, Mads On 25. Nov, 2014, at 12:33 , Emmanuel FARHI wrote: > Hello Sylvain and Peter, > > I think the only requirement for the GROUP to work is > 1- to ensure that all component internal variables (those in DECLARE) are > also in OUTPUT PARAMETERS. > 2- to ensure that in case of interaction, the SCATTER macro is used to > indicate 'this is the one to use in the GROUP'. > > You may, I think, fix these in the code. > If it works, think to send back the corrected component so that next time > you and other users can employ the component directly. > > Emmanuel. > > On Tue, November 25, 2014 11:07, Peter Kj??r Willendrup wrote: >> Dear Sylvain, >> >> I would suggest you take a look at Elliptic_guide_gravity by Henrik Bo >> Hoffmann Carlsen and Mads Bertelsen from Uni Copenhagen. If I remember >> correctly, it has exactly the properties you are looking for (and further >> takes gravity into account). >> >> It is used in the following example instruments included with the last >> McStas release: >> >> Reflectometer.instr >> Test_Guides.instr >> Test_Guides_Curved.instr >> >> Mads is the ???expert??? on using this component for various complex >> arrangements, I am putting him cc: here in case you need further, specific >> help. >> >> Best, >> >> Peter >> >> >> >> On 25 Nov 2014, at 10:49 , DESERT Sylvain >> > wrote: >> >> Hi, >> I am using the contributed component Guide_four_side from T. Panzner of >> PSI which doesn???t support the GROUPing method. >> My need is to simulate an elliptic guide where both vertical walls don???t >> share the same focal point. >> Guide_anyshape is also not a solution since it???s not possible to get >> different m-values for each side of the guide. >> Any idea how to make the component GROUP compliant? >> Any other idea how to simulate such a guide? >> Best wishes, >> Sylvain >> >> _______________________________________________ >> mcstas-users mailing list >> mcstas-users at mcstas.org >> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >> >> _______________________________________________ >> mcstas-users mailing list >> mcstas-users at mcstas.org >> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >> > > > -- > FARHI Emmanuel > Groupe DS/CS, ILL4/156, Tel 04 76 20 71 35 > ILL, Grenoble > From pkwi at fysik.dtu.dk Tue Nov 25 13:12:05 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Tue, 25 Nov 2014 12:12:05 +0000 Subject: [mcstas-users] mantid output test In-Reply-To: <9FD256ED3764AA40BD335311A4123FA0457941D4@EXCHMBX03.fed.cclrc.ac.uk> References: <9FD256ED3764AA40BD335311A4123FA0457941D4@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: <4D0598D6-935F-4E50-ABF1-FB0F3147508C@fysik.dtu.dk> Dear Rob, You have indeed stumbled across a proper bug - it seems what I implemented in mcdisplay for generation of the IDF implicitly assumes n>1 bins? :-) I will test for the special case of n=1 bins in the next released mcdisplay. I am able to generate the IDF and NeXus output if I define an event monitor with 2x2 bins which loads OK into Mantid. (My Mantid then on the other hand crashes when I attempt to show the instrument? This may or may not be my recently updated Mac OS X Yosemite, not clear?. - But ?color fill plot? can be done) Best, Peter On 25 Nov 2014, at 12:13 , robert.dalgliesh at stfc.ac.uk wrote: Hi, I?ve been brave and tried the Mantid output option in mcstas this morning. I?m using mcstas 2.1 and mantid 3.2.1 on a Redhat 6.4 box. There seems to be no problem with the installed NeXus and hdf libraries the simulation runs fine. The problem comes when I try following the instructions to generate the IDF file. This is the simple instrument I?ve tried some of the variables would be picked up in later components. /* Change name of instrument and input parameters with default values */ DEFINE INSTRUMENT test(s1=0.03,s2=0.02,s3=0.008,bs=0.05,cdel=0.0,sampdet=4.406,lmin=0.5,lmax=13.0,dang=0.0) DECLARE %{ %} INITIALIZE %{ %} TRACE COMPONENT Origin = Progress_bar() AT (0,0,0) ABSOLUTE COMPONENT sourceMantid = ISIS_moderator( Face = "hydrogen", Lmax = lmax, Lmin = lmin, dist = 3.7, focus_xw = 0.03, focus_yh = 0.03, xwidth = 0.083, yheight = 0.033, CAngle = 0.0, SAC = 1) AT (0.0, 0.0, 0.0) RELATIVE PREVIOUS COMPONENT guide1 = Guide( w1 = 0.03, h1 = 0.03, w2 = 0.03, h2 = 0.03, l = 5.3, m = 3.0) AT (0.0, 0.0, 3.7) RELATIVE Origin COMPONENT disk1 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = 10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.689) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT disk2 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = -10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.739) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT nD_Mantid_0 = Monitor_nD( options ="mantid square x limits =[-0.0155 0.0155] bins=1 y limits =[-0.0155 0.0155] bins=1, neutron pixel t, list all neutrons", xmin = -0.0155, xmax = 0.0155, ymin = -0.0155, ymax = 0.0155, restore_neutron = 1, filename = "monitor1Events.dat") AT (0, 0, 9.8195) RELATIVE sourceMantid The xml file resulting from this when I run the command mcdisplay --format=Mantid Test_Mantid.instr -n0 after compiling chucks out this message Illegal division by zero at /usr/local/bin/mcdisplay line 391, line 73. And proceeds to dump an enormously long xml file with a huge number of weird repeated components. Any hints as to what is messing things up would be greatly appreciated. Thanks Rob =================================== Dr. Robert Dalgliesh ISIS STFC Rutherford Appleton Laboratory R3 1.29 Harwell Oxford Didcot OX11 0QX Office Tel: +44 (0) 1235 445687 or OffSpec Instrument: +44 (0) 1235 567045 Internal Mobile Extension: 1176 e-mail: robert.dalgliesh at stfc.ac.uk -- Scanned by iCritical. _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkwi at fysik.dtu.dk Tue Nov 25 13:16:12 2014 From: pkwi at fysik.dtu.dk (=?iso-8859-1?Q?Peter_Kj=E6r_Willendrup?=) Date: Tue, 25 Nov 2014 12:16:12 +0000 Subject: [mcstas-users] Making a component GROUP-compatible In-Reply-To: References: Message-ID: <633DF9AD-3724-4B95-B654-5037F7181E5D@fysik.dtu.dk> Dear Mads, I am not aware if the Version tag of the component can be trusted to identify the internal revisions you and Henrik work with? If so, what McStas 2.1 contains is Version: 0.88. (Corresponding to 88beta.comp maybe?) Best, Peter > On 25 Nov 2014, at 12:57 , Mads Bertelsen wrote: > > Dear Sylvain > > I do not believe it will be easy to modify the code so that it can be used in a group for your purpose. Henrik Carlsen wrote the component, while I have tested it. The initial ambition was to allow for transparent walls, but it proved quite difficult with the way he set up the code, so I think it was abandoned, I was never asked to test it anyway. In order to make it work in a group, this transparent option would have to work. I do however see a lot of traces of this transparent option in the code, but not in the documentation, so it may be possible to get it working. I will ask Henrik the next time I see him. > > The remaining option is to modify the component directly to use different focal points for each wall actually seems easier, as the code is nicely split up for interactions with the 4 different sides of the ellipse. Using this method would require the left and right side of the ellipse to start at the same z coordinate. > > I am looking at the version I believe is the newest called 89beta.comp. McStas 2.0 contains an old version, was it updated for McStas 2.1? > > Best regards, > Mads > > On 25. Nov, 2014, at 12:33 , Emmanuel FARHI wrote: > >> Hello Sylvain and Peter, >> >> I think the only requirement for the GROUP to work is >> 1- to ensure that all component internal variables (those in DECLARE) are >> also in OUTPUT PARAMETERS. >> 2- to ensure that in case of interaction, the SCATTER macro is used to >> indicate 'this is the one to use in the GROUP'. >> >> You may, I think, fix these in the code. >> If it works, think to send back the corrected component so that next time >> you and other users can employ the component directly. >> >> Emmanuel. >> >> On Tue, November 25, 2014 11:07, Peter Kj??r Willendrup wrote: >>> Dear Sylvain, >>> >>> I would suggest you take a look at Elliptic_guide_gravity by Henrik Bo >>> Hoffmann Carlsen and Mads Bertelsen from Uni Copenhagen. If I remember >>> correctly, it has exactly the properties you are looking for (and further >>> takes gravity into account). >>> >>> It is used in the following example instruments included with the last >>> McStas release: >>> >>> Reflectometer.instr >>> Test_Guides.instr >>> Test_Guides_Curved.instr >>> >>> Mads is the ??oexpert??? on using this component for various complex >>> arrangements, I am putting him cc: here in case you need further, specific >>> help. >>> >>> Best, >>> >>> Peter >>> >>> >>> >>> On 25 Nov 2014, at 10:49 , DESERT Sylvain >>> > wrote: >>> >>> Hi, >>> I am using the contributed component Guide_four_side from T. Panzner of >>> PSI which doesn??Tt support the GROUPing method. >>> My need is to simulate an elliptic guide where both vertical walls don??Tt >>> share the same focal point. >>> Guide_anyshape is also not a solution since it??Ts not possible to get >>> different m-values for each side of the guide. >>> Any idea how to make the component GROUP compliant? >>> Any other idea how to simulate such a guide? >>> Best wishes, >>> Sylvain >>> >>> _______________________________________________ >>> mcstas-users mailing list >>> mcstas-users at mcstas.org >>> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >>> >>> _______________________________________________ >>> mcstas-users mailing list >>> mcstas-users at mcstas.org >>> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >>> >> >> >> -- >> FARHI Emmanuel >> Groupe DS/CS, ILL4/156, Tel 04 76 20 71 35 >> ILL, Grenoble >> > From robert.dalgliesh at stfc.ac.uk Tue Nov 25 13:23:00 2014 From: robert.dalgliesh at stfc.ac.uk (robert.dalgliesh at stfc.ac.uk) Date: Tue, 25 Nov 2014 12:23:00 +0000 Subject: [mcstas-users] mantid output test In-Reply-To: <4D0598D6-935F-4E50-ABF1-FB0F3147508C@fysik.dtu.dk> References: <9FD256ED3764AA40BD335311A4123FA0457941D4@EXCHMBX03.fed.cclrc.ac.uk> <4D0598D6-935F-4E50-ABF1-FB0F3147508C@fysik.dtu.dk> Message-ID: <9FD256ED3764AA40BD335311A4123FA0457942D3@EXCHMBX03.fed.cclrc.ac.uk> Thanks Peter, That worked. Incidentally it still took a bit of hacking to install mcstas 2.1 from rpm. The soft links still point at some strange places. Thanks again Rob From: Peter Kj?r Willendrup [mailto:pkwi at fysik.dtu.dk] Sent: 25 November 2014 12:12 To: Dalgliesh, Robert (STFC,RAL,ISIS) Cc: mcstas-users at mcstas.org Subject: Re: [mcstas-users] mantid output test Dear Rob, You have indeed stumbled across a proper bug - it seems what I implemented in mcdisplay for generation of the IDF implicitly assumes n>1 bins? :-) I will test for the special case of n=1 bins in the next released mcdisplay. I am able to generate the IDF and NeXus output if I define an event monitor with 2x2 bins which loads OK into Mantid. (My Mantid then on the other hand crashes when I attempt to show the instrument? This may or may not be my recently updated Mac OS X Yosemite, not clear?. - But ?color fill plot? can be done) Best, Peter On 25 Nov 2014, at 12:13 , robert.dalgliesh at stfc.ac.uk wrote: Hi, I?ve been brave and tried the Mantid output option in mcstas this morning. I?m using mcstas 2.1 and mantid 3.2.1 on a Redhat 6.4 box. There seems to be no problem with the installed NeXus and hdf libraries the simulation runs fine. The problem comes when I try following the instructions to generate the IDF file. This is the simple instrument I?ve tried some of the variables would be picked up in later components. /* Change name of instrument and input parameters with default values */ DEFINE INSTRUMENT test(s1=0.03,s2=0.02,s3=0.008,bs=0.05,cdel=0.0,sampdet=4.406,lmin=0.5,lmax=13.0,dang=0.0) DECLARE %{ %} INITIALIZE %{ %} TRACE COMPONENT Origin = Progress_bar() AT (0,0,0) ABSOLUTE COMPONENT sourceMantid = ISIS_moderator( Face = "hydrogen", Lmax = lmax, Lmin = lmin, dist = 3.7, focus_xw = 0.03, focus_yh = 0.03, xwidth = 0.083, yheight = 0.033, CAngle = 0.0, SAC = 1) AT (0.0, 0.0, 0.0) RELATIVE PREVIOUS COMPONENT guide1 = Guide( w1 = 0.03, h1 = 0.03, w2 = 0.03, h2 = 0.03, l = 5.3, m = 3.0) AT (0.0, 0.0, 3.7) RELATIVE Origin COMPONENT disk1 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = 10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.689) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT disk2 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = -10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.739) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT nD_Mantid_0 = Monitor_nD( options ="mantid square x limits =[-0.0155 0.0155] bins=1 y limits =[-0.0155 0.0155] bins=1, neutron pixel t, list all neutrons", xmin = -0.0155, xmax = 0.0155, ymin = -0.0155, ymax = 0.0155, restore_neutron = 1, filename = "monitor1Events.dat") AT (0, 0, 9.8195) RELATIVE sourceMantid The xml file resulting from this when I run the command mcdisplay --format=Mantid Test_Mantid.instr -n0 after compiling chucks out this message Illegal division by zero at /usr/local/bin/mcdisplay line 391, line 73. And proceeds to dump an enormously long xml file with a huge number of weird repeated components. Any hints as to what is messing things up would be greatly appreciated. Thanks Rob =================================== Dr. Robert Dalgliesh ISIS STFC Rutherford Appleton Laboratory R3 1.29 Harwell Oxford Didcot OX11 0QX Office Tel: +44 (0) 1235 445687 or OffSpec Instrument: +44 (0) 1235 567045 Internal Mobile Extension: 1176 e-mail: robert.dalgliesh at stfc.ac.uk -- Scanned by iCritical. _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkwi at fysik.dtu.dk Tue Nov 25 13:43:10 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Tue, 25 Nov 2014 12:43:10 +0000 Subject: [mcstas-users] mantid output test In-Reply-To: <9FD256ED3764AA40BD335311A4123FA0457942D3@EXCHMBX03.fed.cclrc.ac.uk> References: <9FD256ED3764AA40BD335311A4123FA0457941D4@EXCHMBX03.fed.cclrc.ac.uk> <4D0598D6-935F-4E50-ABF1-FB0F3147508C@fysik.dtu.dk> <9FD256ED3764AA40BD335311A4123FA0457942D3@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: <1A6D3480-0282-4B84-A1ED-A8BDB6BF7A43@fysik.dtu.dk> Good to hear that. :-) In regard to the rpm?s - where did they point? and where would you have liked to have them point? (Then there is a chance things will be OK for 2.2? ;-) ) Peter On 25 Nov 2014, at 13:23 , robert.dalgliesh at stfc.ac.uk wrote: Thanks Peter, That worked. Incidentally it still took a bit of hacking to install mcstas 2.1 from rpm. The soft links still point at some strange places. Thanks again Rob From: Peter Kj?r Willendrup [mailto:pkwi at fysik.dtu.dk] Sent: 25 November 2014 12:12 To: Dalgliesh, Robert (STFC,RAL,ISIS) Cc: mcstas-users at mcstas.org Subject: Re: [mcstas-users] mantid output test Dear Rob, You have indeed stumbled across a proper bug - it seems what I implemented in mcdisplay for generation of the IDF implicitly assumes n>1 bins? :-) I will test for the special case of n=1 bins in the next released mcdisplay. I am able to generate the IDF and NeXus output if I define an event monitor with 2x2 bins which loads OK into Mantid. (My Mantid then on the other hand crashes when I attempt to show the instrument? This may or may not be my recently updated Mac OS X Yosemite, not clear?. - But ?color fill plot? can be done) Best, Peter On 25 Nov 2014, at 12:13 , robert.dalgliesh at stfc.ac.uk wrote: Hi, I?ve been brave and tried the Mantid output option in mcstas this morning. I?m using mcstas 2.1 and mantid 3.2.1 on a Redhat 6.4 box. There seems to be no problem with the installed NeXus and hdf libraries the simulation runs fine. The problem comes when I try following the instructions to generate the IDF file. This is the simple instrument I?ve tried some of the variables would be picked up in later components. /* Change name of instrument and input parameters with default values */ DEFINE INSTRUMENT test(s1=0.03,s2=0.02,s3=0.008,bs=0.05,cdel=0.0,sampdet=4.406,lmin=0.5,lmax=13.0,dang=0.0) DECLARE %{ %} INITIALIZE %{ %} TRACE COMPONENT Origin = Progress_bar() AT (0,0,0) ABSOLUTE COMPONENT sourceMantid = ISIS_moderator( Face = "hydrogen", Lmax = lmax, Lmin = lmin, dist = 3.7, focus_xw = 0.03, focus_yh = 0.03, xwidth = 0.083, yheight = 0.033, CAngle = 0.0, SAC = 1) AT (0.0, 0.0, 0.0) RELATIVE PREVIOUS COMPONENT guide1 = Guide( w1 = 0.03, h1 = 0.03, w2 = 0.03, h2 = 0.03, l = 5.3, m = 3.0) AT (0.0, 0.0, 3.7) RELATIVE Origin COMPONENT disk1 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = 10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.689) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT disk2 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = -10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.739) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT nD_Mantid_0 = Monitor_nD( options ="mantid square x limits =[-0.0155 0.0155] bins=1 y limits =[-0.0155 0.0155] bins=1, neutron pixel t, list all neutrons", xmin = -0.0155, xmax = 0.0155, ymin = -0.0155, ymax = 0.0155, restore_neutron = 1, filename = "monitor1Events.dat") AT (0, 0, 9.8195) RELATIVE sourceMantid The xml file resulting from this when I run the command mcdisplay --format=Mantid Test_Mantid.instr -n0 after compiling chucks out this message Illegal division by zero at /usr/local/bin/mcdisplay line 391, line 73. And proceeds to dump an enormously long xml file with a huge number of weird repeated components. Any hints as to what is messing things up would be greatly appreciated. Thanks Rob =================================== Dr. Robert Dalgliesh ISIS STFC Rutherford Appleton Laboratory R3 1.29 Harwell Oxford Didcot OX11 0QX Office Tel: +44 (0) 1235 445687 or OffSpec Instrument: +44 (0) 1235 567045 Internal Mobile Extension: 1176 e-mail: robert.dalgliesh at stfc.ac.uk -- Scanned by iCritical. _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.dalgliesh at stfc.ac.uk Tue Nov 25 15:27:08 2014 From: robert.dalgliesh at stfc.ac.uk (robert.dalgliesh at stfc.ac.uk) Date: Tue, 25 Nov 2014 14:27:08 +0000 Subject: [mcstas-users] mantid output test In-Reply-To: <1A6D3480-0282-4B84-A1ED-A8BDB6BF7A43@fysik.dtu.dk> References: <9FD256ED3764AA40BD335311A4123FA0457941D4@EXCHMBX03.fed.cclrc.ac.uk> <4D0598D6-935F-4E50-ABF1-FB0F3147508C@fysik.dtu.dk> <9FD256ED3764AA40BD335311A4123FA0457942D3@EXCHMBX03.fed.cclrc.ac.uk> <1A6D3480-0282-4B84-A1ED-A8BDB6BF7A43@fysik.dtu.dk> Message-ID: <9FD256ED3764AA40BD335311A4123FA04579443C@EXCHMBX03.fed.cclrc.ac.uk> The broken links pointed at /var/lib/alternatives It seems to be a hangover from making sure that mcstas 2.0 and 2.1 can be installed side by side even though I did an uninstall of the previous version. Maybe there needs to be some extra checking. Rob From: Peter Kj?r Willendrup [mailto:pkwi at fysik.dtu.dk] Sent: 25 November 2014 12:43 To: Dalgliesh, Robert (STFC,RAL,ISIS) Cc: mcstas-users at mcstas.org Subject: Re: [mcstas-users] mantid output test Good to hear that. :-) In regard to the rpm?s - where did they point? and where would you have liked to have them point? (Then there is a chance things will be OK for 2.2? ;-) ) Peter On 25 Nov 2014, at 13:23 , robert.dalgliesh at stfc.ac.uk wrote: Thanks Peter, That worked. Incidentally it still took a bit of hacking to install mcstas 2.1 from rpm. The soft links still point at some strange places. Thanks again Rob From: Peter Kj?r Willendrup [mailto:pkwi at fysik.dtu.dk] Sent: 25 November 2014 12:12 To: Dalgliesh, Robert (STFC,RAL,ISIS) Cc: mcstas-users at mcstas.org Subject: Re: [mcstas-users] mantid output test Dear Rob, You have indeed stumbled across a proper bug - it seems what I implemented in mcdisplay for generation of the IDF implicitly assumes n>1 bins? :-) I will test for the special case of n=1 bins in the next released mcdisplay. I am able to generate the IDF and NeXus output if I define an event monitor with 2x2 bins which loads OK into Mantid. (My Mantid then on the other hand crashes when I attempt to show the instrument? This may or may not be my recently updated Mac OS X Yosemite, not clear?. - But ?color fill plot? can be done) Best, Peter On 25 Nov 2014, at 12:13 , robert.dalgliesh at stfc.ac.uk wrote: Hi, I?ve been brave and tried the Mantid output option in mcstas this morning. I?m using mcstas 2.1 and mantid 3.2.1 on a Redhat 6.4 box. There seems to be no problem with the installed NeXus and hdf libraries the simulation runs fine. The problem comes when I try following the instructions to generate the IDF file. This is the simple instrument I?ve tried some of the variables would be picked up in later components. /* Change name of instrument and input parameters with default values */ DEFINE INSTRUMENT test(s1=0.03,s2=0.02,s3=0.008,bs=0.05,cdel=0.0,sampdet=4.406,lmin=0.5,lmax=13.0,dang=0.0) DECLARE %{ %} INITIALIZE %{ %} TRACE COMPONENT Origin = Progress_bar() AT (0,0,0) ABSOLUTE COMPONENT sourceMantid = ISIS_moderator( Face = "hydrogen", Lmax = lmax, Lmin = lmin, dist = 3.7, focus_xw = 0.03, focus_yh = 0.03, xwidth = 0.083, yheight = 0.033, CAngle = 0.0, SAC = 1) AT (0.0, 0.0, 0.0) RELATIVE PREVIOUS COMPONENT guide1 = Guide( w1 = 0.03, h1 = 0.03, w2 = 0.03, h2 = 0.03, l = 5.3, m = 3.0) AT (0.0, 0.0, 3.7) RELATIVE Origin COMPONENT disk1 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = 10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.689) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT disk2 = DiskChopper( theta_0 = 111.0, radius = 0.27, yheight = 0.04, nu = -10.0, nslit = 1, jitter = 0.0, delay = 0.015417+0.00012222+cdel*1.0e-6) AT (0.0, 0.0, 9.739) ABSOLUTE ROTATED (0.0, 0.0, 90.0) ABSOLUTE COMPONENT nD_Mantid_0 = Monitor_nD( options ="mantid square x limits =[-0.0155 0.0155] bins=1 y limits =[-0.0155 0.0155] bins=1, neutron pixel t, list all neutrons", xmin = -0.0155, xmax = 0.0155, ymin = -0.0155, ymax = 0.0155, restore_neutron = 1, filename = "monitor1Events.dat") AT (0, 0, 9.8195) RELATIVE sourceMantid The xml file resulting from this when I run the command mcdisplay --format=Mantid Test_Mantid.instr -n0 after compiling chucks out this message Illegal division by zero at /usr/local/bin/mcdisplay line 391, line 73. And proceeds to dump an enormously long xml file with a huge number of weird repeated components. Any hints as to what is messing things up would be greatly appreciated. Thanks Rob =================================== Dr. Robert Dalgliesh ISIS STFC Rutherford Appleton Laboratory R3 1.29 Harwell Oxford Didcot OX11 0QX Office Tel: +44 (0) 1235 445687 or OffSpec Instrument: +44 (0) 1235 567045 Internal Mobile Extension: 1176 e-mail: robert.dalgliesh at stfc.ac.uk -- Scanned by iCritical. _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users _______________________________________________ mcstas-users mailing list mcstas-users at mcstas.org http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From robert.dalgliesh at stfc.ac.uk Tue Nov 25 15:33:17 2014 From: robert.dalgliesh at stfc.ac.uk (robert.dalgliesh at stfc.ac.uk) Date: Tue, 25 Nov 2014 14:33:17 +0000 Subject: [mcstas-users] Mantid Nexus export again Message-ID: <9FD256ED3764AA40BD335311A4123FA045794479@EXCHMBX03.fed.cclrc.ac.uk> A further question on the Mantid Nexus import/export. Is it possible to export more than one detector at a time? I seem to get empty detectors when I import into mantid unless I limit the number to 1. If not is it planned that this will be available? It?s a bit tedious running the same simulation with different configurations and then having to somehow conjoin the Nexus data in Mantid. Additionally, the hdf5 file seems to be appended after each simulation. This rapidly results in a very large file when using events. Could the append be an option? Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From pkwi at fysik.dtu.dk Wed Nov 26 12:28:15 2014 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Wed, 26 Nov 2014 11:28:15 +0000 Subject: [mcstas-users] Mantid Nexus export again In-Reply-To: <9FD256ED3764AA40BD335311A4123FA045794479@EXCHMBX03.fed.cclrc.ac.uk> References: <9FD256ED3764AA40BD335311A4123FA045794479@EXCHMBX03.fed.cclrc.ac.uk> Message-ID: Dear Rob, That should be entirely possible - but an important detail is the use of the min=offset keyword to define pixel enumeration on subsequent monitors/panels. In the attached I have added an extra monitor_nd like this: COMPONENT nD_Mantid_1 = Monitor_nD( options ="mantid square x limits=[-0.2 0.2] bins=128 y limits=[-0.2 0.2] bins=128, neutron pixel t, list all neutrons", xmin = -0.2, xmax = 0.2, ymin = -0.2, ymax = 0.2, restore_neutron = 1, filename = "bank01_events.dat") AT (0.15, 0, 3.2) RELATIVE sampleMantid COMPONENT nD_Mantid_2 = Monitor_nD( options ="mantid square x limits=[-0.2 0.2] bins=128 y limits=[-0.2 0.2] bins=128, neutron pixel min=1e6 t , list all neutrons", xmin = -0.2, xmax = 0.2, ymin = -0.2, ymax = 0.2, restore_neutron = 1, filename = "bank02_events.dat") AT (-0.15, 0, 3.5) RELATIVE sampleMantid And that seems to work for me - see attached graphics. Best, Peter [cid:a92046bf-5e9c-44db-b8ed-2d6a7613dff5 at win.dtu.dk] On 25 Nov 2014, at 15:33 , robert.dalgliesh at stfc.ac.uk wrote: A further question on the Mantid Nexus import/export. Is it possible to export more than one detector at a time? I seem to get empty detectors when I import into mantid unless I limit the number to 1. If not is it planned that this will be available? It?s a bit tedious running the same simulation with different configurations and then having to somehow conjoin the Nexus data in Mantid. Additionally, the hdf5 file seems to be appended after each simulation. This rapidly results in a very large file when using events. Could the append be an option? Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: MantidPlotScreenSnapz007.jpg Type: image/jpeg Size: 127146 bytes Desc: MantidPlotScreenSnapz007.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: templateSANS_Mantid.instr Type: application/octet-stream Size: 3838 bytes Desc: templateSANS_Mantid.instr URL: From wokaoyan1981 at 126.com Fri Nov 28 02:39:21 2014 From: wokaoyan1981 at 126.com (=?GBK?B?s8LR5dbb?=) Date: Fri, 28 Nov 2014 09:39:21 +0800 (CST) Subject: [mcstas-users] need ellipsoidal mirror Message-ID: Hi all, Would anybody please contribute an ellipsoidal mirror component with description for input parameters? Thank you. Best regards, Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From farhi at ill.fr Thu Dec 11 21:13:09 2014 From: farhi at ill.fr (Emmanuel FARHI) Date: Thu, 11 Dec 2014 21:13:09 +0100 (CET) Subject: [mcstas-users] Post-Doc Fellowship: Ray tracing for USANS option on SANS instruments Message-ID: Post-Doc Fellowship: Ray tracing for USANS option on SANS instruments A post-doctoral position is available at the European Photon & Neutron (EPN) Science Campus in Grenoble (France). The EPN Science Campus is a site of excellence for cutting-edge science in several fields and it is a very exciting place to work on science, grouping in the same area three major institutes of research in Europe (Institut Laue Langevin, European synchrotron Radiation Facilities, European Molecular Biology Laboratory and their partnerships). To learn more about EPN Science Campus go to: http://www.epn- campus.eu/about-us. The main focus of the project is to perform ray-tracing calculation, using McStas code, in order to design tailored Ultra Small Angle Neuron Scattering (USANS) option on SANS instruments. The construction of a prototype is also planned and the candidate could be involved in the design, engineering and experimental tests. The post-doctoral fellowship will start in the beginning of 2015 and it will be running for one year with possibility of renewal. Requirements: the candidate should be either a EU citizen or a national from a country with free circulation EU agreements. Other nationals should posses a working permit in EU. Qualified candidates must have obtained a PhD degree in one of the following disciplines: Physics and/or Chemistry, Material Science, Material Engineering, Chemistry Engineering, Nuclear Engineering. Knowledge in ray tracing and instrumentation design will be strongly considered. Experience in SANS and USANS measurements and publications related to them will be valuable. We are searching for a candidate very motivated in development of instrumentation with skills in working in team and in independent way. Taking into account the international character of the project and the necessity to work with people from groups in different country in EU, a good knowledge of English (both written and oral) is required. If you are interested, please, send as soon as possible but no later than the end of December 2014, an email with your CV either to: Dr. Claudia Mondelli (Project Leader), email: mondelli at ill.fr Dr. Ralf Schweins, email: schweins at ill.eu If you know any potential candidate, please pass-on this announce ! -- FARHI Emmanuel Groupe DS/CS, ILL4/156, Tel 04 76 20 71 35 ILL, Grenoble From pkwi at fysik.dtu.dk Fri Dec 19 15:14:59 2014 From: pkwi at fysik.dtu.dk (=?Windows-1252?Q?Peter_Kj=E6r_Willendrup?=) Date: Fri, 19 Dec 2014 14:14:59 +0000 Subject: [mcstas-users] Post-Doc Fellowship: Ray tracing for USANS option on SANS instruments References: <54942C85.1090704@ill.eu> Message-ID: <002D566B-B025-4E18-9C3F-8D58017CBF9A@fysik.dtu.dk> Dear McStas users, Please find below an intersting Post-Doc -advert for McStas simulation and USANS/SANS design work at the EPN campus. Best, Peter Willendrup Begin forwarded message: Post-Doc Fellowship: Ray tracing for USANS option on SANS instruments A postdoctoral position is available at the European Photon & Neutron (EPN) Science Campus in Grenoble (France). The EPN Science Campus is a site of excellence for cutting-edge science in several fields and it is a very exciting place to work on science, grouping in the same area three major institutes of research in Europe (Institut Laue ? Langevin, European Synchrotron Radiation Facilitiy, European Molecular Biology Laboratory and their partnerships). To learn more about EPN Science Campus go to: http://www.epn-campus.eu/about-us. The main focus of the project is to perform ray-tracing calculations, using McStas code, in order to design a tailored Ultra Small Angle Neuron Scattering (USANS) option for SANS instruments. The construction of a prototype is also planned and the candidate would be involved in the design, engineering and experimental tests. The postdoctoral fellowship will start in the beginning of 2015 and it will be running for one year with the possibility of extension for another year. Requirements: the candidate should be either a EU citizen or a national from a country with free circulation EU agreements. Other nationals should posses a working permit for the European Union. Qualified candidates must have obtained a PhD degree in one of the following disciplines: Physics, Chemistry, Materials Science, Materials Engineering, Chemistry Engineering, Nuclear Engineering. Knowledge in ray tracing and instrumentation design will be strongly considered. Experience in SANS and USANS measurements and publications related to them will be valuable. We are searching for a candidate with high motivation in the development of instrumentation, having both the skills to work in a team and in an independent way. Taking into account the international character of the project, a good knowledge of English (both written and oral) is required. For more information, and if you are interested, please contact with your CV both: Dr. Claudia Mondelli (Project Leader), email: mondelli at ill.fr Dr. Ralf Schweins, email: schweins at ill.eu -- Dr. Ralf SCHWEINS ********************************************************************* Institut Laue-Langevin Large Scale Structures Group 71 Avenue des Martyrs CS 20156 F-38042 Grenoble CEDEX 9 Tel: +33 4 76 20 70 91 Secretary: +33 4 76 20 73 56 Fax: +33 4 76 20 71 20 ********************************************************************* http://www.ill.eu/lss/people/ralf-schweins/dr-ralf-schweins/ http://www.ill.eu/lss/more/world-directory-of-sans-instruments/ http://www.ill.eu/d11/home/ ********************************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: