RE: [Ifeffit] A question for Windows users
Hello Bruce, everybody you wrote:
Athena is not always particularly creative about the names it suggests for output files. For example, if you use the feature of saving several marked groups to a single output file, Athena suggests that the names be "marked.space". That is, if you save marked groups as chi(k), the suggested file name is "marked.chi". If you save marked groups as the real part of chi(R), the suggested file name is "marked.chir_re".
It is possible to configure Explorer such that it does not display file extensions (i.e. the bit after the dot). That might make it hard to tell different marked group output files apart if the suggested names are used.
Is this a problem for anyone? Should I change the suggested names such that the suggestive part is not in the extension? That is, would "chi.marked" and "chir_re.marked" be better names?
Actually, as a Window user (booo! hisss!), my first move is to have all the extensions appearing in Explorer, a basic security move (e.g., to avoid clicking on a "picture.gif" that actually corresponds to a "picture.gif.exe", with all undesirable consequences). I also find it much easier to keep the pre-dot part of the data file for the sample name, and the post-dot part for the data type (and I'm eternally grateful to Ifeffit to provide us miscellaneous and yet distinct extensions; no joke). Therefore, I suggest NOT to change the current feature. Best regards, Michel Schlegel
Michel, Thanks -- I completely agree. Our data collecion program (and at least one other at an APS beamline where athena is used heavily, and I suspect many others) use the file extension for scan number: datafile.001, datafile.002, ... On top of that, many of the analysis programs (at least the ones I use!) keep related files as datafile.xmu, datafile.chi, datafile.rsp, ... Because of this, I find the Windows 'hide file extensions' to be completely unusable for handling real data analysis based on small ascii files. I make sure this feature is turned off on all our beamline computers where people will be running athena, artemis, and sixpack, and wouldn't expect athena to try to recover from Windows "very clever" ability to hide file extenstions... --Matt
Michel and Matt, Thanks for the feedback. I am of the same opinion as both of you, both about how the bit after the dot should be used and about Explorer's annoying hide-the-extension feature. However, in developing software, there is always the issue that the software might behave in a way that will confuse the user for reasons that are entirely procedural and not central to the function of the software or the chore it attempts to perform. I sometimes have trouble guaging which features of my programs will fail in that way since I am (1) intimately familiar with how my programs operate, and (2) a rather idiosyncratic computer user to begin with. Fortunately, I now have the resource of our mailing list to help me when I get confused about these things. Thanks for the help. 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, X24c, U4b 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/
participants (3)
-
Bruce Ravel
-
Matt Newville
-
SCHLEGEL Michel 177447