Random behaviour Artemis 0.7.001
Hi to all, I'm a new ifeffit user (I started using this software in october '03). My environment: Linux Debian/GNU, perl 5.008003, Tk 800.024 and Ifeffit 1.2.5 First of all, I would like to express my congratulations to the authors and thanks them all for their work. I updated the new versions last week and I appreciate the new more user friendly layout. But I found some strange behaviour with Artemis. 1. When Artemis starts, I receive this message: Use of uninitialized value in join or string at /usr/local/bin/artemis line 1236 2. Sometimes I save a project and when I reopen it doesn't found the datafiles (obviously I didn't modify the file names). 3. Sometimes the fit have no-sense values so I have to save the project, rerun Artemis, and with the same parameters I obtain good fit. It seems like after a certain number of fits the software starts to fail. I would like to know if someone have noticed the same behaviour. The problem is that points 2,3 are random. Thanks, Mauro
On Wednesday 17 March 2004 06:41 am, mauro@rulp.org wrote:
First of all, I would like to express my congratulations to the authors and thanks them all for their work.
Thanks for the kind words.
1. When Artemis starts, I receive this message:
Use of uninitialized value in join or string at /usr/local/bin/artemis line 1236
You can safely ignore this. This error happens as artemis tries to initialize the string that gets put in the "Prepared by" slot of the project properties. I will be more careful about how I initialize that string in the next release, but I am confident that nothing bad is happening.
2. Sometimes I save a project and when I reopen it doesn't found the datafiles (obviously I didn't modify the file names).
I have never seen this happen. (I mostly work on one SuSE linux system or another -- all the other stats are the same as what you quoted.) You should send me an example. Or, even, better, send me a detailed recipe for reproducing the problem on my computer. When this happens, is anything written to the screen? Does Artemis beep and tell you to look at the ARTEMIS.TRAP file? If either is the case, I will need to see what they say.
3. Sometimes the fit have no-sense values so I have to save the project, rerun Artemis, and with the same parameters I obtain good fit. It seems like after a certain number of fits the software starts to fail.
This one I *have* seen. My current hypothesis is that I am using ifeffit's erase() command in a way that is flakey. Unfortunately, I haven't been able to come up with a simple enough demonstration of the problem to merit complaining to Matt about it. Indeed, I am not sure that erase() is really the problem. In any case, I changed how erase() is used in a few places in the version I am currently working on and haven't seen this problem recently. So, there is hope ;-) In the meantime, I don't have better advice than to save and restart. Thanks for the bug report -- hearing about these problems is the only way I can make the software better. And welcome to the ifeffit family! B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 222 Naval Research Laboratory phone: (1) 202 767 5947 Washington DC 20375, USA fax: (1) 202 767 1697 NRL Synchrotron Radiation Consortium (NRL-SRC) Beamlines X11a, X11b, X23b National Synchrotron Light Source Brookhaven National Laboratory, Upton, NY 11973 My homepage: http://feff.phys.washington.edu/~ravel EXAFS software: http://feff.phys.washington.edu/~ravel/software/exafs/
Hi all,
3. Sometimes the fit have no-sense values so I have to save the project, rerun Artemis, and with the same parameters I obtain good fit. It seems like after a certain number of fits the software starts to fail.
This one I *have* seen. My current hypothesis is that I am using ifeffit's erase() command in a way that is flakey. Unfortunately, I haven't been able to come up with a simple enough demonstration of the problem to merit complaining to Matt about it. Indeed, I am not sure that erase() is really the problem. In any case, I changed how erase() is used in a few places in the version I am currently working on and haven't seen this problem recently. So, there is hope ;-) In the meantime, I don't have better advice than to save and restart.
I have also experienced the same problem when using "gifeffit", not artemis. Sometimes a "mutant" of this bug appears with the fit parameters staying okay, but the errors increasing with each fit attempt to enormous values. Unfortunately I also didn't find a cause -> effect relation until now. Best, Peter -- -------------------------------------------------------------- Peter Pfalzer Universitaet Augsburg Tel: +49-821-598-3215 Lehrstuhl fuer Experimentalphysik II Fax: +49-821-598-3411 Universitaetsstr. 1 D-86135 Augsburg Germany Peter.Pfalzer@physik.uni-augsburg.de http://www.physik.uni-augsburg.de/exp2 --------------------------------------------------------------
Mauro, Bruce, Peter,
3. Sometimes the fit have no-sense values so I have to save the project, rerun Artemis, and with the same parameters I obtain good fit. It seems like after a certain number of fits the software starts to fail.
This one I *have* seen. My current hypothesis is that I am using ifeffit's erase() command in a way that is flakey. Unfortunately, I haven't been able to come up with a simple enough demonstration of the problem to merit complaining to Matt about it. Indeed, I am not sure that erase() is really the problem. In any case, I changed how erase() is used in a few places in the version I am currently working on and haven't seen this problem recently. So, there is hope ;-) In the meantime, I don't have better advice than to save and restart.
I have also experienced the same problem when using "gifeffit", not artemis. Sometimes a "mutant" of this bug appears with the fit parameters staying okay, but the errors increasing with each fit attempt to enormous values. Unfortunately I also didn't find a cause -> effect relation until now.
For what it's worth, I agree that erase() seems to cause problems on some occassions, especially after multiple erase()'s and re-setting of arrays. I've also seen some odd problems using the slice() and interpolation functions in combination with the minimize() command. I have a hard time reproducing these problems myself, so they're difficult to diagnose. Sorry for the trouble!! --Matt
On Wed, Mar 17, 2004 at 08:30:02AM -0500, Bruce Ravel wrote:
On Wednesday 17 March 2004 06:41 am, mauro@rulp.org wrote:
2. Sometimes I save a project and when I reopen it doesn't found the datafiles (obviously I didn't modify the file names).
I have never seen this happen. (I mostly work on one SuSE linux system or another -- all the other stats are the same as what you quoted.)
You should send me an example. Or, even, better, send me a detailed recipe for reproducing the problem on my computer.
When this happens, is anything written to the screen? Does Artemis beep and tell you to look at the ARTEMIS.TRAP file? If either is the case, I will need to see what they say.
I had this problem with only two projects and passing from a Windows 2000 machine to my Linux (but with the identical directory/file structure). I wanted just to ask if someone had seen this problem before. If it will happen again I will send you the ARTEMIS.TRAP file. Thanks, Mauro
participants (4)
-
Bruce Ravel -
Matt Newville -
mauro＠rulp.org -
Peter Pfalzer