- Ifeffit - millenia.cars.aps.anl.gov

RE: [Ifeffit] RESTRAINTS IN IFEFFIT
by Kelly, Shelly D. 25 Jan '06

25 Jan '06

Hi Renato, See below for some comments: > > Hi Folks, this is my first message on the list. Perhaps someone could help > me. The subject is how to include restraints on exafs refinement. There is > just scanty information about this on the ifeffit reference manual. > > I'm trying to refine the exafs data of a rhombohedral perovskite. > > The main MS contributions to the signal at about 3.5 A (non phase correct) > arise from M - O - M interactions being M the absorber . We have a > significant SS path, a two-legged and a three-legged path. The structural > parameters of these three terms are correlated since all refers to the > same > A-B-C triangle and the A-B and B-C distances must be that found for > M-O1 nearest-neighbor configurations. For these reasons > we constrained the photo electron path length for three-legged to the > M-O nearest-neighbor distance:R(three-leg = 2*RM-O). [Kelly, Shelly D.] The three-leg path length is given by half the total path length. Calculated as R = (distance_AB + distance_BC + distance_AC) * 0.5 You know the distance from A-B and the distance from B-C but the distance from A-C is dependent on the angle of the triangle path. You can write an equation to determine the angle A. a^2 = b^2 + c^2 -2bc cos(A) where a=distance_AC, b=distance_AB, c=distance_BC and A is the angle opposite of the AC side of the triangle. Then the four leg path has a path length defined as R = (2*distance_AB + 2*distance_BC)*0.5 The single path from A to B has the distance R = (2*distance_AB)*0.5 The single path from A to C has the distance R = (2*distance_AC)*0.5 Which also depends on the angle A and distance_AB as defined above. So for your case you have one unknown length and one unknown bond angle to describe these path lengths. i.e. distance_AB=distance_BC is unknown and angle A is unknown. HTH Shelly I'm trying to > intoroduce the quantity defined as delta = R(three-legged)-R(two-legged) > and thus define the SS half path length as a function of delta R(SS) = R > (three-legged) - 2*delta. I think it is a restraint not a constraint. > So I defined (def) the delta function on the line above the command FEFFIT > also delr for the SS path. I introduced the restraint in the line FEFFIT > as > restraint = delrSS). The fit produce the same results as obtainde without > the definition of delta and delrSS (function of delta). > So I need to know how to introduce this restraint in the fit in order to > calculate de M - O - M bond angle (this angle should be calculated using > simple geometric relationships) - perhaps introduce the bond angle as a > restraint. > Someone can say me where I introduce the definitions of restraint > parameters? > > Thank you very much for your kind attention > > Renato Canha > > Universidade Federal do Rio Grande doNorte > Departamento de Quimica > Natal - RN - BRAZIL > Open WebMail Project (http://openwebmail.org) > > > ---------- Original Message ----------- > From: ifeffit-request(a)millenia.cars.aps.anl.gov > To: ifeffit(a)millenia.cars.aps.anl.gov > Sent: Mon, 23 Jan 2006 12:00:13 -0600 > Subject: Ifeffit Digest, Vol 35, Issue 14 > > > Send Ifeffit mailing list submissions to > > ifeffit(a)millenia.cars.aps.anl.gov > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit > > or, via email, send a message with subject or body 'help' to > > ifeffit-request(a)millenia.cars.aps.anl.gov > > > > You can reach the person managing the list at > > ifeffit-owner(a)millenia.cars.aps.anl.gov > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Ifeffit digest..." > > > > Today's Topics: > > > > 1. Re: Re: I should be able to find this somewhere... (Bruce Ravel) > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Sun, 22 Jan 2006 16:58:07 -0600 > > From: Bruce Ravel <bravel(a)anl.gov> > > Subject: Re: [Ifeffit] Re: I should be able to find this somewhere... > > To: XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> > > Message-ID: <200601221658.07513.bravel(a)anl.gov> > > Content-Type: text/plain; charset="iso-8859-1" > > > > Hi, > > > > In fact, Artemis and Athena both attempt to deal correctly with input > > chi(k) data that is not on the expected grid. Both codes perform a > > test to see if the data is on the standard grid and, if not, > > front-loads the data with zeros and uses Ifeffit's boxcar rebinning > > function to put the data on the expected grid. > > > > Alas, there was a bug in the rebinning macro used by A&A which caused > > it to fail in a particular situation met by the data in Matthew's > > example. This bug will be fixed in the next release. > > > > If you import mu(E) data into Athena and then import data from the > > Athena project file into Artemis, you will never see the problem that > > Matthew reported. > > > > B > > > > On Tuesday 17 January 2006 16:09, Matt Newville wrote: > > > Hi Matthew, Bruce, > > > > > > OK, I think it's a bug. Well, maybe it's just a consequence of a > > > "known but not well advertised" problem. > > > > > > The chi(k) data you have doesn't start at k=0. By itself, this should > > > be OK, and the fit seems to be mostly fine. There seems to be a bug > > > in Ifeffit that the output fit chi(k) has the same number of data > > > points as the input chi(k) data. In this case is incorrect -- it > > > should go to the last data point in k. From looking at the code, I'm > > > pretty sure this has no effect on the fit and is only an error in the > > > output array. But the shortened chi_fit(k) will have an impact on the > > > way Bruce is calculating the residual. Even if that were fixed, the > > > residual would still be wrong, as the residual in Artemis is > > > calculated as > > > set(data0_res.k = data0.k) > > > set(data0_res.chi = data0.chi - data0_fit.chi) > > > > > > and then Fourier transforming to R-space. Since the data and fit > > > aren't aligned in k-space, the residual is incorrect. It should be > > > > > > set(data0_res.chi = data0.chi - interp(data0_fit.k, data0_fit.chi, > > > data0.k)) > > > > > > or some variation on that. > > > > > > Sorry for the trouble. It's definitely a result of narrow-mindedly > > > expecting that all chi(k) data comes from Ifeffit/Athena and will > > > always start at k=0. We should get this fixed (it's mostly there!) so > > > that data from other sources can be used. Right now, the easiest > > > work-around is to pre-pack the chi(k) data with zeros (starting from > > > k=0.00) > > > > > > --Matt > > > > > > _______________________________________________ > > > Ifeffit mailing list > > > Ifeffit(a)millenia.cars.aps.anl.gov > > > http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit > > > > -- > > Bruce Ravel ---------------------------------------------- > bravel(a)anl.gov > > > > Molecular Environmental Science Group, Building 203, Room E-165 > > MRCAT, Sector 10, Advance Photon Source, Building 433, Room B007 > > > > Argonne National Laboratory phone and voice mail: (1) 630 > > 252 5033 Argonne IL 60439, USA fax: > > (1) 630 252 9793 > > > > My homepage: http://cars9.uchicago.edu/~ravel > > EXAFS software: http://cars9.uchicago.edu/~ravel/software/ > > > > ------------------------------ > > > > _______________________________________________ > > Ifeffit mailing list > > Ifeffit(a)millenia.cars.aps.anl.gov > > http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit > > > > End of Ifeffit Digest, Vol 35, Issue 14 > > *************************************** > ------- End of Original Message ------- > > _______________________________________________ > Ifeffit mailing list > Ifeffit(a)millenia.cars.aps.anl.gov > http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit

1 0

Re: Possible bug in Artemis. (Bruce Ravel)
by joshua jason kas 25 Jan '06

25 Jan '06

Hi Bruce, Thanks for the tips. I fooled around with the feff.inp and found that artemis somehow has a problem when feff is run with the RMULTIPLIER card. This card is purely for convenience, so I took it out and things work fine. This card was used in feff6 although the code runs very slowly with it for some reason. Anyway, here is the feff.inp file that I was using for feff6 or feff8 (they both have the problem). Thanks, Josh TITLE GeCl4 HOLE 1 1.0 CONTROL 1 1 1 1 1 1 (feff8) CONTROL 1 1 1 1 (feff6) PRINT 1 0 0 0 0 3 EXCHANGE 0 1 1 CORRECTIONS 1.2427845974 0.0041969513 RMAX 10.0 RMULTIPLIER 1.01 POTENTIALS 0 32 Ge -1 -1 1 1 17 Cl -1 -1 4 ATOMS 0.0000000000 0.0000000000 0.0000000000 0 1.1568027 1.1568027 1.1568027 1 Cl 1.1568027 -1.1568027 -1.1568027 1 Cl -1.1568027 1.1568027 -1.1568027 1 Cl -1.1568027 -1.1568027 1.1568027 1 Cl END > From: Bruce Ravel <bravel(a)anl.gov> > Subject: Re: [Ifeffit] Possible bug in Artemis. > To: XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> > Message-ID: <200601231845.59426.bravel(a)anl.gov> > Content-Type: text/plain; charset="iso-8859-1" > > On Monday 23 January 2006 17:47, joshua jason kas wrote: >> Hi, >> When I import a feff calculation, or run feff, the paths show up in >> artemis, but the description is garbled. What I mean is that the path >> description under Scattering Path which normally looks like >> >> [+] Cl [+] O ... >> >> looks like >> >> [+] <?> [+] <?> ... > > This looks like another version of a bug that has cropped up here and there. > The algorithm for generating the interpretation page parses the feff.inp file > and a couple of feff's output files. Every so often, someone throws a > hand-made feff.inp file at Artemis that works in feff but breaks the rather > crufty parser I wrote. > > If you can send me the feff.inp file that would help. The artemis project > file might help also, so send that along. Even if it is one that makes > Artemis do bad things when you try to read, I can still peak on the inside and > figure out what's going on. > > B > > > > -- > Bruce Ravel ---------------------------------------------- bravel(a)anl.gov > > Molecular Environmental Science Group, Building 203, Room E-165 > MRCAT, Sector 10, Advanced Photon Source, Building 433, Room B007 > > Argonne National Laboratory phone and voice mail: (1) 630 252 5033 > Argonne IL 60439, USA fax: (1) 630 252 9793 > > My homepage: http://cars9.uchicago.edu/~ravel > EXAFS software: http://cars9.uchicago.edu/~ravel/software/ > > > > ------------------------------ > > Message: 2 > Date: Mon, 23 Jan 2006 20:18:42 -0500 > From: "TAO, Ye" <yetao(a)chem.uga.edu> > Subject: Re: [Ifeffit] Possible bug in Artemis. > To: "XAFS Analysis using Ifeffit" <ifeffit(a)millenia.cars.aps.anl.gov> > Message-ID: <00f001c62084$1d8d28c0$3b05c080@RASD800> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > Josh, > > Have a try to set the absorber coordinate as origin (0 0 0) in feff.inp, > then it should work. > > Ye > ----- Original Message ----- > From: "joshua jason kas" <hebhop(a)u.washington.edu> > To: <ifeffit(a)millenia.cars.aps.anl.gov> > Sent: Monday, January 23, 2006 6:47 PM > Subject: [Ifeffit] Possible bug in Artemis. > > >> Hi, >> When I import a feff calculation, or run feff, the paths show up in >> artemis, but the description is garbled. What I mean is that the path >> description under Scattering Path which normally looks like >> >> [+] Cl [+] O ... >> >> looks like >> >> [+] <?> [+] <?> ... >> >> and if I save the project file and reopen it, it can't >> I have attached a screenshot. >> Here is some info on my software >> 1) artemis 0.8.004 >> 2) ifeffit 1.2.8 >> 3) perl -e 'use Tk; print $Tk::VERSION,$/' gives 804.027 >> 4) perl v5.8.7 >> >> I tried updating Tk, and that works about as well as it always has on my >> system. Most of the tests passed, a few failed. >> This may be a problem with my version of Linux, or my version of perl/Tk. >> Anyway, any help would be much appreciated. >> Thank you very much, >> Josh Kas > > > -------------------------------------------------------------------------------- > > >> _______________________________________________ >> Ifeffit mailing list >> Ifeffit(a)millenia.cars.aps.anl.gov >> http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit >> > > > > ------------------------------ > > Message: 3 > Date: Tue, 24 Jan 2006 11:43:30 -0300 > From: "Renato Canha Ambrosio" <rcanha(a)ccet.ufrn.br> > Subject: [Ifeffit] RESTRAINTS IN IFEFFIT > To: ifeffit(a)millenia.cars.aps.anl.gov > Message-ID: <20060124142316.M21887(a)ccet.ufrn.br> > Content-Type: text/plain; charset=iso-8859-1 > > Hi Folks, this is my first message on the list. Perhaps someone could help > me. The subject is how to include restraints on exafs refinement. There is > just scanty information about this on the ifeffit reference manual. > > I'm trying to refine the exafs data of a rhombohedral perovskite. > > The main MS contributions to the signal at about 3.5 A (non phase correct) > arise from M � O � M interactions being M the absorber . We have a > significant SS path, a two-legged and a three-legged path. The structural > parameters of these three terms are correlated since all refers to the same > A-B-C triangle and the A-B and B-C distances must be that found for > M-O1 nearest-neighbor configurations. For these reasons > we constrained the photo electron path length for three-legged to the > M-O nearest-neighbor distance:R(three-leg = 2*RM-O). I'm trying to > intoroduce the quantity defined as delta = R(three-legged)-R(two-legged) > and thus define the SS half path length as a function of delta R(SS) = R > (three-legged) - 2*delta. I think it is a restraint not a constraint. > So I defined (def) the delta function on the line above the command FEFFIT > also delr for the SS path. I introduced the restraint in the line FEFFIT as > restraint = delrSS). The fit produce the same results as obtainde without > the definition of delta and delrSS (function of delta). > So I need to know how to introduce this restraint in the fit in order to > calculate de M - O - M bond angle (this angle should be calculated using > simple geometric relationships) - perhaps introduce the bond angle as a > restraint. > Someone can say me where I introduce the definitions of restraint parameters? > > Thank you very much for your kind attention > > Renato Canha > > Universidade Federal do Rio Grande doNorte > Departamento de Quimica > Natal - RN - BRAZIL > Open WebMail Project (http://openwebmail.org) > > > ---------- Original Message ----------- > From: ifeffit-request(a)millenia.cars.aps.anl.gov > To: ifeffit(a)millenia.cars.aps.anl.gov > Sent: Mon, 23 Jan 2006 12:00:13 -0600 > Subject: Ifeffit Digest, Vol 35, Issue 14 > >> Send Ifeffit mailing list submissions to >> ifeffit(a)millenia.cars.aps.anl.gov >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit >> or, via email, send a message with subject or body 'help' to >> ifeffit-request(a)millenia.cars.aps.anl.gov >> >> You can reach the person managing the list at >> ifeffit-owner(a)millenia.cars.aps.anl.gov >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Ifeffit digest..." >> >> Today's Topics: >> >> 1. Re: Re: I should be able to find this somewhere... (Bruce Ravel) >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 22 Jan 2006 16:58:07 -0600 >> From: Bruce Ravel <bravel(a)anl.gov> >> Subject: Re: [Ifeffit] Re: I should be able to find this somewhere... >> To: XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> >> Message-ID: <200601221658.07513.bravel(a)anl.gov> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Hi, >> >> In fact, Artemis and Athena both attempt to deal correctly with input >> chi(k) data that is not on the expected grid. Both codes perform a >> test to see if the data is on the standard grid and, if not, >> front-loads the data with zeros and uses Ifeffit's boxcar rebinning >> function to put the data on the expected grid. >> >> Alas, there was a bug in the rebinning macro used by A&A which caused >> it to fail in a particular situation met by the data in Matthew's >> example. This bug will be fixed in the next release. >> >> If you import mu(E) data into Athena and then import data from the >> Athena project file into Artemis, you will never see the problem that >> Matthew reported. >> >> B >> >> On Tuesday 17 January 2006 16:09, Matt Newville wrote: >>> Hi Matthew, Bruce, >>> >>> OK, I think it's a bug. Well, maybe it's just a consequence of a >>> "known but not well advertised" problem. >>> >>> The chi(k) data you have doesn't start at k=0. By itself, this should >>> be OK, and the fit seems to be mostly fine. There seems to be a bug >>> in Ifeffit that the output fit chi(k) has the same number of data >>> points as the input chi(k) data. In this case is incorrect -- it >>> should go to the last data point in k. From looking at the code, I'm >>> pretty sure this has no effect on the fit and is only an error in the >>> output array. But the shortened chi_fit(k) will have an impact on the >>> way Bruce is calculating the residual. Even if that were fixed, the >>> residual would still be wrong, as the residual in Artemis is >>> calculated as >>> set(data0_res.k = data0.k) >>> set(data0_res.chi = data0.chi - data0_fit.chi) >>> >>> and then Fourier transforming to R-space. Since the data and fit >>> aren't aligned in k-space, the residual is incorrect. It should be >>> >>> set(data0_res.chi = data0.chi - interp(data0_fit.k, data0_fit.chi, >>> data0.k)) >>> >>> or some variation on that. >>> >>> Sorry for the trouble. It's definitely a result of narrow-mindedly >>> expecting that all chi(k) data comes from Ifeffit/Athena and will >>> always start at k=0. We should get this fixed (it's mostly there!) so >>> that data from other sources can be used. Right now, the easiest >>> work-around is to pre-pack the chi(k) data with zeros (starting from >>> k=0.00) >>> >>> --Matt >>> >>> _______________________________________________ >>> Ifeffit mailing list >>> Ifeffit(a)millenia.cars.aps.anl.gov >>> http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit >> >> -- >> Bruce Ravel ---------------------------------------------- bravel(a)anl.gov >> >> Molecular Environmental Science Group, Building 203, Room E-165 >> MRCAT, Sector 10, Advance Photon Source, Building 433, Room B007 >> >> Argonne National Laboratory phone and voice mail: (1) 630 >> 252 5033 Argonne IL 60439, USA fax: >> (1) 630 252 9793 >> >> My homepage: http://cars9.uchicago.edu/~ravel >> EXAFS software: http://cars9.uchicago.edu/~ravel/software/ >> >> ------------------------------ >> >> _______________________________________________ >> Ifeffit mailing list >> Ifeffit(a)millenia.cars.aps.anl.gov >> http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit >> >> End of Ifeffit Digest, Vol 35, Issue 14 >> *************************************** > ------- End of Original Message ------- > > > > ------------------------------ > > _______________________________________________ > Ifeffit mailing list > Ifeffit(a)millenia.cars.aps.anl.gov > http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit > > > End of Ifeffit Digest, Vol 35, Issue 16 > *************************************** >

2 1

Possible bug in Artemis.
by joshua jason kas 24 Jan '06

24 Jan '06

Hi, When I import a feff calculation, or run feff, the paths show up in artemis, but the description is garbled. What I mean is that the path description under Scattering Path which normally looks like [+] Cl [+] O ... looks like [+] <?> [+] <?> ... and if I save the project file and reopen it, it can't I have attached a screenshot. Here is some info on my software 1) artemis 0.8.004 2) ifeffit 1.2.8 3) perl -e 'use Tk; print $Tk::VERSION,$/' gives 804.027 4) perl v5.8.7 I tried updating Tk, and that works about as well as it always has on my system. Most of the tests passed, a few failed. This may be a problem with my version of Linux, or my version of perl/Tk. Anyway, any help would be much appreciated. Thank you very much, Josh Kas

3 2

Re: I should be able to find this somewhere...
by Bruce Ravel 22 Jan '06

22 Jan '06

On Friday 13 January 2006 20:25, you wrote: > By what factor is the residual multiplied when plotted in Artemis? I can't > find that figure quoted. > mam The residual is saved in k-space and Fourier transformed. B -- Bruce Ravel ---------------------------------------------- bravel(a)anl.gov Molecular Environmental Science Group, Building 203, Room E-165 MRCAT, Sector 10, Advanced Photon Source, Building 433, Room B007 Argonne National Laboratory phone and voice mail: (1) 630 252 5033 Argonne IL 60439, USA fax: (1) 630 252 9793 My homepage: http://cars9.uchicago.edu/~ravel EXAFS software: http://cars9.uchicago.edu/~ravel/software/

4 9

Re: moving the legend in Athena
by Bruce Ravel 20 Jan '06

20 Jan '06

On Thursday 19 January 2006 14:05, Carlo Segre wrote: > When I plot data using athena, I would like to move the legend. How can I > do this? Go to the preferences, then to the plot branch. key_x and key_y are the xy coordinates of the upper left corner of the legend box. key_dy is the spacing between lines. The answer is the same for Artemis. B -- Bruce Ravel ---------------------------------------------- bravel(a)anl.gov Molecular Environmental Science Group, Building 203, Room E-165 MRCAT, Sector 10, Advanced Photon Source, Building 433, Room B007 Argonne National Laboratory phone and voice mail: (1) 630 252 5033 Argonne IL 60439, USA fax: (1) 630 252 9793 My homepage: http://cars9.uchicago.edu/~ravel EXAFS software: http://cars9.uchicago.edu/~ravel/software/

2 1

Enabling auto-updater for Artemis etc on startup (Windows)
by Simon Granville 19 Jan '06

19 Jan '06

Hello and Happy New Year all, my first of possibly many questions to this list (so please be gentle!) should hopefully be an easy one. When at Matt's iFEFFIT session in Melbourne at the start of December, I changed something in the updater.inifile (in the config directory of ifeffit) so that Artemis and Athena didn't attempt to look for updates when those programs are started. Of course I did this from a hint by Matt - now I'd quite like to reenable that auo-update and I don't know what to change. I know there's a newer version or two out there (my Artemis version is 0.8.002). Here's what my updater.ini file looks like [updater] next_checktime = tomorrow update_site = http://cars9.uchicago.edu/ifeffit/updates/ timestamp = 1137635213.22 http_proxy = timeout_connect = 60.0 timeout_download = 2400.0 Cheers, Simon. Simon Granville PhD student MacDiarmid Institute for Advanced Materials and Nanotechnology Victoria University of Wellington Wellington New Zealand

2 1

Re: XANES calculations
by John J. Rehr 17 Jan '06

17 Jan '06

Dear Antonio, It appears that you've just experienced a common problem with hexagonal space groups that one often needs a shift of the origin to get the "correct" crystal structure. According to the atoms documentation (click on SHIFT in Webatoms) there should be a note about this when you try to run, but I didn't see it anywhere when I tried WEBATOMS today. Anyway the fix is to introduce a MS shift vector of (0 0 .25), as in the atoms.inp file I sent you. I think it might be useful if an appropriate shift were introduced by default into the atoms database for very common lattice structures like graphite, or otherwise to detail more precisely the coordinates of the shift that one has to introduce by hand into atoms.inp (which is less desirable). Maybe Bruce Ravel can consider these friendly suggestions in future releases of atoms. I hope you don't mind, but I've forwarded this msg to the ifeffit list. Cheers, John ---------- Forwarded message ---------- Date: Mon, 16 Jan 2006 09:20:39 +0100 From: Antonio Politano <politano(a)fis.unical.it> To: 'John J. Rehr' <jjr(a)leonardo.phys.washington.edu> Subject: R: R: XANES calculations Yes, I understand about stoichiometry. But I don't have understood why using an atoms.inp file taken from the Atoms.inp archive I have six nearest neighbours of the central assorber at 1,42 A. In your feff.inp file under the ATOMS card there are only three nearest neighbours at 1,42 A (this is correct!!!). Thank you very much!!! Antonio Politano

1 0

Re: possible bugs in Artemis
by Bruce Ravel 15 Jan '06

15 Jan '06

On Sunday 15 January 2006 03:22, you wrote: > When I push any of the 'Document' buttons, I get a blank window, a 'clunk' > and a bunch of error messages including a 'fileopen' error, suggesting that > the documentation pages aren't in the right places. Also, what determines > the k-range over which Artemis fits? If I ask for a longer k-range than > what it does by default, nothing seems to happen. Marcus is the second person to report this problem, which exists in the current versions of both Athena and Artemis. The problem exists in the tool that I use to display the document and falls into the category of obvious problems that I failed to test for before the last release. D'oh! The next release will fix this issue. Sadly, I might not have time to make a release in the next two weeks -- we'll see. In any case, the same documentation is available in a number of other places. On a Windows machine, there should be a Start menu entry labeled Ifeffit documentation that will lead you to html versions of the docs. Also, the html versions can be found at http://cars9.uchicago.edu/~ravel/software/docs.html B -- Bruce Ravel ---------------------------------------------- bravel(a)anl.gov Molecular Environmental Science Group, Building 203, Room E-165 MRCAT, Sector 10, Advance Photon Source, Building 433, Room B007 Argonne National Laboratory phone and voice mail: (1) 630 252 5033 Argonne IL 60439, USA fax: (1) 630 252 9793 My homepage: http://cars9.uchicago.edu/~ravel EXAFS software: http://cars9.uchicago.edu/~ravel/software/

1 0

[HOWTO] Ifeffit f1f2() function
by Mauro Rovezzi 09 Jan '06

09 Jan '06

Hi to all, Is it correct to use as energy convolution width (in the f1f2 Ifeffit function) the natural widths of atomic levels tabulated by Krause & Oliver (J. Phys. Chem. Ref. Data, Vol. 8, No. 2, 1979)? My problem is to smooth (arctg-like) Cromer-Liberman f"(E) at the edge region [NOTE: I don't use feff8 because is too slow]. Thanks, Mauro -- Mauro Rovezzi <mauro.rovezzi(a)esrf.fr> PhD student - GILDA BM08 c/o ESRF (Grenoble, FR)

3 2

new versions for the new year!
by Bruce Ravel 07 Jan '06

07 Jan '06

Happy New Year everyone! I have just released Athena 0.8.047, Artemis 0.8.004 and Hephaestus 0.12. You can read all about them at http://cars9.uchicago.edu/iffwiki/HoraeVersion059 New source code tarballs are at SourceForge and at my website. A Windows updater package has been made available and should be offered to the Windows users the next time you fire up one of the codes. Debian users can check Carlo's repository in the next few days -- he is usually quite punctual in making debian packages. The horae_update script has been fixed (I think). Those that want to use it can grab its newest version at http://cars9.uchicago.edu/~ravel/software/packages/horae_update and use it to install the software. As always, let me know about any problems or suggestions. Regards, B -- Bruce Ravel ---------------------------------------------- bravel(a)anl.gov Molecular Environmental Science Group, Building 203, Room E-165 MRCAT, Sector 10, Advanced Photon Source, Building 433, Room B007 Argonne National Laboratory phone and voice mail: (1) 630 252 5033 Argonne IL 60439, USA fax: (1) 630 252 9793 My homepage: http://cars9.uchicago.edu/~ravel EXAFS software: http://cars9.uchicago.edu/~ravel/software/exafs/

4 5