From farhi at ill.eu Tue Jan 6 16:05:31 2015 From: farhi at ill.eu (Emmanuel FARHI) Date: Tue, 06 Jan 2015 16:05:31 +0100 Subject: [mcstas-users] Work placement at the ILL (2*6 months) and a PhD offer (3 y) Message-ID: <54ABF9BB.6090508@ill.eu> An HTML attachment was scrubbed... URL: From 104pet104 at gmail.com Tue Jan 27 20:08:41 2015 From: 104pet104 at gmail.com (=?UTF-8?B?0J/QtdGC0YAg0JrQvtC90LjQug==?=) Date: Tue, 27 Jan 2015 23:08:41 +0400 Subject: [mcstas-users] Perfect crystals Message-ID: Hello everybody! Currently we are working on several simulation project and the question has arised how to handle perfect Si crystals? We think of crystal with small mosaicity or mirror with corresponding reflectivity profile. Is there any more native and general approach? Best regards, Peter Konik From erkn at fysik.dtu.dk Wed Jan 28 11:34:30 2015 From: erkn at fysik.dtu.dk (Erik B Knudsen) Date: Wed, 28 Jan 2015 11:34:30 +0100 Subject: [mcstas-users] Perfect crystals In-Reply-To: References: Message-ID: <54C8BB36.3000207@fysik.dtu.dk> Dear Peter, This depends really on how perfect your crystal is. The Single_crystal component distributed with McStas currently regards mosaicity as a gaussian approximation, and as such might not be appropriate for use with perfect crystals. In case of a Darwin width dominated crystal, we could possibly modify the Perfect_crystal component that exists in McXtrace (the X-ray sister of McStas) to handle neutrons instead. It has some other limitations but this can also be extended. This shouldn't be very difficult to do. I guess the appropriate route depends a lot on what it is exactly you want to do and more details about the actual crystals. Could you be a little more specific? For sure we'd be happy to help you along. cheers Erik On 27/01/15 20:08, ???? ????? wrote: > Hello everybody! > > Currently we are working on several simulation project and the > question has arised how to handle perfect Si crystals? We think of > crystal with small mosaicity or mirror with corresponding reflectivity > profile. Is there any more native and general approach? > > Best regards, > Peter Konik > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > -- Erik Bergb?ck Knudsen, Research Engineer | DTU | morituri NEXMAP, DTU Fysik, DK-2800 Kgs. Lyngby, Denmark |<>-<>| te phone: (+45) 2132 6655 |<>-<>| salutant From 104pet104 at gmail.com Wed Jan 28 13:55:35 2015 From: 104pet104 at gmail.com (=?UTF-8?B?0J/QtdGC0YAg0JrQvtC90LjQug==?=) Date: Wed, 28 Jan 2015 16:55:35 +0400 Subject: [mcstas-users] mcstas-users Digest, Vol 35, Issue 2 In-Reply-To: References: Message-ID: Dear Erik, we are working on simulations of double crystal diffractometer, so we speak on Si crystals with Darwin curve reflections. Best regards, Peter Konik 2015-01-28 15:00 GMT+04:00 : > Send mcstas-users mailing list submissions to > mcstas-users at mcstas.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > or, via email, send a message with subject or body 'help' to > mcstas-users-request at mcstas.org > > You can reach the person managing the list at > mcstas-users-owner at mcstas.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mcstas-users digest..." > > > Today's Topics: > > 1. Perfect crystals (???? ?????) > 2. Re: Perfect crystals (Erik B Knudsen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 27 Jan 2015 23:08:41 +0400 > From: ???? ????? <104pet104 at gmail.com> > To: mcstas-users at mcstas.org > Subject: [mcstas-users] Perfect crystals > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Hello everybody! > > Currently we are working on several simulation project and the > question has arised how to handle perfect Si crystals? We think of > crystal with small mosaicity or mirror with corresponding reflectivity > profile. Is there any more native and general approach? > > Best regards, > Peter Konik > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Jan 2015 11:34:30 +0100 > From: Erik B Knudsen > To: > Subject: Re: [mcstas-users] Perfect crystals > Message-ID: <54C8BB36.3000207 at fysik.dtu.dk> > Content-Type: text/plain; charset="UTF-8"; format=flowed > > Dear Peter, > > This depends really on how perfect your crystal is. The Single_crystal component distributed with McStas > currently regards mosaicity as a gaussian approximation, and as such might not be appropriate for use > with perfect crystals. > In case of a Darwin width dominated crystal, we could possibly modify > the Perfect_crystal component that exists in McXtrace (the X-ray sister of McStas) to handle neutrons instead. > It has some other limitations but this can also be extended. This shouldn't be very difficult to do. > > I guess the appropriate route depends a lot on what it is exactly you want to do and more details about the actual > crystals. Could you be a little more specific? For sure we'd be happy to help you along. > > cheers > Erik > > On 27/01/15 20:08, ???? ????? wrote: >> Hello everybody! >> >> Currently we are working on several simulation project and the >> question has arised how to handle perfect Si crystals? We think of >> crystal with small mosaicity or mirror with corresponding reflectivity >> profile. Is there any more native and general approach? >> >> Best regards, >> Peter Konik >> _______________________________________________ >> mcstas-users mailing list >> mcstas-users at mcstas.org >> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >> > > -- > Erik Bergb?ck Knudsen, Research Engineer | DTU | morituri > NEXMAP, DTU Fysik, DK-2800 Kgs. Lyngby, Denmark |<>-<>| te > phone: (+45) 2132 6655 |<>-<>| salutant > > > > ------------------------------ > > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > > > End of mcstas-users Digest, Vol 35, Issue 2 > ******************************************* From Peter.Link at frm2.tum.de Mon Feb 2 15:49:58 2015 From: Peter.Link at frm2.tum.de (Peter Link) Date: Mon, 02 Feb 2015 15:49:58 +0100 Subject: [mcstas-users] McStas 2.1 on Win7prof 64bit machine problem Message-ID: <54CF8E96.7060604@frm2.tum.de> Dear friends, I like to report my problem in running mcstas 2.1 on my w7 machine. I installed the package as recommended. I can start mcgui and load an instrument file. Once I try to compile an instrument I get the following error messages ... d:/python27/egg-info/mingw/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.2/../../../ ../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible d:/python27/egg-info/min gw/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.2/../../../../x86_64-w64-mingw32/li b\libm.a when searching for -lm ... I have an Enthougth Python 2.7 installed, which otherwise works fine. Have you any idea whats up? I wouldn't like to kill my python installation as I use it for other purpose, too. Best regards, Peter -- Dr. Peter Link Leiter Neutronenoptik Forschungs-Neutronenquelle Heinz Maier-Leibnitz Technische Universit?t M?nchen Lichtenbergstr. 1 85747 Garching From pkwi at fysik.dtu.dk Mon Feb 2 16:11:54 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Mon, 2 Feb 2015 15:11:54 +0000 Subject: [mcstas-users] McStas 2.1 on Win7prof 64bit machine problem In-Reply-To: <54CF8E96.7060604@frm2.tum.de> References: <54CF8E96.7060604@frm2.tum.de> Message-ID: Dear Peter, My first guess would be that your Python libm.a ends up ?before? on the searched library path than what your c-compiler provides? Is your gcc sitting with strawberry Perl in c:\strawberry\perl\bin ? Then it might help to put -Lc:\\strawberry\\perl\\lib (or whatever the path of the ?real? libm is) into your MCSTAS_CFLAGS? Alternatively, try modifying the mccodeenv.bat script in c:\mcstas-2.1\bin so that you suppress the pytohon? (I.e. set the PATH explicitly rather than adding c:\mcstas-2.1\bin) Best, Peter On 02 Feb 2015, at 15:49 , Peter Link > wrote: Dear friends, I like to report my problem in running mcstas 2.1 on my w7 machine. I installed the package as recommended. I can start mcgui and load an instrument file. Once I try to compile an instrument I get the following error messages ... d:/python27/egg-info/mingw/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.2/../../../ ../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible d:/python27/egg-info/min gw/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.2/../../../../x86_64-w64-mingw32/li b\libm.a when searching for -lm ... I have an Enthougth Python 2.7 installed, which otherwise works fine. Have you any idea whats up? I wouldn't like to kill my python installation as I use it for other purpose, too. Best regards, Peter -- Dr. Peter Link Leiter Neutronenoptik Forschungs-Neutronenquelle Heinz Maier-Leibnitz Technische Universit?t M?nchen Lichtenbergstr. 1 85747 Garching _______________________________________________ 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 Wed Feb 4 09:31:09 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Wed, 4 Feb 2015 08:31:09 +0000 Subject: [mcstas-users] McStas 2.1 on Win7prof 64bit machine problem In-Reply-To: References: <54CF8E96.7060604@frm2.tum.de> Message-ID: <2BD71B0C-B6B2-4535-97C6-C31AEAFCC3E7@fysik.dtu.dk> Hi mcstas-users, Peter Link reports that the problem could be resolved by putting the Python stuff at the very end of the Windows PATH variable definition. I will document this on the website among the ?known issues? for the Windows platform. Best, Peter On 02 Feb 2015, at 16:11 , Peter Kj?r Willendrup > wrote: Dear Peter, My first guess would be that your Python libm.a ends up ?before? on the searched library path than what your c-compiler provides? Is your gcc sitting with strawberry Perl in c:\strawberry\perl\bin ? Then it might help to put -Lc:\\strawberry\\perl\\lib (or whatever the path of the ?real? libm is) into your MCSTAS_CFLAGS? Alternatively, try modifying the mccodeenv.bat script in c:\mcstas-2.1\bin so that you suppress the pytohon? (I.e. set the PATH explicitly rather than adding c:\mcstas-2.1\bin) Best, Peter On 02 Feb 2015, at 15:49 , Peter Link > wrote: Dear friends, I like to report my problem in running mcstas 2.1 on my w7 machine. I installed the package as recommended. I can start mcgui and load an instrument file. Once I try to compile an instrument I get the following error messages ... d:/python27/egg-info/mingw/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.2/../../../ ../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible d:/python27/egg-info/min gw/usr/bin/../lib/gcc/x86_64-w64-mingw32/4.5.2/../../../../x86_64-w64-mingw32/li b\libm.a when searching for -lm ... I have an Enthougth Python 2.7 installed, which otherwise works fine. Have you any idea whats up? I wouldn't like to kill my python installation as I use it for other purpose, too. Best regards, Peter -- Dr. Peter Link Leiter Neutronenoptik Forschungs-Neutronenquelle Heinz Maier-Leibnitz Technische Universit?t M?nchen Lichtenbergstr. 1 85747 Garching _______________________________________________ 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 pkwi at fysik.dtu.dk Tue Feb 10 10:51:44 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Tue, 10 Feb 2015 09:51:44 +0000 Subject: [mcstas-users] Guidance document, ESS TDR and pancake moderators Message-ID: Dear all, A number of McStas users have expressed that the documentation for the ESS_moderator component distributed with McStas is not completely clear. To remedy this, Ken Andersen and I have (with the help of data from Troels Sch?nfeldt) produced the attached document that will hopefully help. Please note that at this point, only TDR-like and pancake moderators are described in McStas. An updated set of moderator descriptions will be released with McStas 2.2 during the spring of 2015. Al the best, Peter Willendrup Peter Kj?r Willendrup Senior Research Engineer, Special Advisor DTU Physics [cid:fa26f480-1353-45fe-b15c-9752cd675b64 at win.dtu.dk] Technical University of Denmark [cid:fa6f8519-0722-4f8c-abd3-c3a047cfa080 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 -------------- 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: Reproducing ESS TDR and pancake brillances with McStas.pdf Type: application/pdf Size: 2285008 bytes Desc: Reproducing ESS TDR and pancake brillances with McStas.pdf URL: From a.kusmin at tudelft.nl Wed Feb 11 15:41:28 2015 From: a.kusmin at tudelft.nl (=?UTF-8?B?QW5kcsOpIEt1c21pbg==?=) Date: Wed, 11 Feb 2015 15:41:28 +0100 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output Message-ID: <54DB6A18.30409@tudelft.nl> Hi everyone, I had a problem of an incorrect output for a 1D detector in case when environmental variable MCSTAS_FORMAT was set to gnuplot. (only one column was written in the output file instead of four) 2D output (such as e.g. PSDMonitor.dat) was correct. Short summary to test reproducibility export variable MCSTAS_FORMAT = gnuplot Load TestSANS.instr (from "examples"), compile it, and run with default parameters. When running via mcgui, you can set output PGPLOT or gnuplot, it doesn not matter - your output files QDetector.dat and RDetector.dat will have only 100 values instead of 400. If you set MCSTAS_FORMAT="" then (after restarting mcgui) you will get correct output. I tried other components such as L_monitor, the same behaviour. I hope this will help someone and the bug can be fixed, best regards Andre From pkwi at fysik.dtu.dk Thu Feb 12 20:16:44 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Thu, 12 Feb 2015 19:16:44 +0000 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output In-Reply-To: <54DB6A18.30409@tudelft.nl> References: <54DB6A18.30409@tudelft.nl> Message-ID: <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> Dear Andre, With which version of McStas did you experience this? - Under some very special circumstances McStas 2.0 can exhibit this type of issue. It would also help to try reproducing the problem to know the exact system you are running on, i.e. what OS and which version. I firmly believe the setting of MCSTAS_FORMAT to gnuplot will not affect anything: In the internal c-code of McStas the ?gnuplot? format is actually unhandled and we revert to the traditional McStas or PGPLOT format. The setting of gnuplot only affects the tool-layer, i.e. mcplot etc. Best, Peter > On 11 Feb 2015, at 15:41 , Andr? Kusmin wrote: > > Hi everyone, > I had a problem of an incorrect output for a 1D detector in case when environmental variable > MCSTAS_FORMAT was set to gnuplot. (only one column was written in the output file instead of four) > 2D output (such as e.g. PSDMonitor.dat) was correct. > > Short summary to test reproducibility > export variable MCSTAS_FORMAT = gnuplot > Load TestSANS.instr (from "examples"), compile it, and run with default parameters. > When running via mcgui, you can set output PGPLOT or gnuplot, it doesn not matter - your output > files QDetector.dat and RDetector.dat will have only 100 values instead of 400. > > If you set MCSTAS_FORMAT="" then (after restarting mcgui) > you will get correct output. > > I tried other components such as L_monitor, the same behaviour. > > I hope this will help someone and the bug can be fixed, > > best regards > > Andre > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users From a.kusmin at tudelft.nl Fri Feb 13 10:53:11 2015 From: a.kusmin at tudelft.nl (=?UTF-8?B?QW5kcsOpIEt1c21pbg==?=) Date: Fri, 13 Feb 2015 10:53:11 +0100 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output In-Reply-To: <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> References: <54DB6A18.30409@tudelft.nl> <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> Message-ID: <54DDC987.5020509@tudelft.nl> Dear Peter, I am sorry, I forgot some basic rules of a bug report. I have Slackware 14.1 64 bit multilib , and I had this problem for both McStas 2.1 and McStas compiled from svn. Some things do not work on Slackware out of the box, so I tested if this problem is reproducible on Debian. And it is the same behaviour on Debian. ( DebianEdu/Skolelinux Release: 7.8 (wheezy) Arch: amd64 ) where I installed McStas 2.1 stable release using following sequence apt-get install mcstas-manuals-2.1 (this installed mcstas-2.1 mcstas-comps-2.1 mcstas-manuals-2.1 ) apt-get install mcstas-suite-python then I manually installed pgplot5_5.2.2-19_amd64.deb and then apt-get install mcstas-suite mcstas-suite-perl mcstas-tools-perl-2.1 libpgplot-perl The strangest thing to me is that when I run instrument-executable compiled on Debian (e.g. TestSANS.out) on a machine with no mcstas (mcplot,etc) installed I will get wrong 1D detector output file ! (with only one column out of four) if I will issue MCSTAS_FORMAT="gnuplot" before running Setting MCSTAS_FORMAT="something" also leads to wrong results So, I can't see how mcplot or other auxillary McStas tools can be a source of the problem I will test this behavior on Mac Os Maverics next time I will boot into MacOs. Hope this helps, Andre > Dear Andre, > > > With which version of McStas did you experience this? - Under some very special circumstances McStas 2.0 can exhibit this type of issue. > > It would also help to try reproducing the problem to know the exact system you are running on, i.e. what OS and which version. > > I firmly believe the setting of MCSTAS_FORMAT to gnuplot will not affect anything: In the internal c-code of McStas the ?gnuplot? format is actually unhandled and we revert to the traditional McStas or PGPLOT format. The setting of gnuplot only affects the tool-layer, i.e. mcplot etc. > > > Best, > > Peter > -- Dr Andr? Kusmin Department Radiation Science and Technology Faculty of Applied Sciences Delft University of Technology Mekelweg 15 2629 JB Delft the Netherlands phone: +31 (0)15 278 4701 fax: +31 (0)15 278 8303 e-mail: a.kusmin at tudelft.nl From pkwi at fysik.dtu.dk Fri Feb 13 11:12:04 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Fri, 13 Feb 2015 10:12:04 +0000 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output In-Reply-To: <54DDC987.5020509@tudelft.nl> References: <54DB6A18.30409@tudelft.nl> <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> <54DDC987.5020509@tudelft.nl> Message-ID: <4E68543C-7125-4F0C-A325-F2E20B880E04@fysik.dtu.dk> Dear Andre, On 13 Feb 2015, at 10:53 , Andr? Kusmin > wrote: I am sorry, I forgot some basic rules of a bug report. This is perfectly OK. :-) I have Slackware 14.1 64 bit multilib , and I had this problem for both McStas 2.1 and McStas compiled from svn. Some things do not work on Slackware out of the box, so I tested if this problem is reproducible on Debian. And it is the same behaviour on Debian. ( DebianEdu/Skolelinux Release: 7.8 (wheezy) Arch: amd64 ) where I installed McStas 2.1 stable release using following sequence apt-get install mcstas-manuals-2.1 (this installed mcstas-2.1 mcstas-comps-2.1 mcstas-manuals-2.1 ) apt-get install mcstas-suite-python then I manually installed pgplot5_5.2.2-19_amd64.deb and then apt-get install mcstas-suite mcstas-suite-perl mcstas-tools-perl-2.1 libpgplot-perl The strangest thing to me is that when I run instrument-executable compiled on Debian (e.g. TestSANS.out) on a machine with no mcstas (mcplot,etc) installed I will get wrong 1D detector output file ! (with only one column out of four) if I will issue MCSTAS_FORMAT="gnuplot" before running Setting MCSTAS_FORMAT="something" also leads to wrong results So, I can't see how mcplot or other auxillary McStas tools can be a source of the problem I will test this behavior on Mac Os Maverics next time I will boot into MacOs. You indeed seem to have found a general problem! I have just reproduced the bug with a different instrument on OS X Yosemite? I will try to dig for the cause of this early next week. Best, Peter Dear Andre, With which version of McStas did you experience this? - Under some very special circumstances McStas 2.0 can exhibit this type of issue. It would also help to try reproducing the problem to know the exact system you are running on, i.e. what OS and which version. I firmly believe the setting of MCSTAS_FORMAT to gnuplot will not affect anything: In the internal c-code of McStas the ?gnuplot? format is actually unhandled and we revert to the traditional McStas or PGPLOT format. The setting of gnuplot only affects the tool-layer, i.e. mcplot etc. Best, Peter -- Dr Andr? Kusmin Department Radiation Science and Technology Faculty of Applied Sciences Delft University of Technology Mekelweg 15 2629 JB Delft the Netherlands phone: +31 (0)15 278 4701 fax: +31 (0)15 278 8303 e-mail: a.kusmin at tudelft.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jean-Francois.Moulin at hzg.de Fri Feb 13 12:41:56 2015 From: Jean-Francois.Moulin at hzg.de (Jean-Francois.Moulin at hzg.de) Date: Fri, 13 Feb 2015 12:41:56 +0100 Subject: [mcstas-users] what happened to plane_intersect_Gfast? Message-ID: Hi dear Devels! I am trying to port a Mcstas 1.x component to 2.1 (am still under 2.1rc1) and was hopefully able to cleanup the parameters, but now I am hitting a "undefined reference to `plane_intersect_Gfast'" compiler error. Was this function deprecated or replaced ? Thanks in advance for any help Best regards, Jean-Fran?ois - Helmholtz Zentrum Geesthacht Institut f?r Werkstoffforschung Abteilung WPN, Instrument REFSANS Lichtenbergstr. 1 85747 Garching FRM II Tel.: +49 (0)89 289 10762 Internet: http://www.frm2.tum.de Helmholtz-Zentrum Geesthacht Zentrum f?r Material- und K?stenforschung GmbH Max-Planck-Stra?e 1 I 21502 Geesthacht I Deutschland/Germany Gesch?ftsf?hrer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Gan? Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus Amtsgericht L?beck HRB 285 GE (Register Court) Internet: http://www.hzg.de From p at willendrup.org Fri Feb 13 14:36:32 2015 From: p at willendrup.org (Peter Willendrup) Date: Fri, 13 Feb 2015 14:36:32 +0100 Subject: [mcstas-users] what happened to plane_intersect_Gfast? In-Reply-To: References: Message-ID: <927BD93B-9FD3-49EC-835A-A050C54371CF@willendrup.org> Dear Jean-Francois, plane_intersect_Gfast was nothing but a special case of a second order equation solver (of course :-) ). These days all comps needing this functionality apply solve_2nd_order instead, i.e. Replace your existing ret = plane_intersect_Gfast(&dt, A, B, C); by ret = solve_2nd_order(&dt, NULL, A, B, C); in case you need only the first root of the polynomium. Alternatively send your component along here and I will have a look during next week. Best, Peter > On 13 Feb 2015, at 12:41 , Jean-Francois.Moulin at hzg.de wrote: > > Hi dear Devels! > > I am trying to port a Mcstas 1.x component to 2.1 (am still under 2.1rc1) and was hopefully able to cleanup the parameters, but now I am hitting a > "undefined reference to `plane_intersect_Gfast'" compiler error. > Was this function deprecated or replaced ? > > Thanks in advance for any help > > Best regards, > Jean-Fran?ois > > - > Helmholtz Zentrum Geesthacht > Institut f?r Werkstoffforschung > Abteilung WPN, Instrument REFSANS > Lichtenbergstr. 1 > 85747 Garching FRM II > Tel.: +49 (0)89 289 10762 > Internet: http://www.frm2.tum.de > Helmholtz-Zentrum Geesthacht > Zentrum f?r Material- und K?stenforschung GmbH > Max-Planck-Stra?e 1 I 21502 Geesthacht I Deutschland/Germany > > Gesch?ftsf?hrer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Gan? > Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus > Amtsgericht L?beck HRB 285 GE (Register Court) > Internet: http://www.hzg.de > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users From Jean-Francois.Moulin at hzg.de Fri Feb 13 17:37:47 2015 From: Jean-Francois.Moulin at hzg.de (Jean-Francois.Moulin at hzg.de) Date: Fri, 13 Feb 2015 17:37:47 +0100 Subject: [mcstas-users] Antwort: Re: what happened to plane_intersect_Gfast? In-Reply-To: <927BD93B-9FD3-49EC-835A-A050C54371CF@willendrup.org> References: <927BD93B-9FD3-49EC-835A-A050C54371CF@willendrup.org>, Message-ID: Dear Peter! Thanks a lot, that seems to do the trick! have a nice WE! JF - Helmholtz Zentrum Geesthacht Institut f?r Werkstoffforschung Abteilung WPN, Instrument REFSANS Lichtenbergstr. 1 85747 Garching FRM II Tel.: +49 (0)89 289 10762 Internet: http://www.frm2.tum.de -----Peter Willendrup schrieb: ----- An: Jean-Francois.Moulin at hzg.de Von: Peter Willendrup Gesendet von: Peter Willendrup Datum: 13.02.2015 14:36 Kopie: mcstas-users at mcstas.org Betreff: Re: [mcstas-users] what happened to plane_intersect_Gfast? Dear Jean-Francois, plane_intersect_Gfast was nothing but a special case of a second order equation solver (of course :-) ). These days all comps needing this functionality apply solve_2nd_order instead, i.e. Replace your existing ret = plane_intersect_Gfast(&dt, A, B, C); by ret = solve_2nd_order(&dt, NULL, A, B, C); in case you need only the first root of the polynomium. Alternatively send your component along here and I will have a look during next week. Best, Peter > On 13 Feb 2015, at 12:41 , Jean-Francois.Moulin at hzg.de wrote: > > Hi dear Devels! > > I am trying to port a Mcstas 1.x component to 2.1 (am still under 2.1rc1) and was hopefully able to cleanup the parameters, but now I am hitting a > "undefined reference to `plane_intersect_Gfast'" compiler error. > Was this function deprecated or replaced ? > > Thanks in advance for any help > > Best regards, > Jean-Fran?ois > > - > Helmholtz Zentrum Geesthacht > Institut f?r Werkstoffforschung > Abteilung WPN, Instrument REFSANS > Lichtenbergstr. 1 > 85747 Garching FRM II > Tel.: +49 (0)89 289 10762 > Internet: http://www.frm2.tum.de > Helmholtz-Zentrum Geesthacht > Zentrum f?r Material- und K?stenforschung GmbH > Max-Planck-Stra?e 1 I 21502 Geesthacht I Deutschland/Germany > > Gesch?ftsf?hrer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Gan? > Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus > Amtsgericht L?beck HRB 285 GE (Register Court) > Internet: http://www.hzg.de?? > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users Helmholtz-Zentrum Geesthacht Zentrum f?r Material- und K?stenforschung GmbH Max-Planck-Stra?e 1 I 21502 Geesthacht I Deutschland/Germany Gesch?ftsf?hrer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Gan? Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus Amtsgericht L?beck HRB 285 GE (Register Court) Internet: http://www.hzg.de From pkwi at fysik.dtu.dk Tue Feb 17 09:51:08 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Tue, 17 Feb 2015 08:51:08 +0000 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output In-Reply-To: <4E68543C-7125-4F0C-A325-F2E20B880E04@fysik.dtu.dk> References: <54DB6A18.30409@tudelft.nl> <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> <54DDC987.5020509@tudelft.nl> <4E68543C-7125-4F0C-A325-F2E20B880E04@fysik.dtu.dk> Message-ID: Dear Andre, The bug has been fixed in our SVN repos for next release - see here http://trac.mccode.org/changeset/5365#file0 (Sorry that I named you Markus Appel in the log message - what confused me is that I have a few bug reports from him also at this point? ;-) ) If you want you can hand-edit your mccode-r.c accordingly or apply the attached diff to your local mccode-r.c file. (e.g. cd /usr/share/mcstas/2.1/share ; patch -p0 /tmp/diff-5365.patch) Alternatively, you may build a fresh set of packages for yourself via 1) Checking out our SVN trunk: svn co https://svn.mccode.org/svn/McCode/trunk 2) Install the relevant dependencies listed in the file trunk/BUILD_DEPS.TXT 3) Run one or more of the build scripts provided in trunk, e.g. ./build_debs_mcstas 2.2beta Best, Peter On 13 Feb 2015, at 11:12 , Peter Kj?r Willendrup > wrote: Dear Andre, On 13 Feb 2015, at 10:53 , Andr? Kusmin > wrote: I am sorry, I forgot some basic rules of a bug report. This is perfectly OK. :-) I have Slackware 14.1 64 bit multilib , and I had this problem for both McStas 2.1 and McStas compiled from svn. Some things do not work on Slackware out of the box, so I tested if this problem is reproducible on Debian. And it is the same behaviour on Debian. ( DebianEdu/Skolelinux Release: 7.8 (wheezy) Arch: amd64 ) where I installed McStas 2.1 stable release using following sequence apt-get install mcstas-manuals-2.1 (this installed mcstas-2.1 mcstas-comps-2.1 mcstas-manuals-2.1 ) apt-get install mcstas-suite-python then I manually installed pgplot5_5.2.2-19_amd64.deb and then apt-get install mcstas-suite mcstas-suite-perl mcstas-tools-perl-2.1 libpgplot-perl The strangest thing to me is that when I run instrument-executable compiled on Debian (e.g. TestSANS.out) on a machine with no mcstas (mcplot,etc) installed I will get wrong 1D detector output file ! (with only one column out of four) if I will issue MCSTAS_FORMAT="gnuplot" before running Setting MCSTAS_FORMAT="something" also leads to wrong results So, I can't see how mcplot or other auxillary McStas tools can be a source of the problem I will test this behavior on Mac Os Maverics next time I will boot into MacOs. You indeed seem to have found a general problem! I have just reproduced the bug with a different instrument on OS X Yosemite? I will try to dig for the cause of this early next week. Best, Peter Dear Andre, With which version of McStas did you experience this? - Under some very special circumstances McStas 2.0 can exhibit this type of issue. It would also help to try reproducing the problem to know the exact system you are running on, i.e. what OS and which version. I firmly believe the setting of MCSTAS_FORMAT to gnuplot will not affect anything: In the internal c-code of McStas the ?gnuplot? format is actually unhandled and we revert to the traditional McStas or PGPLOT format. The setting of gnuplot only affects the tool-layer, i.e. mcplot etc. Best, Peter -- Dr Andr? Kusmin Department Radiation Science and Technology Faculty of Applied Sciences Delft University of Technology Mekelweg 15 2629 JB Delft the Netherlands phone: +31 (0)15 278 4701 fax: +31 (0)15 278 8303 e-mail: a.kusmin at tudelft.nl _______________________________________________ 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: diff-5365.patch Type: application/octet-stream Size: 877 bytes Desc: diff-5365.patch URL: From a.kusmin at tudelft.nl Tue Feb 17 10:45:05 2015 From: a.kusmin at tudelft.nl (=?UTF-8?B?QW5kcsOpIEt1c21pbg==?=) Date: Tue, 17 Feb 2015 10:45:05 +0100 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output In-Reply-To: References: <54DB6A18.30409@tudelft.nl> <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> <54DDC987.5020509@tudelft.nl> <4E68543C-7125-4F0C-A325-F2E20B880E04@fysik.dtu.dk> Message-ID: <54E30DA1.4010602@tudelft.nl> Dear Peter, that was fast, thank you! As for calling me Markus Appel - I don't mind; the main thing is that the bug is fixed :) best, Andre On 02/17/2015 09:51 AM, Peter Kj?r Willendrup wrote: > Dear Andre, > > > The bug has been fixed in our SVN repos for next release - see here > http://trac.mccode.org/changeset/5365#file0 > (Sorry that I named you Markus Appel in the log message - what > confused me is that I have a few bug reports from him also at this > point? ;-) ) > > If you want you can hand-edit your mccode-r.c accordingly or apply > the attached diff to your local mccode-r.c file. (e.g. cd > /usr/share/mcstas/2.1/share ; patch -p0 /tmp/diff-5365.patch) > > Alternatively, you may build a fresh set of packages for yourself via > 1) Checking out our SVN trunk: > svn co https://svn.mccode.org/svn/McCode/trunk > 2) Install the relevant dependencies listed in the file > trunk/BUILD_DEPS.TXT > 3) Run one or more of the build scripts provided in trunk, e.g. > ./build_debs_mcstas 2.2beta > > > Best, > > Peter > -------------- next part -------------- An HTML attachment was scrubbed... URL: From masolomaster3000 at googlemail.com Tue Feb 17 12:59:16 2015 From: masolomaster3000 at googlemail.com (Markus Appel) Date: Tue, 17 Feb 2015 12:59:16 +0100 Subject: [mcstas-users] MCSTAS_FORMAT=gnuplot leads to wrong 1D detector output In-Reply-To: <54E30DA1.4010602@tudelft.nl> References: <54DB6A18.30409@tudelft.nl> <2B214D73-17E1-4983-AFAB-E3280E793EF6@fysik.dtu.dk> <54DDC987.5020509@tudelft.nl> <4E68543C-7125-4F0C-A325-F2E20B880E04@fysik.dtu.dk> <54E30DA1.4010602@tudelft.nl> Message-ID: <54E32D14.4010901@googlemail.com> On 02/17/2015 10:45 AM, Andr? Kusmin wrote: > As for calling me Markus Appel - I don't mind; Nobody should mind! Although it might get confusing at some point ;) Cheers, Markus From pkwi at fysik.dtu.dk Thu Feb 19 11:00:26 2015 From: pkwi at fysik.dtu.dk (=?utf-8?B?UGV0ZXIgS2rDpnIgV2lsbGVuZHJ1cA==?=) Date: Thu, 19 Feb 2015 10:00:26 +0000 Subject: [mcstas-users] Bugfix-release of the ESS_moderator.comp Message-ID: <0FF00228-4F39-4ADC-9113-CD26C1F07D54@fysik.dtu.dk> Dear all, Jan Saroun from NPI in Czech Republic (and author of RESTRAX/SIMRES) has spotted an unfortunate error in the ESS_moderator.comp component, relating to the 2014 "pancake" case. The bug is a missing distance-factor in a solid-angle computation and will lead to a too high brilliance emitted from the source. Unfortunately was never spotted in our tests since these happen with an instrument where this distance is set to 1 m... (and 1 x 1 = 1... ) The updated source packge for use with McStas 1.12c and 2.x is available for download at http://mcstas.org/download/share/ESS_moderator_February_2015.tgz . A set of ?release notes? is available at http://mcstas.org/download/share/ESS_moderator_February_2015.tgz.html Best and sorry for any inconvenience this may cause, Peter 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 a.kusmin at tudelft.nl Mon Mar 2 13:43:10 2015 From: a.kusmin at tudelft.nl (=?UTF-8?B?QW5kcsOpIEt1c21pbg==?=) Date: Mon, 02 Mar 2015 13:43:10 +0100 Subject: [mcstas-users] Pol_simpleBfield : wrong intensity(?) Message-ID: <54F45ADE.2090708@tudelft.nl> Hi everyone, I noticed that in a simple polarized neutron instrument made of source, polarizer, precession field, analyzer the resulting signal, as expected, oscillates as cos(const*lambda*B*L) but at B=0, the intensity of the signal is less than 100% (see attached PNG, plotted intensity against two different lengths of magnetic field regions). It turns out that intensity at B*L=0 is correct. For 100 % polarized beam and zero precession field the intensity after the analyzer is 4.2e-14 (with TestLarmor.out) The same intensity I get with ./TestLarmorOnlysource.out but when I set non zero field in precession region I get even larger intensity, which is impossible. Test can be done with two attached instr files and commands: ./TestLarmor.out By1=0 -n 1e5 DLambda=0.000001 ./TestLarmor.out By1=0.000001 -n 1e5 DLambda=0.000001 ./TestLarmorOnlysource.out -n 1e5 DLambda=0.000001 could anyone please check if this is reproducible? perhaps I miss something. I have McStas pre2.2 (compiled from SVN) on linux multilib 64 bit (Slackware) best regards Andre -------------- next part -------------- /******************************************************************************* * McStas instrument definition URL=http://www.mcstas.org * * Instrument: TestLarmor * * %Identification * Release: McStas 2.2 * * %Description * Toy model to test Larmor precessions * ** * %End *******************************************************************************/ DEFINE INSTRUMENT TestLarmor( Lambda= 2.1, DLambda= 0.1, sourcefocusdist = 100, detsize=0.5, //polarization initialpol = 1.0, polarizerpos = 0.5, //fields Bfield1start = 1, BsizeX = 0.5, BsizeY = 0.05, BsizeZ = 2, // field strength By1 = 0.001 ) DECLARE %{ double Bfield1stop; %} INITIALIZE %{ Bfield1stop=Bfield1start+BsizeZ; %} TRACE COMPONENT Origin = Progress_bar() AT (0, 0, 0) ABSOLUTE COMPONENT Source = Source_simple( radius = 0.00, yheight = 0.01, xwidth = 0.01, dist = sourcefocusdist, focus_xw = 0.01, focus_yh = 0.01, lambda0 = Lambda, dlambda = DLambda * Lambda) AT (0, 0, 0) RELATIVE Origin COMPONENT polariser = Set_pol(px=initialpol) AT (0, 0, polarizerpos) RELATIVE Origin COMPONENT B_field1=Pol_simpleBfield(xwidth=BsizeX, yheight=BsizeY, zdepth=BsizeZ, Bx=0, By=By1, Bz=0) AT (0, 0, Bfield1start) RELATIVE Origin COMPONENT B_field_stop1=Pol_simpleBfield_stop(magnet_comp_stop=B_field1) AT (0, 0, Bfield1stop) RELATIVE Origin // ************************* // analyzer and detectors // ************************* COMPONENT analyser = Analyser_ideal(mx=1, my=0, mz=0) AT (0, 0, Bfield1stop+1) RELATIVE Origin COMPONENT PSD = PSD_monitor(nx=1, ny=1, filename="PSD", xwidth=detsize, yheight=detsize) AT (0, 0, Bfield1stop+1.0002) RELATIVE Origin FINALLY %{ %} END -------------- next part -------------- /******************************************************************************* * McStas instrument definition URL=http://www.mcstas.org * * Instrument: TestLarmorOnlysource * * %Identification * Release: McStas 2.2 * * %Description * only source and detector * * * %End *******************************************************************************/ DEFINE INSTRUMENT TestLarmorOnlysource( Lambda= 2.1, DLambda= 0.1, sourcefocusdist = 100, detsize=0.5, polarizerpos = 0.5 ) DECLARE %{ %} INITIALIZE %{ %} TRACE COMPONENT Origin = Progress_bar() AT (0, 0, 0) ABSOLUTE COMPONENT Source = Source_simple( radius = 0.00, yheight = 0.01, xwidth = 0.01, dist = sourcefocusdist, focus_xw = 0.01, focus_yh = 0.01, lambda0 = Lambda, dlambda = DLambda * Lambda) AT (0, 0, 0) RELATIVE Origin COMPONENT PSD = PSD_monitor(nx=1, ny=1, filename="PSD", xwidth=detsize, yheight=detsize) AT (0, 0, polarizerpos+1.0002) RELATIVE Origin FINALLY %{ %} END -------------- next part -------------- A non-text attachment was scrubbed... Name: example-Larmor-shift-linlin-01.png Type: image/png Size: 62092 bytes Desc: not available URL: From erkn at fysik.dtu.dk Tue Mar 3 08:10:46 2015 From: erkn at fysik.dtu.dk (Erik B Knudsen) Date: Tue, 3 Mar 2015 08:10:46 +0100 Subject: [mcstas-users] Pol_simpleBfield : wrong intensity(?) In-Reply-To: <54F45ADE.2090708@tudelft.nl> References: <54F45ADE.2090708@tudelft.nl> Message-ID: <54F55E76.3060900@fysik.dtu.dk> Dear Andre and others, I can confirm this irregular behaviour on my linux system with a McStas 2.1. I have therefore opened a ticket on the matter in our bug-tracking system, and will investigate the matter further asap. Please stay tuned. cheers Erik On 02/03/15 13:43, Andr? Kusmin wrote: > Hi everyone, > > I noticed that in a simple polarized neutron instrument > made of source, polarizer, precession field, analyzer > the resulting signal, as expected, oscillates as cos(const*lambda*B*L) > but at B=0, the intensity of the signal is less than 100% (see attached > PNG, plotted intensity against two different lengths of magnetic field > regions). > > It turns out that intensity at B*L=0 is correct. > > For 100 % polarized beam and zero precession field the intensity after > the analyzer is 4.2e-14 > (with TestLarmor.out) > The same intensity I get with ./TestLarmorOnlysource.out > but when I set non zero field in precession region I get even larger > intensity, which is impossible. > > Test can be done with two attached instr files and commands: > > ./TestLarmor.out By1=0 -n 1e5 DLambda=0.000001 > ./TestLarmor.out By1=0.000001 -n 1e5 DLambda=0.000001 > ./TestLarmorOnlysource.out -n 1e5 DLambda=0.000001 > > could anyone please check if this is reproducible? > perhaps I miss something. > > I have McStas pre2.2 (compiled from SVN) on linux multilib 64 bit > (Slackware) > > > best regards > Andre > > > > > > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > -- Erik Bergb?ck Knudsen, Research Engineer | DTU | morituri NEXMAP, DTU Fysik, DK-2800 Kgs. Lyngby, Denmark |<>-<>| te phone: (+45) 2132 6655 |<>-<>| salutant From 104pet104 at gmail.com Tue Mar 10 15:45:22 2015 From: 104pet104 at gmail.com (=?UTF-8?B?0J/QtdGC0YAg0JrQvtC90LjQug==?=) Date: Tue, 10 Mar 2015 18:45:22 +0400 Subject: [mcstas-users] Possible guide_gravity bug Message-ID: Hello everybody! I have strange behavior while simulating S-curved guide. I make it of several Guide-gravity comps rotated relative each other. If I curve guide in horizontal direction - everything is ok. If I curve the guide in vertical direction there are two variants. If the first part is curved down then once again everything is ok. But if I start with curving up no neutrons reach the end of guide. This is the second time I get this problem. The file is attached. Thanks -------------- next part -------------- A non-text attachment was scrubbed... Name: SANS2.instr Type: application/octet-stream Size: 14340 bytes Desc: not available URL: From Jean-Francois.Moulin at hzg.de Wed Mar 11 14:51:51 2015 From: Jean-Francois.Moulin at hzg.de (Jean-Francois.Moulin at hzg.de) Date: Wed, 11 Mar 2015 14:51:51 +0100 Subject: [mcstas-users] instr compilation fails Message-ID: Hi! on a newly installed Mint 17.1 64 bit I installed Mcstas 2.1 from repo. I was able to run some simulations but it seems that when an instr needs compilation, I get into trouble: jfmoulin at jfmlap:~/Lab/MCarlo/McStas$ mcgui refsans.instr [jfmlap:03276] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 231 [jfmlap:03276] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file ess_singleton_module.c at line 140 [jfmlap:03276] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file runtime/orte_init.c at line 128 -------------------------------------------------------------------------- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -------------------------------------------------------------------------- -------------------------------------------------------------------------- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -------------------------------------------------------------------------- -------------------------------------------------------------------------- Sorry! You were supposed to get help about: mpi_errors_are_fatal unknown handle But I couldn't open the help file: /usr/share/openmpi/help-mpi-errors.txt: No such file or directory. Sorry! -------------------------------------------------------------------------- -------------------------------------------------------------------------- Sorry! You were supposed to get help about: ompi mpi abort:cannot guarantee all killed But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime.txt: No such file or directory. Sorry! -------------------------------------------------------------------------- Any help appreciated! cheers JF - Helmholtz Zentrum Geesthacht Institut f?r Werkstoffforschung Abteilung WPN, Instrument REFSANS Lichtenbergstr. 1 85747 Garching FRM II Tel.: +49 (0)89 289 10762 Internet: http://www.frm2.tum.de Helmholtz-Zentrum Geesthacht Zentrum f?r Material- und K?stenforschung GmbH Max-Planck-Stra?e 1 I 21502 Geesthacht I Deutschland/Germany Gesch?ftsf?hrer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Gan? Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus Amtsgericht L?beck HRB 285 GE (Register Court) Internet: http://www.hzg.de From farhi at ill.eu Wed Mar 11 15:22:58 2015 From: farhi at ill.eu (Emmanuel FARHI) Date: Wed, 11 Mar 2015 15:22:58 +0100 Subject: [mcstas-users] instr compilation fails In-Reply-To: References: Message-ID: <55004FC2.90707@ill.eu> An HTML attachment was scrubbed... URL: From 104pet104 at gmail.com Wed Mar 18 18:46:52 2015 From: 104pet104 at gmail.com (=?UTF-8?B?0J/QtdGC0YAg0JrQvtC90LjQug==?=) Date: Wed, 18 Mar 2015 21:46:52 +0400 Subject: [mcstas-users] mcstas-users Digest, Vol 35, Issue 3 In-Reply-To: References: Message-ID: Dear Erik, how is it going with porting Perfect_crystal comp to McStas or making manual how to do it for us? Best regards, Peter Konik 2015-01-30 15:00 GMT+04:00 : > Send mcstas-users mailing list submissions to > mcstas-users at mcstas.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > or, via email, send a message with subject or body 'help' to > mcstas-users-request at mcstas.org > > You can reach the person managing the list at > mcstas-users-owner at mcstas.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mcstas-users digest..." > > > Today's Topics: > > 1. Re: mcstas-users Digest, Vol 35, Issue 2 (???? ?????) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Jan 2015 16:55:35 +0400 > From: ???? ????? <104pet104 at gmail.com> > To: mcstas-users at mcstas.org > Subject: Re: [mcstas-users] mcstas-users Digest, Vol 35, Issue 2 > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Dear Erik, > > we are working on simulations of double crystal diffractometer, so we > speak on Si crystals with Darwin curve reflections. > > Best regards, > Peter Konik > > 2015-01-28 15:00 GMT+04:00 : >> Send mcstas-users mailing list submissions to >> mcstas-users at mcstas.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >> or, via email, send a message with subject or body 'help' to >> mcstas-users-request at mcstas.org >> >> You can reach the person managing the list at >> mcstas-users-owner at mcstas.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of mcstas-users digest..." >> >> >> Today's Topics: >> >> 1. Perfect crystals (???? ?????) >> 2. Re: Perfect crystals (Erik B Knudsen) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 27 Jan 2015 23:08:41 +0400 >> From: ???? ????? <104pet104 at gmail.com> >> To: mcstas-users at mcstas.org >> Subject: [mcstas-users] Perfect crystals >> Message-ID: >> >> Content-Type: text/plain; charset=UTF-8 >> >> Hello everybody! >> >> Currently we are working on several simulation project and the >> question has arised how to handle perfect Si crystals? We think of >> crystal with small mosaicity or mirror with corresponding reflectivity >> profile. Is there any more native and general approach? >> >> Best regards, >> Peter Konik >> >> >> ------------------------------ >> >> Message: 2 >> Date: Wed, 28 Jan 2015 11:34:30 +0100 >> From: Erik B Knudsen >> To: >> Subject: Re: [mcstas-users] Perfect crystals >> Message-ID: <54C8BB36.3000207 at fysik.dtu.dk> >> Content-Type: text/plain; charset="UTF-8"; format=flowed >> >> Dear Peter, >> >> This depends really on how perfect your crystal is. The Single_crystal component distributed with McStas >> currently regards mosaicity as a gaussian approximation, and as such might not be appropriate for use >> with perfect crystals. >> In case of a Darwin width dominated crystal, we could possibly modify >> the Perfect_crystal component that exists in McXtrace (the X-ray sister of McStas) to handle neutrons instead. >> It has some other limitations but this can also be extended. This shouldn't be very difficult to do. >> >> I guess the appropriate route depends a lot on what it is exactly you want to do and more details about the actual >> crystals. Could you be a little more specific? For sure we'd be happy to help you along. >> >> cheers >> Erik >> >> On 27/01/15 20:08, ???? ????? wrote: >>> Hello everybody! >>> >>> Currently we are working on several simulation project and the >>> question has arised how to handle perfect Si crystals? We think of >>> crystal with small mosaicity or mirror with corresponding reflectivity >>> profile. Is there any more native and general approach? >>> >>> Best regards, >>> Peter Konik >>> _______________________________________________ >>> mcstas-users mailing list >>> mcstas-users at mcstas.org >>> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >>> >> >> -- >> Erik Bergb?ck Knudsen, Research Engineer | DTU | morituri >> NEXMAP, DTU Fysik, DK-2800 Kgs. Lyngby, Denmark |<>-<>| te >> phone: (+45) 2132 6655 |<>-<>| salutant >> >> >> >> ------------------------------ >> >> _______________________________________________ >> mcstas-users mailing list >> mcstas-users at mcstas.org >> http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users >> >> >> End of mcstas-users Digest, Vol 35, Issue 2 >> ******************************************* > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > mcstas-users mailing list > mcstas-users at mcstas.org > http://mailman.mcstas.org/cgi-bin/mailman/listinfo/mcstas-users > > > ------------------------------ > > End of mcstas-users Digest, Vol 35, Issue 3 > *******************************************