Minor bugs in the new versions
Dear Bruce, I installed the new versions of the programs. Many thanks for your ongoing work and especially for the new feature of exporting parameter values in Athena. While working with the new versions I listed the problems that I still ran over (all just minor problems that are not critical or for which I figured out a workaround). Some of the bugs have already been mentioned, but I was not sure if they should already be fixed with this release - if not please just ignore these points. Hope it helps to improve the software. My System is Win2000. Artemis 0.7.003 - After the update the path to the stash-folder is set to the default path: "c:\Program Files\Ifeffit\horae\stash" although my Ifeffit is installed at "c:\Programme\Ifeffit" and previously the stash folder was "c:\Programme\Ifeffit\horae\stash". Is it possible to set the stash folder automatically to the subfolder in the installation directory? Obviously, this should be corrected via: Options | General | Workspace. But Artemis will not let me do that. I included the messages that Artemis gives when I change the path and press "Save changes to future sessions" and "return to main window". In the latter case Artemis will ask if I want to keep changes for future sessions (obviously it recognizes that changes have not been saved) but will not return to the main program (and not change the path). However, it does affect working with Artemis in any other way (as far as I can tell). - Atoms potential cards (in feff.inp) is sometimes wrong. (work-around: enlarge r_max in atoms.inp) - Artemis will stumple if I try to import 30 paths (my default) but feff generated less than that (no paths will be loaded and and error message generated, see ARTEMIS Import.TRAP). - If I run feff, import 30 paths and then do that a second time, Artemis does not delete the old entries in the "data&paths"-window but just append the new entries with names "feff0001.dat:2" etc., is that the intended behaviour? The problem is that if I decrease r_max in feff.inp before doing the second run (to a value so that feff produces less than 30 path-files) Artemis will generate error messages when trying to plot the first path entries (obviously because they dont exist anymore). - Function "discard this dataset" does not delete the main folder "data0.feff.0". Therefore, after deleting a few FEFF-datasets I end up with a lot of folders "data0.feff.x", because the empty ones are not reused. The function also does not delete the corresponding parameter values (which is probably better than deleting them). - Set-up of Atoms/Feff-page before loading a datafile will lead to errors (already discussed) Athena 0.8.027 - Athena does not start when Artemis is running. Two new Windows will show up for a moment in the taskbar and disappear again, no error logs are written to the stash-folder. No problems occur if Artemis is not running. Also Artemis will not start when Athena is running. - When using the export function via "File | Save marked groups as data" Athena will state that I may not export more than 15 datafiles. But it also produces errors with less files: it seems that the maximum line width is limited to 259 characters. The line with the names of the datagroups is usually longer and therefore gets truncated. - Access to last opened files is not released: it is not possible to rename/delete project files that just have been closed or data files that just have been read in. This is possible after a new project file is opened or a new data file imported. - Sometimes the selection of groups gets faulty: when clicking on one of the groups it will not be highlighted. Instead the previously selected group will be redisplayed (and remains highlighted). Sometimes a completly different group will be highlighted and displayed. Closing and reopening will not solve the problem, but restarting of Athena does. I could not figure out how to reproduce this error and nothing is written to the stash-folder. - Athena sometimes resizes the width of the right panel (Data groups) by itself. E.g. when exporting data via "File | Save chi(R)" the window becomes wider and gets small again when clicking on a datagroup afterwards (but not always ?!). Atoms ? - I am not sure about the version number because "Help"|"About Atoms" displays "left" (?!) instead of version number. - The "Browse Space Groups" will still invoke the browser only once. Hephaestus 0.01 - Multiple choosing of Settings | Energies will TOGGLE between display in energies/wavelengths (instead of just keeping displaying in terms of energy). Moreover, the checkmark in the Settings-Dialog will stay at "Energies", even when displaying in wavelengts. Despite of this I would propose to display the unit on the main page anyway. - On my machine the checkmarks are hard to recognize as they only shown up as two tiny red dots. But they will show up as checkmarks when I hover over them with the mouse. (This behaviour is common to all the programs, also in previous versions). I also have some general question: - Is it possible to do an offline installation on a computer not connected to the internet? (e.g. by manually loading the updates-files and changing "update_site" in updater.ini) - Is there a way in Athena to display the raw data of a group as a text file? Athena will not allow to edit this data via "Edit | Edit data as text". I only had the idea of saving the group and looking at the resulting text file. - This raised another point: if I compare the file I read into Athena with the file I exported then I notice that they have a different scaling (abszissae values) - does Athena automatically change the scaling when importing data files? I also noticed that when exporting multiple groups then all groups are scaled to the same abszissae values which is not the case when I export them separately. Regards, Gerrit
Hi Gerrit, I can answer one of your questions:
- Is it possible to do an offline installation on a computer not connected to the internet? (e.g. by manually loading the updates-files and changing "update_site" in updater.ini)
Yes, it should be possible to change update_site in updater.ini. You'd want to copy the contents of the current update site to another web site. I don't know if anyone else has tried this, but I have used this setting for testing purposes. In principle, we could put the updates on Sourceforge.net as well. You can also manually download all the ifup_XXX.zip files, and unpack them with WinZip or any other program in order (so that ifup_002.zip overwrites updates from ifup_001.zip, and so forth) into C:\Program Files\Ifeffit, or wherever you installed Ifeffit. See http://cars9.uchicago.edu/cgi-bin/ifeffit/faqwiz?req=show&file=faq02.008.htp for more details about the updater. --Matt
Gerrit, Thanks for the extremely well thought out and useful bug/suggestion report. I am aiming to make a full release in the third or fourth week of May and I will try to adress most of your points before then. I have a few immediate comments:
- After the update the path to the stash-folder is set to the default path: "c:\Program Files\Ifeffit\horae\stash" although my Ifeffit is installed at "c:\Programme\Ifeffit" and previously the stash folder was "c:\Programme\Ifeffit\horae\stash". Is it possible to set the stash folder automatically to the subfolder in the installation directory?
This is really surprising behavior and may indicate a problem in our windows installer or updater. On windows and by default, Artemis uses the environment variable IFEFFIT_DIR to determine the location of the stash folder (as well as a few other folders). Specifically it is set to $ENV{IFEFFIT_DIR}\horae\stash. The IFEFFIT_DIR variable is set by the batch file, which gets created during installation. When you double click on the desktop icon or use the Start menu, that batch file gets executed. The batch file sets a few environmental variables, then calls the artemis executable. Since those variables were set by the batch file, they are available to the artemis process. It appears that something is going awry in the installation/update process. You should check that the desktop and Start menu shortcuts are still pointing to the correct batch file and that the batch file correctly sets the IFEFFIT_DIR variable. If any part of that is wrong, it would be useful to start from scratch, that is to run the installer and check all those things, then apply the updates and check again. Perhaps some step of that game is being done incorrectly. If all of that appears to be set correctly, then I'll keep searching for the problem, although at the moment I don't see how artemis can get it wrong if the batch file is correct.
Obviously, this should be corrected via: Options | General | Workspace. But Artemis will not let me do that. I included the messages that
And I thought that worked, but I probably did not test it well enough.
- Atoms potential cards (in feff.inp) is sometimes wrong. (work-around: enlarge r_max in atoms.inp)
You and others have mentioned this in recent months. I am aware of the problem, but the solution is going to require a lot of work. I have been procrastinating ;-) Fortunately, there is, as you say, a simple work-around.
- If I run feff, import 30 paths and then do that a second time, Artemis does not delete the old entries in the "data&paths"-window but just append the new entries with names "feff0001.dat:2" etc., is that the intended behaviour?
Yes. Either use the "Import no paths option" or delete all paths from the list before rerunning feff. The entry in the list for "feff0001.dat" just has a pointer to the feff0001.dat file. If the file changes because you reran feff, it will point at the new file. This is, admitedly, awkward behavior. However, the problem of handling the situation of rerunning feff and having Artemis certainly do the "right thing" is surprisingly subtle. I have a lot of work to do before Artemis will behave any differently from how it currently behaves.
Athena 0.8.027 - Athena does not start when Artemis is running. Two new Windows will show up for a moment in the taskbar and disappear again, no error logs are written to the stash-folder. No problems occur if Artemis is not running. Also Artemis will not start when Athena is running.
This is almost certainly a memory management problem -- an unfortunate confluence of the memory model in windows 2K and the fact that Ifeffit is written in fortran and statically allocates a large amount of memory. I believe the only solutions are to use only one at a time or to put more memory in your computer. You might get some more infomration about the problem if you were to open a comand window and run the artemis batch file by hand. Then if any message get generated, they won't disappear because the window disappears (as it does when the taskbar items show up momentarily).
- Sometimes the selection of groups gets faulty: when clicking on one of the groups it will not be highlighted. Instead the previously selected group will be redisplayed (and remains highlighted). Sometimes a completly different group will be highlighted and displayed. Closing and reopening will not solve the problem, but restarting of Athena does. I could not figure out how to reproduce this error and nothing is written to the stash-folder.
You are not the first to mention this, but I have, thus far, been unable to reproduce this myself. If you can send me a recipe guaranteed to show this, that would be very helpful.
- Athena sometimes resizes the width of the right panel (Data groups) by itself. E.g. when exporting data via "File | Save chi(R)" the window becomes wider and gets small again when clicking on a datagroup afterwards (but not always ?!).
This is probably because a message was written to the echo area that was longer than the echo area is wide. I have been meaning to fix that problem.
Atoms ? - I am not sure about the version number because "Help"|"About Atoms" displays "left" (?!) instead of version number. - The "Browse Space Groups" will still invoke the browser only once.
Fixing Atoms is quite low on my list of priorities. Don't be surprised if time passes and these don't get addressed.
- Is there a way in Athena to display the raw data of a group as a text file? Athena will not allow to edit this data via "Edit | Edit data as text". I only had the idea of saving the group and looking at the resulting text file.
Only during the session in which the original data file was imported. In that case, Athena still knows about the raw data file and so can display it as text. After saving and reading a project file, Athena no longer knows where the original data was. It never occured to me that one might want to edit a data group as text. Saving and looking at the text file is the only way to do so at this time. I'll put this on the todo list.
- This raised another point: if I compare the file I read into Athena with the file I exported then I notice that they have a different scaling (abszissae values) - does Athena automatically change the scaling when importing data files? I also noticed that when exporting multiple groups then all groups are scaled to the same abszissae values which is not the case when I export them separately.
I don't understand the question. Why don't you send me some data that demonstrates what you are asking about. B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 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/
Hello Matt and Bruce, thanks for the immediate answers.
Yes, it should be possible to change update_site in updater.ini. You'd want to copy the contents of the current update site to another web site. You can also manually download all the ifup_XXX.zip files,
I think I now understand how to do that. Actually I did not want to change update_site to another website but to a local folder (is that also possible?) but if it is sufficient just to overwrite the installation directory with the content of the zip-files thats even easier for me. Bruce Ravel schrieb:
- After the update the path to the stash-folder is set to the default path: "c:\Program Files\Ifeffit\horae\stash" although my Ifeffit is installed at "c:\Programme\Ifeffit" and previously the stash folder was "c:\Programme\Ifeffit\horae\stash". Is it possible to set the stash folder automatically to the subfolder in the installation directory?
On windows and by default, Artemis uses the environment variable IFEFFIT_DIR to determine the location of the stash folder (as well as a few other folders). Specifically it is set to $ENV{IFEFFIT_DIR}\horae\stash. The IFEFFIT_DIR variable is set by the batch file, which gets created during installation. When you double click on the desktop icon or use the Start menu, that batch file gets executed. The batch file sets a few environmental variables, then calls the artemis executable. Since those variables were set by the batch file, they are available to the artemis process.
It appears that something is going awry in the installation/update process. You should check that the desktop and Start menu shortcuts are still pointing to the correct batch file and that the batch file correctly sets the IFEFFIT_DIR variable. If any part of that is wrong, it would be useful to start from scratch, that is to run the installer and check all those things, then apply the updates and check again. Perhaps some step of that game is being done incorrectly.
If all of that appears to be set correctly, then I'll keep searching for the problem, although at the moment I don't see how artemis can get it wrong if the batch file is correct.
I checked the batch file but both the shortcut to the batch file as well as the batch file itself seem to be correct. I also did a new installation from scratch but the situation didn't change. Here is the content of artemis.bat: @echo off SET IFEFFIT_MAIN=C:\Programme\Ifeffit SET IFEFFIT_DIR=C:\Programme\Ifeffit SET PATH=%PATH%;%IFEFFIT_DIR% SET PGPLOT_DIR=%IFEFFIT_DIR% SET PGPLOT_DEV=/GW "%IFEFFIT_DIR%"\updater.exe cd "%IFEFFIT_DIR%" artemis.exe Immediatly after first start of Artemis the folder "C:\Program Files\Ifeffit\horae\stash\" is created where Artemis will store its files. I found these entries in "artemis.config" (windows= obviously points to the folder that ifeffit actually uses): default=~/.horae/stash/ windows=C:\\Program Files\\Ifeffit\\horae\\stash\\
Athena 0.8.027 - Athena does not start when Artemis is running. Two new Windows will show up for a moment in the taskbar and disappear again, no error logs are written to the stash-folder. No problems occur if Artemis is not running. Also Artemis will not start when Athena is running.
This is almost certainly a memory management problem -- an unfortunate confluence of the memory model in windows 2K and the fact that Ifeffit is written in fortran and statically allocates a large amount of memory. I believe the only solutions are to use only one at a time or to put more memory in your computer.
Well, I have 265MB RAM. But it did work with the previous versions. These are the error messages when I try to start Athena when Artemis is running and vice versa: c:\Programme\Ifeffit>athena.bat Ifeffit checked for updates recently. Can't load 'auto/Ifeffit/Ifeffit.dll' for module Ifeffit: load_file:Das angegebe ne Modul wurde nicht gefunden at /PerlApp/DynaLoader.pm line 212. BEGIN failed--compilation aborted at athena line 59. c:\Programme\Ifeffit>artemis.bat Ifeffit checked for updates recently. Can't load 'auto/Ifeffit/Ifeffit.dll' for module Ifeffit: load_file:Das angegebe ne Modul wurde nicht gefunden at /PerlApp/DynaLoader.pm line 212. BEGIN failed--compilation aborted at artemis line 53. ("Das angegebene Modul wurde nicht gefunden at.." means: "The specified modul was not found at ..")
- Sometimes the selection of groups gets faulty: when clicking on one of You are not the first to mention this, but I have, thus far, been unable to reproduce this myself. If you can send me a recipe guaranteed to show this, that would be very helpful.
I don't know myself.
- Is there a way in Athena to display the raw data of a group as a text file? Athena will not allow to edit this data via "Edit | Edit data as text". I only had the idea of saving the group and looking at the resulting text file.
It never occured to me that one might want to edit a data group as text. Saving and looking at the text file is the only way to do so at this time. I'll put this on the todo list.
Actually I do not want to edit the data. It just happened to me that I wanted to check if a data group loaded into athena corresponds to an experimental file, i.e. was read from this file (because I changed filenames afterwards).
- This raised another point: if I compare the file I read into Athena with the file I exported then I notice that they have a different scaling (abszissae values) - does Athena automatically change the scaling when importing data files? I also noticed that when exporting multiple groups then all groups are scaled to the same abszissae values which is not the case when I export them separately.
I don't understand the question. Why don't you send me some data that demonstrates what you are asking about.
I made a mistake in my previous posting: athenatest.zip contains two experimental files: exp01.dat and exp02.dat with a (slightly) different scaling. I read them in and exported to exp01.xmu and exp02.xmu. The values indeed correspond exactly to the original files. But if I import both groups to a single file then the scaling of the first group will be used for both and the ordinate data from exp02 will be changed accordingly. How is this done, linear interpolation? Actually, I find this behaviour very useful: if I export many groups for display in an other program I can plot all of them versus the same abzissae-values. Is it possible to integrate that feature for export of single files as well? (as I now prefer that method because of the automatic parameter export). Regards, Gerrit
On Wednesday 28 April 2004 05:20 am, Schmithals wrote:
I checked the batch file but both the shortcut to the batch file as well as the batch file itself seem to be correct. I also did a new installation from scratch but the situation didn't change. Here is the content of artemis.bat:
@echo off SET IFEFFIT_MAIN=C:\Programme\Ifeffit SET IFEFFIT_DIR=C:\Programme\Ifeffit SET PATH=%PATH%;%IFEFFIT_DIR% SET PGPLOT_DIR=%IFEFFIT_DIR% SET PGPLOT_DEV=/GW "%IFEFFIT_DIR%"\updater.exe cd "%IFEFFIT_DIR%" artemis.exe
Immediatly after first start of Artemis the folder "C:\Program Files\Ifeffit\horae\stash\" is created where Artemis will store its files. I found these entries in "artemis.config" (windows= obviously points to the folder that ifeffit actually uses): default=~/.horae/stash/ windows=C:\\Program Files\\Ifeffit\\horae\\stash\\
Hmmm... it seems that I did not test the general.workspace configuration variable very well at all. I would say that you should just change that variable, but you said that changing it does not work. It seems that this is a bug and, so long as reconfiguring the variable does not work, it is a bug you will have to live with until the next release. Sorry. You might try editing the C:\wherever you installed\Ifeffit\horae\artemis.ini file by hand to change the workspace parameter in the general section (should be near the top) to read correctly. I think that should work even if the preferences dialog in Artemis does not. I'll try to have this fixed in the next release. B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 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/
On Wednesday 28 April 2004 05:20 am, Schmithals wrote:
>>Athena 0.8.027 >>- Athena does not start when Artemis is running. Two new Windows will >>show up for a moment in the taskbar and disappear again, no error logs >>are written to the stash-folder. No problems occur if Artemis is not >>running. Also Artemis will not start when Athena is running. > > This is almost certainly a memory management problem -- an unfortunate > confluence of the memory model in windows 2K and the fact that Ifeffit > is written in fortran and statically allocates a large amount of > memory. I believe the only solutions are to use only one at a time or > to put more memory in your computer.
Well, I have 265MB RAM. But it did work with the previous versions. These are the error messages when I try to start Athena when Artemis is running and vice versa:
c:\Programme\Ifeffit>athena.bat Ifeffit checked for updates recently. Can't load 'auto/Ifeffit/Ifeffit.dll' for module Ifeffit: load_file:Das angegebe ne Modul wurde nicht gefunden at /PerlApp/DynaLoader.pm line 212. BEGIN failed--compilation aborted at athena line 59.
c:\Programme\Ifeffit>artemis.bat Ifeffit checked for updates recently. Can't load 'auto/Ifeffit/Ifeffit.dll' for module Ifeffit: load_file:Das angegebe ne Modul wurde nicht gefunden at /PerlApp/DynaLoader.pm line 212. BEGIN failed--compilation aborted at artemis line 53.
("Das angegebene Modul wurde nicht gefunden at.." means: "The specified modul was not found at ..")
First off, thanks for the translation! My answer is essentially the same. Either there is a memory conflict or the running program is putting a lock on the Ifeffit.dll file. Hopefully someone out who knows more about Windows than I do can comment on this.... B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 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/
On Wednesday 28 April 2004 05:20 am, Schmithals wrote:
I made a mistake in my previous posting: athenatest.zip contains two experimental files: exp01.dat and exp02.dat with a (slightly) different scaling. I read them in and exported to exp01.xmu and exp02.xmu. The values indeed correspond exactly to the original files. But if I import both groups to a single file then the scaling of the first group will be used for both and the ordinate data from exp02 will be changed accordingly. How is this done, linear interpolation?
Aha! I misunderstood the question. You are refering to the energy grid on which the data are written out. I had thought that by "scaling" you were refering somehow to the height along the y-axis. Yes -- when Athena exports many data groups in one file, it selects the energy grid of the first marked group (i.e. the one occupying the top-most position in the group list) as the standard and then interpolates each of the other groups onto that energy grid using Ifeffit qinterp() function. This interpolation is necessary for a file with a single energy column. FYI, Athena also interpolates when doing a merge and in any other situation where a common energy grid is called for.
Actually, I find this behaviour very useful: if I export many groups for display in an other program I can plot all of them versus the same abzissae-values. Is it possible to integrate that feature for export of single files as well? (as I now prefer that method because of the automatic parameter export).
Sort of. It is possible to interpolate data as it is imported to the energy grid of the standard using the pre-processing feature of the column selection dialog. However any kind of e0 shift, either by calibration or alignment, would undo that. Athena should allow you to interpolate a group onto the grid of another group at any time. I'll put that on the to do list. B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 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 Gerrit,
Yes, it should be possible to change update_site in updater.ini. You'd want to copy the contents of the current update site to another web site. You can also manually download all the ifup_XXX.zip files,
I think I now understand how to do that. Actually I did not want to change update_site to another website but to a local folder (is that also possible?) but if it is sufficient just to overwrite the installation directory with the content of the zip-files thats even easier for me.
The update files must be on a web site. The updater reads the update level and zip files using normal web protocals, and reads only the updater.ini file and the current update level from the local disk. Since all it really does is download and unzip the update files for you, it's not that hard to do it by hand. On some of the other issues you're seeing: 1 artemis.config from ifup_008.zip has windows=C:\Program Files\Ifeffit\.... hardwired into it. Bruce might have an opinion on whether it's better to change this file by hand or just erase it and allow it to be remade. But it's probably going to cause similar problems for anyone who's installed somewhere other than C:\Program Files\Ifeffit 2 I can definitely run artemis and athena at the same on a Windows machine, so I doubt there's a lock on Perl's Ifeffit.dll. I'd assume that if other people could only run one of these at a time there would be many complaints. 3 On my WinXP box, athena and artemis each use about 55Mb at startup -- without reading in any data. That seems to be about 50% Ifeffit / 50% Perl/Tk (the ifeffit shell takes ~24Mb). I don't know enough about what changed to guess why the memory usage would've changed between versions of artemis and athena, but I think they should both be able to run in 256Mb. Anyway, I'd suggest watching the memory usage in TaskManager as you start athena and artemis to see if it really is a memory issue. Hope that helps, --Matt
On Wednesday 28 April 2004 03:01 pm, Matt Newville wrote:
1 artemis.config from ifup_008.zip has windows=C:\Program Files\Ifeffit\.... hardwired into it.
And that is most certainly a bug.
Bruce might have an opinion on whether it's better to change this file by hand or just erase it and allow it to be remade. But it's probably going to cause similar problems for anyone who's installed somewhere other than C:\Program Files\Ifeffit
I have coded up a solution to this problem, but I haven't fired up windows today, so it remains untested. Editing the artemis.config file will have no effect. (It's used at build time to create the artemis.rcw file and used at run time to populate the preferences dialog.) The relevant file, should you choose to edit it by hand, would be artemis.ini.
2 I can definitely run artemis and athena at the same on a Windows machine, so I doubt there's a lock on Perl's Ifeffit.dll. I'd assume that if other people could only run one of these at a time there would be many complaints.
Now, that's a good point! B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 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/
Matt Newville schrieb:
2 I can definitely run artemis and athena at the same on a Windows machine, so I doubt there's a lock on Perl's Ifeffit.dll. I'd assume that if other people could only run one of these at a time there would be many complaints.
3 On my WinXP box, athena and artemis each use about 55Mb at startup -- without reading in any data. That seems to be about 50% Ifeffit / 50% Perl/Tk (the ifeffit shell takes ~24Mb). I don't know enough about what changed to guess why the memory usage would've changed between versions of artemis and athena, but I think they should both be able to run in 256Mb. Anyway, I'd suggest watching the memory usage in TaskManager as you start athena and artemis to see if it really is a memory issue.
I now think its a memory problem, too. My computer is running Win2000, 256 MB of RAM, virtual memory is fixed to 400 MB. I started the Windows Task manager to watch memory usage: - without any programs running (except virus scanner, ..) its 119 MB - After starting Artemis it goes up to 412 MB - Athena won't run Then I set the virtual memory to fixed 600 MB. - After starting Artemis it again takes ~400 MB - Athena now starts! Memory usage is ~700 MB. But shutting down one program before starting the other has been OK for me, too. Regards, Gerrit
participants (3)
-
Bruce Ravel -
Matt Newville -
Schmithals