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

Re: [Ifeffit] Problems with EXAFS Analysis software for MAC
by Ravel, Bruce D. 17 Jul '07

17 Jul '07

Ross, The Ifeffit mailing list is a superb resource for all your ifeffit+friends questions. http://cars9.uchicago.edu/mailman/listinfo/ifeffit/ Among the many nice things about the mailing list is that there are a number of people who, unlike me, use the Mac and will know the answer to your question. I have taken the liberty of forwarding this along to the mailing list. You should join the list so that when someone answers, you will get the mail. Good luck, B -----Original Message----- From: Ross Williams [mailto:Ross.Williams@curtin.edu.au] Sent: Mon 7/16/2007 9:47 AM To: Ravel, Bruce D. Subject: Problems with EXAFS Analysis software for MAC Hi I am having problems running ATHENA, ARTEMIS, and HEPHAESTUS, well actually an of the programs in the package. I have a new Intel MacBook with OS X version 10.4.10. I installed the X11 SDK from the OS X dvd, after I install it I could install your package. However when I open on of the programs (by opening them in Applications/Ifeffit) I am prompted to pick a output device, "X11 graphics" or "aquaterm". Either choice the program icon appears briefly in the dock then dissappears, this happens for all the programs. Any advice would be appreciated. Thanks, Ross +++++++++++++++++++++++++ Ross Williams Centre for Materials Research Curtin University of Technology GPO Box U1987 Perth WA 6845 Western Australia ross.williams(a)curtin.edu.au

2 1

Mac intel OSX - Feff6 whereabouts
by Katy Evans 16 Jul '07

16 Jul '07

Hi, Apologies if this question has a very simple answer but I can't work it out. I installed the iXAFS package onto my new Mac (OSX 10.4.8) and almost everything works very well and it is very pleasant to use so thankyou. BUT Feff6 won't run. I can fit to existing Feff calculations but I can't make new ones, from .inp files that used to work on my other computer, or from quick first shell calculations. The message from Artemis starts 'This error is probably due to having Artemis configured incorrectly and so it does not know how to run Feff on your computer...' and goes on to say that I should check the value of the Feff executable in Preferences, and set it to Feff6. So I checked it and it was indeed Feff6. I looked for Feff6 on my computer and could only find a Feff6.atp file in the Perl directory (/Library/Perl/5.8.6/darwin-thread- multi-2level/Xray/atp) - should there be anything else? I tried typing this address into the box for the Feff executable option but this didn't help. I tried to remove everything and reinstall from the disk image but I am not sure if that was successful since I still only got the option to 'upgrade' when I clicked on the installer package. Where are all the things I need to remove if I want to get rid of the old version? Thankyou, Katy Katy Evans Dept. App. Geol. k.evans(a)curtin.edu.au Curtin University Tel: 0061 8 9266 4682 Bentley Fax: 0061 8 9266 3153 GPO Box U 1987, WA6845

3 2

Basic questions on XANES
by Ashley Harvey 14 Jul '07

14 Jul '07

Dear ifeffit users, This posting is with quite basic questions on XANES data processing. I am a somewhat new XANES experimentalist, in a group that does not typically use XANES, so I am lacking some basic knowledge. For normalization of XANES, my impression is that people generally normalize the spectra from ca. 50 eV up to 100 eV or more after the edge onset. Is there a standard acceptable normalization range for K edges? I have noticed that when I change the start of the normalization window by even a few eV, this can make substantial differences in the XANES when comparing two similar spectra (for example, change in peak and pre-edge peak intensities between XANES of one sample at two temperatures). I keep second-guessing my choice of normalization range. Second, I am also looking at the effect of the various ways to set E0. When I start with ifeffit's default (how is this determined?) and then proceed to set E0 to the zero-crossing of 2nd derivative, I'll get value X. When I change it to a set fraction of the edge step (is this legitimate?) I typically get a lower value, and then when I proceed again to set it to the 2nd derivative zero-crossing, I get a value different from the first time it was set to the zero- crossing. For example, the E0 at an Fe K edge: ifeffit default = 7128.9 eV 2nd derivative zero = 7128.8 set fraction = 7125.1 2nd derivative zero = 7125.5 The value given by the 2nd derivative zero-crossing is dependent on the previous E0 setting. I am having a hard time to move on to the actual interpretation of the data while I am still uncertain about such details. Thanks for your patience with some simple questions. Best, Ashley

2 1

xanes pyrite
by s440697＠stud.uni-goettingen.de 10 Jul '07

10 Jul '07

Hello, i have problems with feff-xanes calculations related to pyrite. I try to get the k-edge of sulfur (as absorber) in FeS2. I get the edge at ~2472 eV and i think this is wrong because i get the same energy with gypsum and i think there should be an energyshift related to 2472 eV. My proceeding is as follows: calculate the atomic positions with the asymetric unit from the http://rruff.geo.arizona.edu/AMS/amcsd.php database (Pyrite spacegroup Pa3) respectively http://rruff.geo.arizona.edu/AMS/xtal_data/CIFfiles/00596.cif with "powdercell 2.4" feffrun with the feff.inp-file like in the attachment (thanks to Josh Kas for his feff-hints) I started the feff-run on the one hand with 12 atoms (unitcell) and on the other hand with 22 atoms (14x Fe and 8x S in the cube) After this i plotted from xmu.dat the absorbtion mu (column 4) as a function of the energy (column 1). The result is in the attachment too. I don't know why i get everytime the Sulfur-k-edge at the same position (for pyrite or gypsum) respectively without energyshift related to 2472 eV. many thanks for your help :-) Ciao, Eckhard

1 0

Re: [Ifeffit] Ifeffit Digest, Vol 53, Issue 3
by Emiliano Fonda 04 Jul '07

04 Jul '07

Thanks for the help, I did a mess using the pgplot package from the distro instead using that compiled with the Ifeffit distribution. I removed that of the distro, cleaned up the installation and started again with the pgplot_install script. Everything is fine now. It took just a few minutes. The fact athena was working (I got a graphic window), while the python wrapper not, that puzzled me. Thanks again, Emiliano. > Message: 2 > Date: Tue, 3 Jul 2007 09:43:56 -0500 > From: "Matt Newville" <newville(a)cars.uchicago.edu> > Subject: Re: [Ifeffit] RE : Ifeffit Digest, Vol 53, Issue 1 > To: "XAFS Analysis using Ifeffit" <ifeffit(a)millenia.cars.aps.anl.gov> > Message-ID: > <b8522e3d0707030743q76eb78bdkd7ce7186a31c75b(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Emilano, > > I use the python wrapper for Ifeffit on linux all the time, and also > use python "for several things on the beamline". And just for the > record, I do not use debian packages. >

2 1

Re: [Ifeffit] RE : Ifeffit Digest, Vol 53, Issue 1
by Matt Newville 03 Jul '07

03 Jul '07

Hi Emilano, I use the python wrapper for Ifeffit on linux all the time, and also use python "for several things on the beamline". And just for the record, I do not use debian packages. Over the years, I've experienced many problems using a shared object version of PGPLOT with Ifeffit and its wrappers. These problems are why I wrote PGPLOT_Install, and why I strongly recommend following the instructions for installing Ifeffit, which includes first installing PGPLOT with the PGPLOT_Install script. They are also why I asked you to run 'ldd' on both /usr/local/bin/ifeffit and /usr/lib/python2.5/site-packages/Ifeffit/_ifeffit.so to see what libraries they load dynamically. Is there a problem with doing these steps? If so, try to find someone who can help you follow the build instructions. For 1.2.10, I will make the following changes: a) PGPLOT_Install will be altered to create libpgplot_iff.a instead of libpgplot.a, and this will be installed to /usr/local/share/ifeffit/pgplot. b) The configuration and makefiles will be altered to link against this libpgplot_iff.a, and not with libpgplot that might be installed by some other package. This will avoid the sorts of conflicts you're seeing an also eliminate the possibility of assuming that using the debian/whatever PGPLOT package will work, as it will not work for anything. It will cause some headaches for everyone using the source installations will be forced to do a COMPLETE re-install (including PGPLOT_Install). But, if someone decides to build and support a package for Ifeffit it will then have no chance of conflicting with or depending on any PGPLOT package. Cheers, --Matt

1 0

RE : Ifeffit Digest, Vol 53, Issue 1
by FONDA Emiliano 03 Jul '07

03 Jul '07

Well, I was attracted by the possibility of importing ifeffit in python, since I started using python for several things on beamline. I am not interested in the gifeffit itself, but in the python wrapper. I will test C. Segre packages if they fix the issue. Thanks, Emiliano. > Is there some feature of gifeffit that you cannot live without? > B.

4 4

Re: [Ifeffit] Meaning of sigma^2 and real space resolution in XAFS
by Scott Calvin 02 Jul '07

02 Jul '07

Hi all, This got marked spam and rejected when I sent it from home this weekend... :) At 12:48 AM 6/30/2007, you wrote: >Hello, > >Thanks Bruce and Matt for the previous comments© >I have the following questions and I would appreciate comments about them: > >My Questions are: >1- Can we consider sigma^2 of a single >scattering path to be a measure of Debey Waller factor? If you mean the Debye-Waller factor from x-ray diffraction, the answer is no. The EXAFS sigma^2 is the variance in the absorber scatterer distance, the XRD sigma^2 is the variance in the position of an atom relative to its lattice point in the crystal. Thus, IF the motion of the absorber and scatterer were uncorrelated, it would be reasonable to think that the EXAFS sigma^2 would be twice the XRD Debye-Waller factor. For nearest-neighbors, though, this is a terrible assumption, as the atoms will tend to move in a correlated fashion (put another way, acoustic phonons dominate over optical ones). Thus the EXAFS sigma^2 for nearest-neighbors will usually be much less than the XRD Debye-Waller factor. Further confusing matters is terminology. In EXAFS, sigma^2 is sometimes called the Debye-Waller factor...but this Debye-Waller factor is not the same as that from XRD! I've also seen "Debye-Waller factor" used to include all information about the shape of the distribution of the absorber-scatterer distance, so that sigma^2 is "the harmonic part of the Debye-Waller factor," but that seems to be an older usage. >2- Is sigma^2 a measure of ¥or directly proportional to¤ strain in a bond? Hmm...I'd say no, although I think I know what you're getting at. One major contributor to sigma^2 is thermal vibrations, which of course increase with temperature. I don't think that's generally categorized as "strain" (although I'm wary of the differing definitions that terms such as this can have in different specialties!). Another contributor to sigma^2 is variations in absorber-scatterer distance due to local defects, surface effects, etc., generally lumped together under the term "static disorder." This term itself can be a little misleading, as, e.g., a nanoparticle can have a sigma^2 that varies in a perfectly regular way with distance from the surface--we call that static disorder, even though it is not particularly disorderly. :) At any rate, what material scientists call "strain" can show up as static disorder. But even in that case, note that if all the bonds in a sample were strained, sigma^2 would not reflect it--it's only when some are strained and some are not that it shows up. So yes, I've seen (knowledgeable) people point at a sigma^2 and say "I think that's high because of strain." But that's a kind of short-hand for what's going on. >3- When doing first shell fitting in Artemis, >The actual bond length is: r_eff + dr +- delta ¥dr¤© >Are the error bars associated with dr values >¥delta¥dr¤ of about 0©001 A¤ realistic? ¥i©e© >0©001 A is too small to detect by XAFS¤© Your formatting didn't come through very well, but I'll give it a shot. Ifeffit (and thus Artemis) do a pretty good job of putting a lower bound on delta dr, in my opinion. Why a lower bound? Because there are all sorts of systematic errors that could be coming in, e.g. an iffy model--such as a first-shell only fit for a crystalline material, since there's often a bit of spectral leakage from more distant shells. I'd be very surprised if Artemis ever gave a 0.001 A delta dr, though, and absolutely shocked if it did so on a first-shell only model. Are you saying that it did do that for you? >4- What determines the real space resolution in >XAFS measurements other than K_max? k_min, of course. To answer the gist of your question more fully, though, I have to get on my soapbox. :) "Resolution" is often taken to mean something other than it does. Resolution criteria literally mean the point at which you could be expected to distinguish between two peaks. It is NOT the limit to the precision of information that can be retrieved by a clever person. Huh? Let's take an example of, oh, a proposal that there are two slightly different (but consistent) nearest-neighbor distances in some material. If those distances differ by less than the resolution implied by the k-space range, then they will not show up as two peaks in the Fourier transform. Instead, they'll show up as one broad peak; i.e. a peak with an anomalously large sigma^2. If a multiple-shell fit was performed and splitting was known to be a possibility, this anomalously large sigma^2 could be taken as indirect evidence for the splitting. In fact, if there were some way to estimate sigma2's a priori (I'll grant you that's a big if!), then the broad peak could be modeled as two scattering paths, with the splitting as a free parameter. In that case, EXAFS could give information about splitting to a greater precision than the resolution of the measurement. A lot of the lore about the capabilities of EXAFS suffers from a similar lack of subtlety. Joe Woicik recently gave a very interesting talk at the NSLS Users' Meeting. It is generally bandied about that EXAFS cannot distinguish scatterers that differ in atomic number by less than 5. This is kind of true--in a mindless first-shell fit--because in those cases del_r and sigma^2 will usually just slop up the differences in phase and amplitude due to the different atomic number of the scatterer. But if you really really knew del_r and sigma^2 a priori, even a difference of one atomic number stands out like a sore thumb! The upshot is that if you model, say, zinc scatterers as if they were iron, the fit will probably "work," but you'll be introducing substantial systematic errors into your fitted variables. A corollary is that in the case of a highly-constrained fit, you may be able to do considerably better than the usual +/- 5 rule. The bottom line of this little speech is that the oft-quoted limits of EXAFS analysis are usually referring to a fit in which no a priori information is used. If you know (or suspect) anything about the system and incorporate that into your model, greater precision is sometimes possible. Of course, the results are then only as good as the a priori information; the whole thing could be a house of cards ready to collapse. But in favorable cases, multiple lines of evidence can be used to construct a convincing scenario... Hope that helped! --Scott Calvin Sarah Lawrence College

1 0

gifeffit installation issue on ubuntu feisty fawn
by Emiliano Fonda 02 Jul '07

02 Jul '07

Hi, I would like to use gifeffit on the beamline where I work for fast extraction of EXAFS data during scans and so on. But I have a problem even before starting to code: horae and ifeffit works well, I compiled and installed the python wrapper, but gifeffit refuse to work and I cannot import the Ifeffit module in python. The error message is: fonda@nemotele:~$ gifeffit Traceback (most recent call last): File "/usr/local/bin/gifeffit", line 2, in <module> import GIFeffit, sys File "/usr/lib/python2.5/site-packages/Ifeffit/GIFeffit.py", line 27, in <module> from Ifeffit import Ifeffit File "/usr/lib/python2.5/site-packages/Ifeffit/Ifeffit.py", line 46, in <module> import _ifeffit, types, cmd, os, sys ImportError: /usr/lib/python2.5/site-packages/Ifeffit/_ifeffit.so: undefined symbol: pgclos_ The linux distro is ubuntu feisty fawn and I got the libpgplot5 package installed... ... may anyone help me, please? Thanks, E. Fonda SAMBA beamline SOLEIL synchrotron

3 2

Meaning of sigma^2 and real space resolution in XAFS
by Moneeb Shatnawi 30 Jun '07

30 Jun '07

Hello, Thanks Bruce and Matt for the previous comments� I have the following questions and I would appreciate comments about them: My Questions are: 1- Can we consider sigma^2 of a single scattering path to be a measure of Debey Waller factor? 2- Is sigma^2 a measure of �or directly proportional to� strain in a bond? 3- When doing first shell fitting in Artemis, The actual bond length is: r_eff + dr +- delta �dr�� Are the error bars associated with dr values �delta�dr� of about 0�001 A� realistic? �i�e� 0�001 A is too small to detect by XAFS�� 4- What determines the real space resolution in XAFS measurements other than K_max? Thanks, Moneeb -- Moneeb T� Shatnawi Physics and Astronomy Department 4256 Biomed� Phys� Sciences Building Michigan State University East Lansing, MI 48824 Tel: +1-517-355-9200 ext�2325 E-mail: mtshatnawi@pa�msu�edu

1 0

Re: [Ifeffit] Fwd: scattering amplitude by FEFF and Artemis
by Feng Wang 29 Jun '07

29 Jun '07

Thank you, Dr. Ravel, Could you please just simply tell me the expression for the magnitude of chi (q) (labelled as |chi(q)|)? Thank you. Feng > Feng, > > I am forwarding this to the Ifeffit mailing list since I am in the > middle of an experiment and don't have much time to devote to an > answer. > > > Dear Dr. Ravel, > > > I am now learning to use your Artemis program to calculate the scattering > > amplitude from each paths (shells). It seems your Artemis can give the > > scattering amplitude of each path, as done by EXAFS calculations in FEFF. I > > think the results from both program should be same or comparable, but it > > looks much different, as attached for a result of diamond-K. Is anything > > wrong with my calculations? > > It's really hard to tell. The figure you sent does not convey any > sense of how it was made. Without a clear explanation of what you > did or, better yet, an artemis project file to inspect, I am not sure > how I can possibly answer your question. > > > I have been wondering how big a cluster we should use for FEFF calculations, > > or the contributions of the atoms far from the central atom (e.g. > 1nm) > > since so big clusters (such as 400 atoms and even more) are used for FEFF > > calculations in several recent publications. I hope to get some ideas from > > the scattering amplitude of the paths involved by the atoms far from the > > central atoms. Do you also have any suggestions? > > The nice thing about feff is that it is very easy to use to answer > this sort of question without having to rely on an "expert". What > happens if you run feff with clusters ranging from very small to very > large and compare the chi(k) functions generated for the first few > coordination shells? > > B > > > Feng > > > ==================================== > > EM group, NINT > > 11421 Saskatachewan Drive > > Edmonton, Canada T6G 2M9 > > -- > 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/ ==================================== EM group, NINT 11421 Saskatachewan Drive Edmonton, Canada T6G 2M9

2 1

Fwd: average first shell position and width
by Bruce Ravel 28 Jun '07

28 Jun '07

Moneeb, I'm in the middle of beam run, so I am forwarding this along to the Ifeffit mailing list for commentary. B ---------- Forwarded Message from Moneeb Shatnawi <Moneeb Shatnawi <mtshatnawi(a)pa.msu.edu>> ---------- Subject: average first shell position and width Date: Wednesday 27 June 2007 From: Moneeb Shatnawi <mtshatnawi(a)pa.msu.edu> To: Bruce Ravel <bravel(a)anl.gov> Dear Dr. Ravel, Hello, I am Moneeb Shatnawi from physics department at Michigan State University, I have a PDF and XAFS data on GeSe system, and I would like to check if the PDF and XAFS results are consistent with each other in terms of the first PDF peak position and width. The first PDF peak in this system is a mixed shell of Se-Se bonds as well as Ge-Se bonds. The PDF data gave a width of the first PDF peak of about 0.06 A, and the XAFS data gave sigma^2 for Ge-Se bond is 0.006 A^2, and for Se-Se bond is 0.003 A^2. How is sigma in XAFS results (I was using Artemis program) related to the width of the first PDF peak? Also, when obtaining the XAFS fits to the data, I was using: Theory ---> first shell fit. In this, I was giving r_eff for Se-Se bond to be 2.32 A and that for Ge-Se to be 2.368 A. Through the XAFS refinement, I obtained r, dr as well as r_eff. which of these should be considered as the actual bond length (r or r_eff)? and how are these related to the average position that I get from fitting the first PDF peak in this system? I appreciate your help, Thanks, Moneeb ------------------------------------------------------- -- 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 2

Fwd: scattering amplitude by FEFF and Artemis
by Bruce Ravel 28 Jun '07

28 Jun '07

Feng, I am forwarding this to the Ifeffit mailing list since I am in the middle of an experiment and don't have much time to devote to an answer. > Dear Dr. Ravel, > I am now learning to use your Artemis program to calculate the scattering > amplitude from each paths (shells). It seems your Artemis can give the > scattering amplitude of each path, as done by EXAFS calculations in FEFF. I > think the results from both program should be same or comparable, but it > looks much different, as attached for a result of diamond-K. Is anything > wrong with my calculations? It's really hard to tell. The figure you sent does not convey any sense of how it was made. Without a clear explanation of what you did or, better yet, an artemis project file to inspect, I am not sure how I can possibly answer your question. > I have been wondering how big a cluster we should use for FEFF calculations, > or the contributions of the atoms far from the central atom (e.g. > 1nm) > since so big clusters (such as 400 atoms and even more) are used for FEFF > calculations in several recent publications. I hope to get some ideas from > the scattering amplitude of the paths involved by the atoms far from the > central atoms. Do you also have any suggestions? The nice thing about feff is that it is very easy to use to answer this sort of question without having to rely on an "expert". What happens if you run feff with clusters ranging from very small to very large and compare the chi(k) functions generated for the first few coordination shells? B > Feng > ==================================== > EM group, NINT > 11421 Saskatachewan Drive > Edmonton, Canada T6G 2M9 -- 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/

1 0

XAFS postdoc position at HASYLAB
by Welter, Edmund 27 Jun '07

27 Jun '07

Dear colleagues, at the Hamburger Synchrotron Strahlungslabor (HASYLAB) a postdoc position in the XAFS business is available. If you or one of your colleagues is interested please contact me by e-mail or phone (address at the bottom of this mail). The main task will be the operation of our new XAFS-beamline (beamline C). As a postdoc you will have the opportunity to use HASYLAB's facilities for your own research. Moreover, you will be a live witness of the construction and commissioning of the new high brilliance source PETRA III (user operation at PETRA III will start in 2009) and of the start phase of the XFEL project. If you have questions about this mail or the available position please do not reply to the mailing list, but contact me directly instead. Best regards, Edmund Welter

1 0

weighting multi-data fit
by Jörg Haug 25 Jun '07

25 Jun '07

Dear all, I have a question regarding the weighting for a multiple data set fitting. I found that there is the parameter Epsilon to do this in Artemis. But in the help file there is no description how to use this parameter. Which value did I have to use to set the weighting to (for example) double or half? Best regards Jörg -- Dr. Jörg Haug Martin-Luther-Universität Halle-Wittenberg Institut für Physik Anorganisch-Nichtmetallische Materialien Friedemann-Bach-Platz 6 D-06108 Halle Telefon: 0345 55 25 529 Fax: 0345 55 27 159 e-mail: joerg.haug(a)physik.uni-halle.de http://www.physik.uni-halle.de/Fachgruppen/Glas/arbeitsgruppen/anw.htm

9 11

Re: [Ifeffit] bond distance resolution and correlation of parameters in MS analyses?
by Peter Lay 20 Jun '07

20 Jun '07

Dear All It is unfortunate that the questions that were asked by Mark appeared to be phrased is such a way to get the responses that were obtained rather than discussing the real issues behind the questions, or whether they reflected the information in the Review. As such, I feel compelled to reply to these comments as they are not an accurate reflection of what was detailed in my article in Coordination Chemistry Review. While scientific debate is welcome, as are corrections to errors, I believe that is important that these information sites should not be used to give incorrect information as to the contents of a paper. 1. Nowhere in this Coord Chem Rev article did I state that the SS resolution equation does not apply to paths involving MS contributions, so the question was incorrectly phrased, as were the responses that claim the paper was incorrect in saying this. What I did say was that MS analyses can distinguish metal-ligand bond lengths that differ by less than the resolution imposed by this equation if the MS pathways from the different ligands are sufficiently different (within the inherent Fourier transform resolution) to get around this problem. There are numerous examples in the literature where metal-ligand bond lengths that differ by less than the SS resolution have been distinguished in this manner and have been verified by comparing crystal structure information with those obtained from MS analyses. Here is a direct copy of the relevant section from the paper, so I am uncertain as to how the contributors to the e-mails can come to the conclusion that I stated that the equation does not apply to resolution in MS paths. Clearly, I have stated that it is only when this resolution is sufficiently different in other atoms of the restrained ligands that metal-ligand bond lengths that have differences less than the SS resolution of bond lengths can be distinguished (the article only talked about ligands treated as restrained entities). This limit on the resolution of distances arises because the larger the k range, the greater the separation of the individual oscillations at the end of the k range. While this equation is often quoted, the resolution of the peaks in the FT corresponding to different shells improves as the temperature is lowered due to reduction in the Debye-Waller factors, so it should only be taken as a reasonable guide. Thus the use of as large a k range as possible not only improves the determinacy of the problem, but it also improves the precision and accuracy to which individual metal-ligand bond lengths are determined, and whether individual bond lengths can be resolved. With the typical k ranges used in SS XAFS analysis, M-L bond differencs have to differ by 0.1-0.2 Å for the oscillations in the XAFS to be sufficiently resolved to distinguish between these two bond lengths. By contrast, MS analysis of XAFS data has the ability to distinguish between metal-ligand bond distances that differ by a factor that is less than the ~0.1 Å limit imposed by the SS resolution, provided that the groups to which the ligand donor atoms are attached have quite different MS contributions, which is often the case. The differentiation of M-L bond distances that are less than the resolution obtainable with SS analysis relies on the MS contributions of other atoms within the ligands, since these normally have sufficiently different frequencies of oscillations in the XAFS so that they can be resolved. The MS contributions are most important in the low k range [18] and hence, the most accurate and precise bond length determinations in terms of resolution of different shells (and three-dimensional structural determination) will be obtained when both a large k range and all of the low k range data are used in the fitting procedure. What do the above comments mean in practice? It means that if a complex has ligands all of the same type and angles that involve the M-ligand bond and the ligand are essentially the same, then MS analysis cannot improve over SS on separating bond distances that differ by less than the SS resolution in the FT. However, if ligands of the same type are at different angles with respect to the metal-ligand axes or have different ligands adjacent or opposite to them, or if different ligands are at similar distances, then there is almost certainly a range of MS paths that have half distances that differ by more than the resolution given by the equation and, hence, the individual metal-ligand distances can be distinguished by the use of MS fitting within the constraints of the equation that was given, when they cannot be distinguished by SS fitting. 2. With regard to point 2, yes the equation should have been more accurately described as the number of independent observations rather than the number of independent points in reference to equation 24 in the review. The number of independent observations is a combination of the number of independent points in the EXAFS data plus the number of independent observations obtained from crystallography that are included in the restrained model, as described in the Binsted, Strange and Hasnain article. The equation (or variations of it, as pointed out by the comments below) is, however, appropriate for use in estimating the value of the number of independent observations that are included in restrained MS modeling for fits to EXAFS data. This is not only used in such EXAFS analyses but also extensively, and for a long time, in protein crystallography to increase the degree to which a fit is overdetermined or to prevent an underdetermined fit to the data. As pointed out by Matt, this is often used for relatively rigid ligands, such as imidazoles; it can also be used for flexible ligands where the internal bond lengths vary over a narrow range that is defined by X-ray crystallography, but one of more angle(s) have significant flexibility. For the former case, the whole ligand is moved as an essentially rigid entity, in much the same way as a single atom in the fitting procedure. The essentially fixed (within small ranges) bond angles and bond lengths involving this group lead to the extra term in the equation that is the number of independent observations that are included in the model and, in a restrained model, this increases the value of N/p, even though the value of p does not change (i.e., the positional parameters within the imidazole, for instance, are also fitted but within a very narrow range that is consistent with the variation observed in accurate X-ray crystallography structures). If these bond lengths and angles (and/or Debye-Waller values) were constrained, then the value of p would also decrease making the problem more overdetermined. The Debye-Waller factors can be calculated for atoms in a ring in order to reduce the value of p, but extreme care has to be taken in the use of these values in constrained fits, since they take no account of disorder problems in the crystal or solution and, hence, could result in constrained values that are artificially low and which would lead to problems in the fitting procedure. The answer to the question is that the Stern paper discusses the number of independent points in the EXAFS data and applies to both SS and MS fitting. However, for restrained MS fits, the number of independent observations that should be used in assessing the degree to which the problem is determined in the fitting procedure is that described in the Binsted, Strange and Hasnain paper (or something similar). The latter type of fitting was that described in the Coordination Chemistry Rev article and presumably has been used in the work described by Mark. All the best Peter HI Mark, > Any thoughts and opinions would be greatly appreciated as this relates directly to corrections suggested to be made to my PhD thesis! This is going to re-iterate most of what Bruce said, but since you asked: > 1)Does the equation for bond distance resolution (r = pi/2deltak) only apply to SS? No. It applies to all EXAFS. > I have held the opinion that this can be applied to MS analysis You have been right. > however I have recently been informed that this equation does not correctly describe distance > resolution in MS analyses. The paper in Coord. Chem. Rev. 2005, 249, 141-160 describes this > and is this concordant with the views of the wider EXAFS community? You were mis-informed. This paper is profoundly wrong, and is not concordant with the views of the wider EXAFS community, as defined by the standards and criteria documents at http://www.i-x-s.org/OLD/subcommittee_reports/sc/err-rep.pdf This paper states that the number of independent points in an XAFS data set is: N_i = [ 2*(rmax - rmin) * (kmax -kmin) / pi ] + Sum D*(N-2) + 1 Here rmin,rmax,kmin, and kmax are the spectral ranges. I cannot tell what the sum is over, but D is the "dimension with a restrained part of the model (ie, three for a three-dimensional model)" and N is "the number of independent atoms within the restrained group of the model". The ( Sum D*(N-2) ) term asserts that the number of independent points in the data is dependent on the model. This is complete nonsense. For what it's worth, the standards and criteria report cited above recommends using N_i = [ 2*(rmax - rmin) * (kmax -kmin) / pi ] rounded to the nearest integer. The report is has a bit more to say, but note that it is carefully (and deliberately) silent on "+1", "+2", etc. This is because N_i is an estimate of the maximum number of parameters that can be extracted from a signal. If you're quibbling whether to add 1 or 2 to this number, it probably means you should really subtract 4. Now, one may apply a variety of modeling approaches (tricks?? assumptions??) to the analysis of multiple scattering in highly constrained three-dimensional models that are often associated with organo-metallics. For example, a histidine ring attached to a metal will give multiple scattering, and you can usually assert that the ring is rigid, though you may need to refine its location and orientation relative to the metal. That makes the bond distances and angles (and MS amplitudes) for all the scattering paths from this ring all dependent on a reduced number of variables. It does not add information to the data. Cheers, --Matt _______________________________________________ Ifeffit mailing list Ifeffit(a)millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit X-Account-Key: account2 X-Mozilla-Keys: Return-Path: <ifeffit-bounces(a)millenia.cars.aps.anl.gov> X-Original-To: j.aitken(a)chem.usyd.edu.au Delivered-To: aitken_j(a)chem.usyd.edu.au Received: from localhost (unknown [127.0.0.1]) by localhost.chem.usyd.edu.au (Postfix) with ESMTP id 3F99881B8; Thu, 7 Jun 2007 07:04:39 +1000 (EST) X-Virus-Scanned: amavisd-new at chem.usyd.edu.au Received: from tismis.chem.usyd.edu.au ([127.0.0.1]) by localhost (tismis.chem.usyd.edu.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIIBlvbv0FPG; Thu, 7 Jun 2007 07:04:36 +1000 (EST) Received: from millenia.cars.aps.anl.gov (millenia.cars.aps.anl.gov [164.54.160.111]) by tismis.chem.usyd.edu.au (Postfix) with ESMTP id 1AFAB8187; Thu, 7 Jun 2007 07:04:35 +1000 (EST) Received: from millenia.cars.aps.anl.gov (localhost.localdomain [127.0.0.1]) by millenia.cars.aps.anl.gov (8.13.8/8.13.8) with ESMTP id l56L3Xc7017917; Wed, 6 Jun 2007 16:03:34 -0500 Received: from polyhymnia.mr.aps.anl.gov (polyhymnia.mr.aps.anl.gov [164.54.244.23]) by millenia.cars.aps.anl.gov (8.13.8/8.13.8) with ESMTP id l56L3WHx017914 for <ifeffit(a)millenia.cars.aps.anl.gov>; Wed, 6 Jun 2007 16:03:32 -0500 Received: from localhost (localhost [127.0.0.1]) by polyhymnia.mr.aps.anl.gov (8.13.8/8.13.8/Debian-3) with ESMTP id l56L0im6015827; Wed, 6 Jun 2007 16:00:44 -0500 From: Bruce Ravel <bravel(a)anl.gov> Organization: Molecular Environmental Science Group at Argonne National Lab To: XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> Date: Wed, 6 Jun 2007 16:00:43 -0500 User-Agent: KMail/1.9.6 References: <200706061213.DGT11246(a)auummr1om07.three.com.au> In-Reply-To: <200706061213.DGT11246(a)auummr1om07.three.com.au> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200706061600.43646.bravel(a)anl.gov> Cc: MarkBondin <mibondin(a)three.com.au> Subject: Re: [Ifeffit] bond distance resolution and correlation of parameters in MS analyses? X-BeenThere: ifeffit(a)millenia.cars.aps.anl.gov X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Bruce Ravel <bravel(a)anl.gov>, XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> List-Id: XAFS Analysis using Ifeffit <ifeffit.millenia.cars.aps.anl.gov> List-Unsubscribe: <http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit>, <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=unsubscribe> List-Archive: <http://millenia.cars.aps.anl.gov/pipermail/ifeffit> List-Post: <mailto:ifeffit@millenia.cars.aps.anl.gov> List-Help: <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=help> List-Subscribe: <http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit>, <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ifeffit-bounces(a)millenia.cars.aps.anl.gov Errors-To: ifeffit-bounces(a)millenia.cars.aps.anl.gov On Wednesday 06 June 2007, MarkBondin wrote: > 2) What is the actual equation which defines the determinacy of a fitting > procedure and does this differ between SS and MS analyses? For MS analyses > there has been a recently published equation (Coord. Chem. Rev. 2005, 249, > 141-160) which takes into acount the number of dimensions used in the > analyses and is this only relevant to MS analyses of data? This has also > been expressed in the paper by Binsted (Biochemistry. 1992, 31, > 12117-12125) however a different equation has been detailed by Stern (Phys. > Rev. B. 1993, 48, 9825-9827) which I have been using as a guide in my MS > analyses. Is this acceptable? 1. I don't know what you mean by the word "determinacy". In any case, I thought I made it clear in my last post that, in my opinion, the differences between SS and MS analysis are in the physical interpretation and not in the statistical interpretation. Feff, Ifeffit, and Artemis certainly go to great lengths to downplay the differences between SS and MS paths in the context of the formalism of the theory and analysis, instead emphasizing their differences only in the context of physical interpretation. 2. Argonne's library only has access to the last year of Coord. Chem. Rev. and I don't have time this week to go fetch it from the stacks. So I cannot comment on that paper. 3. The paper by Stern should be read with some care. The argument Ed makes in that paper can only be true in the case of a perfectly packed signal. EXAFS data, although treated as signal processing problem, is never perfectly packed. The Nyquist criterion is an upper bound on the information content, but the actual content of the data is always somewhat less. There are some very fine papers by Rossner and Krappe about using Baysian techniques to find the actual information content of the EXAFS signal. The executive summary is that if think you need Ed's magic "+2", you are probably overusing the information content of your data. Most of us here in this list aren't as careful in practice as all that Baysian stuff. In general, one tries to stay "well below" the Nyquist upper bound. If your fitting parameters make sense physically, if the correlations are not "too high", and if the error bars on your parameters are not "too big", then you are probably not overusing the information content of your data. What is "too high" and "too big"? Well, I am purposefully using squishy language. It is kind of difficult to use Gaussian statistical techniques on EXAFS data, despite the fact that that's exactly what Ifeffit does. The reason is that Gaussin statistics presumes that your measurememt errors are statistical and normally distributed. In practice, exafs analysis is dominated by systematic uncertainties. Things like detector or sample non-linearities and the approximations made by Feff are much bigger sources of error than shot noise for most experiments. Most of those systematic problems are present in your analysis, but I have no idea how you could possibly quantify them. Hence I find myself using squishy language to discuss fit statistics. Read the papers by the frequent contributors to this mailing list. Scott Calvin and Shelly Kelly in particular are careful EXAFS practitioners who work on tough analysis problems and deal well with these issues. Doing what they do may not be as right as possible, but it certainly ain't wrong. HTH, 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/ _______________________________________________ Ifeffit mailing list Ifeffit(a)millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit Return-Path: <ifeffit-bounces(a)millenia.cars.aps.anl.gov> X-Original-To: j.aitken(a)chem.usyd.edu.au Delivered-To: aitken_j(a)chem.usyd.edu.au Received: from localhost (unknown [127.0.0.1]) by localhost.chem.usyd.edu.au (Postfix) with ESMTP id A3DA68195; Wed, 6 Jun 2007 22:51:48 +1000 (EST) X-Virus-Scanned: amavisd-new at chem.usyd.edu.au Received: from tismis.chem.usyd.edu.au ([127.0.0.1]) by localhost (tismis.chem.usyd.edu.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jldjzjMckVWz; Wed, 6 Jun 2007 22:51:47 +1000 (EST) Received: from millenia.cars.aps.anl.gov (millenia.cars.aps.anl.gov [164.54.160.111]) by tismis.chem.usyd.edu.au (Postfix) with ESMTP id 75D278160; Wed, 6 Jun 2007 22:51:47 +1000 (EST) Received: from millenia.cars.aps.anl.gov (localhost.localdomain [127.0.0.1]) by millenia.cars.aps.anl.gov (8.13.8/8.13.8) with ESMTP id l56CnoPv011737; Wed, 6 Jun 2007 07:49:51 -0500 Received: from polyhymnia.mr.aps.anl.gov (polyhymnia.mr.aps.anl.gov [164.54.244.23]) by millenia.cars.aps.anl.gov (8.13.8/8.13.8) with ESMTP id l56CnmLn011734 for <ifeffit(a)millenia.cars.aps.anl.gov>; Wed, 6 Jun 2007 07:49:48 -0500 Received: from localhost (localhost [127.0.0.1]) by polyhymnia.mr.aps.anl.gov (8.13.8/8.13.8/Debian-3) with ESMTP id l56Cl1cT014080; Wed, 6 Jun 2007 07:47:01 -0500 From: Bruce Ravel <bravel(a)anl.gov> Organization: Molecular Environmental Science Group at Argonne National Lab To: ifeffit(a)millenia.cars.aps.anl.gov Date: Wed, 6 Jun 2007 07:47:01 -0500 User-Agent: KMail/1.9.6 References: <200706061213.DGT11246(a)auummr1om07.three.com.au> In-Reply-To: <200706061213.DGT11246(a)auummr1om07.three.com.au> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200706060747.01272.bravel(a)anl.gov> Cc: MarkBondin <mibondin(a)three.com.au> Subject: Re: [Ifeffit] bond distance resolution and correlation of parameters in MS analyses? X-BeenThere: ifeffit(a)millenia.cars.aps.anl.gov X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Bruce Ravel <bravel(a)anl.gov>, XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> List-Id: XAFS Analysis using Ifeffit <ifeffit.millenia.cars.aps.anl.gov> List-Unsubscribe: <http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit>, <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=unsubscribe> List-Archive: <http://millenia.cars.aps.anl.gov/pipermail/ifeffit> List-Post: <mailto:ifeffit@millenia.cars.aps.anl.gov> List-Help: <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=help> List-Subscribe: <http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit>, <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=subscribe> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 8bit Sender: ifeffit-bounces(a)millenia.cars.aps.anl.gov Errors-To: ifeffit-bounces(a)millenia.cars.aps.anl.gov On Wednesday 06 June 2007, MarkBondin wrote: >1)Does the equation for bond distance resolution (r = pi/2deltak) only >apply to SS? I have held the opinion that this can be applied to MS >analysis however I have recently been informed that this equation does not >correctly describe distance resolution in MS analyses. The paper in Coord. >Chem. Rev. 2005, 249, 141-160 describes this and is this concordant with >the views of the wider EXAFS community? > > >Mark, > >Strictly speaking, that equation doesn't have anything to do with >EXAFS. That is the equation that tells you what your Fourier >component resolution is in a general Fourier analysis problem. It >just so happens that, in the case of single scattering EXAFS analysis, >that equation is easily interpreted in terms of photoelectron >wavenumber k and SS path length r. > >The equation is neither different nor incorrect for MS analysis. >That's true becuase MS analysis isn't any different from SS analysis. >In either case, you do a Fourier transform. In either case, you >attempt to model Fourier components using the contributions from some >number of scattering geometries as computed by theory. In either >case, you are asking yourself if you can actually resolve small >differences in phase of the various things that contribute to the fit. > >The only difference lies in how you *interpret* the physical meaning >of the Fourier components. And even then, things aren't so very >different. In the case of SS analysis, you assert that the R axis is >a measure of "bond length" while for MS analysis the R axis is a >measure of "half path length" -- acknowledging, of course, that there >is a phase shift in the EXAFS equation such that the R axis actually >measures something a bit shorter than the bond or half path length. > >Off the top of my head, I don't recall the paper you cite and I most >certainly cannot speak for the "wider EXAFS community". Speaking for >myself, the physical interpretation of the equation for Fourier >component resolution may change when you consider MS paths, but to >claim that a property of the Fourier transform somehow becomes invalid >when you change the details of the fitting model is just silly. > >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/ > >_______________________________________________ >Ifeffit mailing list >Ifeffit(a)millenia.cars.aps.anl.gov >http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit > > > >Return-Path: <ifeffit-bounces(a)millenia.cars.aps.anl.gov> >X-Original-To: j.aitken(a)chem.usyd.edu.au >Delivered-To: aitken_j(a)chem.usyd.edu.au >Received: from localhost (unknown [127.0.0.1]) > by localhost.chem.usyd.edu.au (Postfix) with ESMTP id B52C68192; > Wed, 6 Jun 2007 22:34:01 +1000 (EST) >X-Virus-Scanned: amavisd-new at chem.usyd.edu.au >Received: from tismis.chem.usyd.edu.au ([127.0.0.1]) > by localhost (tismis.chem.usyd.edu.au [127.0.0.1]) (amavisd-new, > port 10024) > with ESMTP id Bt1hFrBPzdYS; Wed, 6 Jun 2007 22:34:01 +1000 (EST) >Received: from millenia.cars.aps.anl.gov (millenia.cars.aps.anl.gov >[164.54.160.111]) > by tismis.chem.usyd.edu.au (Postfix) with ESMTP id 8255C8160; > Wed, 6 Jun 2007 22:34:00 +1000 (EST) >Received: from millenia.cars.aps.anl.gov (localhost.localdomain [127.0.0.1]) > by millenia.cars.aps.anl.gov (8.13.8/8.13.8) with ESMTP id > l56CVHTh011592; > Wed, 6 Jun 2007 07:31:35 -0500 >Received: from petasus.aps.anl.gov (petasus.aps.anl.gov [164.54.146.72]) > by millenia.cars.aps.anl.gov (8.13.8/8.13.8) with ESMTP id > l56CDQCl011430 > for <ifeffit(a)millenia.cars.aps.anl.gov>; Wed, 6 Jun 2007 07:13:26 > -0500 >Received: from herald.aps.anl.gov (herald.aps.anl.gov [164.54.50.61]) > by petasus.aps.anl.gov (8.13.7/8.13.7) with ESMTP id l56CDPH7020467 > for <ifeffit(a)millenia.cars.aps.anl.gov>; > Wed, 6 Jun 2007 07:13:25 -0500 (CDT) >Received: from iota.aps.anl.gov (iota.aps.anl.gov [164.54.56.65]) > by herald.aps.anl.gov (8.13.7/8.13.7) with ESMTP id l56CDDTr015527 > for <ifeffit(a)millenia.cars.aps.anl.gov>; > Wed, 6 Jun 2007 07:13:13 -0500 (CDT) >Received: from auummr1om07.three.com.au (smtpout3.three.com.au >[202.124.68.59]) > by iota.aps.anl.gov with ESMTP id l56CDBRl028957 > for <ifeffit(a)millenia.cars.aps.anl.gov>; > Wed, 6 Jun 2007 07:13:12 -0500 (CDT) >Received: from auumgu1pr04.three.com.au (auummr1vp02.three.com.au > [10.176.58.185]) by auummr1om07.three.com.au (MOS 3.5.5-GR) > with ESMTP id DGT11246; Wed, 6 Jun 2007 22:13:03 +1000 (EST) >Message-Id: <200706061213.DGT11246(a)auummr1om07.three.com.au> >Content-Disposition: inline >MIME-Version: 1.0 >X-Mailer: Perl5 Mail::Internet v1.40 >From: MarkBondin <mibondin(a)three.com.au> >To: "ifeffit(a)millenia.cars.aps.anl.gov" <ifeffit(a)millenia.cars.aps.anl.gov> >Date: Wed, 06 Jun 2007 22:13:03 +1000 (EST) >X-Priority: 3 (Normal) >X-MIME-Autoconverted: from quoted-printable to 8bit by > millenia.cars.aps.anl.gov id l56CDQCl011430 >X-Mailman-Approved-At: Wed, 06 Jun 2007 07:31:16 -0500 >Subject: [Ifeffit] bond distance resolution and correlation of parameters > in MS analyses? >X-BeenThere: ifeffit(a)millenia.cars.aps.anl.gov >X-Mailman-Version: 2.1.9 >Precedence: list >Reply-To: XAFS Analysis using Ifeffit <ifeffit(a)millenia.cars.aps.anl.gov> >List-Id: XAFS Analysis using Ifeffit <ifeffit.millenia.cars.aps.anl.gov> >List-Unsubscribe: ><http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit>, > ><mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=unsubscribe> >List-Archive: <http://millenia.cars.aps.anl.gov/pipermail/ifeffit> >List-Post: <mailto:ifeffit@millenia.cars.aps.anl.gov> >List-Help: <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=help> >List-Subscribe: <http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit>, > <mailto:ifeffit-request@millenia.cars.aps.anl.gov?subject=subscribe> >Content-Type: text/plain; charset=us-ascii; format=flowed >Content-Transfer-Encoding: 8bit >Sender: ifeffit-bounces(a)millenia.cars.aps.anl.gov >Errors-To: ifeffit-bounces(a)millenia.cars.aps.anl.gov > >Hi, I would like general opinions of some EXAFS practioners in regards to >the most widely accepted methods for bond distance resolution and >correlation of parameters in both single scattering (SS) and multiple >scattering (MS) EXAFS refinements and if these can be said to differ? > >1)Does the equation for bond distance resolution (r = pi/2deltak) only >apply to SS? I have held the opinion that this can be applied to MS >analysis however I have recently been informed that this equation does not >correctly describe distance resolution in MS analyses. The paper in Coord. >Chem. Rev. 2005, 249, 141-160 describes this and is this concordant with >the views of the wider EXAFS community? > >2) What is the actual equation which defines the determinacy of a fitting >procedure and does this differ between SS and MS analyses? For MS analyses >there has been a recently published equation (Coord. Chem. Rev. 2005, 249, >141-160) which takes into acount the number of dimensions used in the >analyses and is this only relevant to MS analyses of data? This has also >been expressed in the paper by Binsted (Biochemistry. 1992, 31, >12117-12125) however a different equation has been detailed by Stern >(Phys. Rev. B. 1993, 48, 9825-9827) which I have been using as a guide in >my MS analyses. Is this acceptable? > >Any thoughts and opinions would be greatly appreciated as this relates >directly to corrections suggested to be made to my PhD thesis! > >Many thanks, > >Mark > >_ Professor Peter A. Lay FAA ARC Australian Professorial Fellow and Personal Chair in Inorganic Chemistry Centre for Heavy Metals Research School of Chemistry The University of Sydney NSW 2006 Australia Tel: +61-2-9351 4269 Fax: +61-2-9351 3329

2 1

Re: [Ifeffit] Ifeffit Digest, Vol 52, Issue 7
by hebhop＠u.washington.edu 19 Jun '07

19 Jun '07

Hi Eckhard, you need to add the following two cards to your feff.inp files: * Self consistent potentials. This can be important for XANES calculatoins. SCF rscf 0 * Full multiple scattering (sums all paths within rfms). This is essential for * most XANES calculations. FMS rfms 0 calculations should be converged w.r.t. rscf and rfms, but for your files, you can just include the whole cluster of atoms. Also, I ran both files and the first one (gypsum) complains that atoms are very close together. FEFF does not crash, but I would check your structure to be sure that it is correct. Cheers, Josh Kas > Hallo @all, > > (first at all, sorry for my bad english) > > i'm a student working on my diploma thesis (nexafs/xanes) and my job is to > simulate with FEFF 8.4 spectra, for example absorption as a function of > energy (mu_(E)). I'm a newbie in this topic and i tried to get the k-edge > of Sulfur for the substance gypsum (CaSO4 * 2(H2O)) and pyrite (FeS2). I'm > interested in the XANES-range of the spectra not the EXAFS. I get > everytime my peaks at ~2472 eV for Sulfur as absorber whatever substance i > use (gypsum, pyrite,...). There are no differences with the peak position > on the energy-scale or shifts. I'm really confused :-( I think, there > should be differences in the spectra... I send you two feff.inp files from > my feff-runs. My source is the mineralogy database > (http://rruff.geo.arizona.edu/AMS/amcsd.php) where i get the data for the > unitcell. Then i put the data in the XtalDraw program to get the positions > of the Atoms in Angstrom, by the way i get i nice 3D-View of the unitcell > :-). Then i put the values of the positions into feff... > I simulated pyrite with 12 atoms and gypsum with 48. > I'm appreciative for every help :-) > > ciao, > Eckhard > > > --------------------------------- > Eckhard Bosman > e.bosman(a)stud.uni-goettingen.de > +49 (0)551-39-14441 > Raum: E0.104 > Institut f?r R?ntgenphysik > Friedrich-Hund-Platz 1 > 37077 G?ttingen > Germany

2 1

Re: [Ifeffit] Ifeffit Digest, Vol 52, Issue 9
by Michel Jaouen 18 Jun '07

18 Jun '07

Dear lena, >I have a question regarding the convergence of XANES calculations. I'm >currently focusing on the O-K edge of perovskite oxides, in particular >SrTiO3 and found that there are still fine-structure changes for large >(9.5?) clusters. Attached is my *.inp file for the 9.5? cluster and a >summary of the XANES for increasing cluster sizes from 6.5? to 9.5?. You >can see that there are still significant changes as the cluster size is >increased from 8.5 to 9.5?. In particular, I find a double peak feature >in the first 5eV after the edge onset, which is not observed >experimentally. It is a normal behavior: when increasing the cluster's size, you are adding more MS paths and then it appears coresponding peaks. It is a general trend for xanes:the measured signal is a probe up to a given distance for MS, a distance you didn't know a priori. Thus the game is to start from a rather small cluster, compute the xanes, compare to the experiment. If some features are missing, increase the size and so on till you obtain (if lucky) all experimental fine structures. On the opposite, as soon as it appears fine structures which don't exist in the experiment reduce the size. > Do you have any suggestions how to obtain a better >convergence? > >Secondly, if you compare the simulated XANES with experimental results >(see attachment: EELS STO.png), I'm not able to match all three main >peaks, even by scaling the energy scale. Are the deviations I'm seeing >within the accuracy of FEFF or do I need to improve my *.inp file? I have been working a lot on STO and have many exchange about this material with John Rehr. In fact you can obtain a quite good match with the experiment (peaks' positions) if you reduce the lattice parameter by 5% (RMULTIPLIER=0.95, see the attached figure). Of course such a reduction is unphysical but from John's own words :"Also regarding SrTiO3, I'm now thinking that the self-energy might be responsible for the need to use an RMULT 0.95." So either you the Rmultiplier trick or you try the feff8.5 version that includes some improvements to the self-energy (using low-loss and the sum rules for normalization). In any case, feff has to much intensity at the edge onset (sigma*) for light elements like Oxygen. Two other comments: why adding a real part vr=1.4eV? I don't find this necessary here from my numerous calculations (it is responsible for the hump at the bottom of the pi* which doesn't exist in the experiment: a positive vr induces a red-shift for the spectrum, look at the ldos). I suggest also not to use the default for lmax (-1), but instead lmax=2 for all atoms (spd basis). You can also try to go up to lmax=3 (spdf basis) because Sr is quite heavy and it can help in some case (for pure Ni for instance, to reproduce the K edge, you must go up to f states). I hope it can help you. Best regards, Michel -- __________________________________________ Michel Jaouen Universite de Poitiers - UFR Sciences - SP2MI LMP UMR 6630-CNRS Boulevard Pierre et Marie Curie - Teleport 2 BP 30179 86962 Futuroscope - Chasseneuil Cedex France Tel : (33) 5 49 49 67 37 Fax : (33) 5 49 49 66 92 e-mail : Michel.Jaouen(a)univ-poitiers.fr __________________________________________

2 1

Re: [Ifeffit] convergence of XANES for STO
by Feng Wang 18 Jun '07

18 Jun '07

Hi Lena, It is no suprising to see the change of the fine structure near the edge within a cluster of that size, because of the long mean free path of the photoelectron. You used a broadening of 0.2eV in your FEFF input, which should give you more details than your experiments. Good luck, Feng > Dear all, > > I have a question regarding the convergence of XANES calculations. I'm > currently focusing on the O-K edge of perovskite oxides, in particular > SrTiO3 and found that there are still fine-structure changes for large > (9.5Å) clusters. Attached is my *.inp file for the 9.5Å cluster and a > summary of the XANES for increasing cluster sizes from 6.5Å to 9.5Å. You > can see that there are still significant changes as the cluster size is > increased from 8.5 to 9.5Å. In particular, I find a double peak feature > in the first 5eV after the edge onset, which is not observed > experimentally. Do you have any suggestions how to obtain a better > convergence? > > Secondly, if you compare the simulated XANES with experimental results > (see attachment: EELS STO.png), I'm not able to match all three main > peaks, even by scaling the energy scale. Are the deviations I'm seeing > within the accuracy of FEFF or do I need to improve my *.inp file? > > Best regards, > Lena > > --------------------------------- > Lena Fitting Kourkoutis > E13 Clark Hall > Cornell University > Applied and Engineering Physics > Ithaca, NY 14853 > > phone: 607-255-0654 > e-mail: lf56(a)cornell.edu > --------------------------------- ==================================== EM group, NINT 11421 Saskatachewan Drive Edmonton, Canada T6G 2M9

3 2

convergence of XANES for STO
by Lena Fitting 18 Jun '07

18 Jun '07

Dear all, I have a question regarding the convergence of XANES calculations. I'm currently focusing on the O-K edge of perovskite oxides, in particular SrTiO3 and found that there are still fine-structure changes for large (9.5Å) clusters. Attached is my *.inp file for the 9.5Å cluster and a summary of the XANES for increasing cluster sizes from 6.5Å to 9.5Å. You can see that there are still significant changes as the cluster size is increased from 8.5 to 9.5Å. In particular, I find a double peak feature in the first 5eV after the edge onset, which is not observed experimentally. Do you have any suggestions how to obtain a better convergence? Secondly, if you compare the simulated XANES with experimental results (see attachment: EELS STO.png), I'm not able to match all three main peaks, even by scaling the energy scale. Are the deviations I'm seeing within the accuracy of FEFF or do I need to improve my *.inp file? Best regards, Lena --------------------------------- Lena Fitting Kourkoutis E13 Clark Hall Cornell University Applied and Engineering Physics Ithaca, NY 14853 phone: 607-255-0654 e-mail: lf56(a)cornell.edu --------------------------------- TITLE SrTiO3 with core hole HOLE 1 1.0 * pot xsph fms paths genfmt ff2chi CONTROL 1 1 1 1 1 1 PRINT 1 0 0 0 0 0 * ixc [ Vr Vi ] EXCHANGE 0 1.4 0.2 * r_scf [ l_scf n_scf ca ] SCF 5.0 0 30 * kmax [ delta_k delta_e ] XANES 4.0 .01 .17 * r_fms l_fms FMS 9.15804 0 * emin emax eimag LDOS -30 20 0.2 RPATH 0.1 POTENTIALS * ipot Z element l_scmt l_fms stoichiometry 0 8 O -1 -1 0.001 1 38 Sr -1 -1 1 2 22 Ti -1 -1 1 3 8 O -1 -1 3 ATOMS * this list contains 285 atoms * x y z ipot tag distance 0.00000 0.00000 0.00000 0 O1 0.00000 0 0.00000 0.00000 1.95250 2 Ti1 1.95250 1 0.00000 0.00000 -1.95250 2 Ti1 1.95250 2 1.95250 0.00000 1.95250 3 O1 2.76125 3 -1.95250 0.00000 1.95250 3 O1 2.76125 4 0.00000 1.95250 1.95250 3 O1 2.76125 5 0.00000 -1.95250 1.95250 3 O1 2.76125 6 1.95250 0.00000 -1.95250 3 O1 2.76125 7 -1.95250 0.00000 -1.95250 3 O1 2.76125 8 0.00000 1.95250 -1.95250 3 O1 2.76125 9 0.00000 -1.95250 -1.95250 3 O1 2.76125 10 1.95250 1.95250 0.00000 1 Sr1 2.76125 11 -1.95250 1.95250 0.00000 1 Sr1 2.76125 12 1.95250 -1.95250 0.00000 1 Sr1 2.76125 13 -1.95250 -1.95250 0.00000 1 Sr1 2.76125 14 3.90500 0.00000 0.00000 3 O1 3.90500 15 -3.90500 0.00000 0.00000 3 O1 3.90500 16 0.00000 3.90500 0.00000 3 O1 3.90500 17 0.00000 -3.90500 0.00000 3 O1 3.90500 18 0.00000 0.00000 3.90500 3 O1 3.90500 19 0.00000 0.00000 -3.90500 3 O1 3.90500 20 3.90500 0.00000 1.95250 2 Ti1 4.36592 21 -3.90500 0.00000 1.95250 2 Ti1 4.36592 22 0.00000 3.90500 1.95250 2 Ti1 4.36592 23 0.00000 -3.90500 1.95250 2 Ti1 4.36592 24 3.90500 0.00000 -1.95250 2 Ti1 4.36592 25 -3.90500 0.00000 -1.95250 2 Ti1 4.36592 26 0.00000 3.90500 -1.95250 2 Ti1 4.36592 27 0.00000 -3.90500 -1.95250 2 Ti1 4.36592 28 3.90500 1.95250 1.95250 3 O1 4.78263 29 -3.90500 1.95250 1.95250 3 O1 4.78263 30 1.95250 3.90500 1.95250 3 O1 4.78263 31 -1.95250 3.90500 1.95250 3 O1 4.78263 32 3.90500 -1.95250 1.95250 3 O1 4.78263 33 -3.90500 -1.95250 1.95250 3 O1 4.78263 34 1.95250 -3.90500 1.95250 3 O1 4.78263 35 -1.95250 -3.90500 1.95250 3 O1 4.78263 36 3.90500 1.95250 -1.95250 3 O1 4.78263 37 -3.90500 1.95250 -1.95250 3 O1 4.78263 38 1.95250 3.90500 -1.95250 3 O1 4.78263 39 -1.95250 3.90500 -1.95250 3 O1 4.78263 40 3.90500 -1.95250 -1.95250 3 O1 4.78263 41 -3.90500 -1.95250 -1.95250 3 O1 4.78263 42 1.95250 -3.90500 -1.95250 3 O1 4.78263 43 -1.95250 -3.90500 -1.95250 3 O1 4.78263 44 1.95250 1.95250 3.90500 1 Sr1 4.78263 45 -1.95250 1.95250 3.90500 1 Sr1 4.78263 46 1.95250 -1.95250 3.90500 1 Sr1 4.78263 47 -1.95250 -1.95250 3.90500 1 Sr1 4.78263 48 1.95250 1.95250 -3.90500 1 Sr1 4.78263 49 -1.95250 1.95250 -3.90500 1 Sr1 4.78263 50 1.95250 -1.95250 -3.90500 1 Sr1 4.78263 51 -1.95250 -1.95250 -3.90500 1 Sr1 4.78263 52 3.90500 3.90500 0.00000 3 O1 5.52250 53 -3.90500 3.90500 0.00000 3 O1 5.52250 54 3.90500 -3.90500 0.00000 3 O1 5.52250 55 -3.90500 -3.90500 0.00000 3 O1 5.52250 56 3.90500 0.00000 3.90500 3 O1 5.52250 57 -3.90500 0.00000 3.90500 3 O1 5.52250 58 0.00000 3.90500 3.90500 3 O1 5.52250 59 0.00000 -3.90500 3.90500 3 O1 5.52250 60 3.90500 0.00000 -3.90500 3 O1 5.52250 61 -3.90500 0.00000 -3.90500 3 O1 5.52250 62 0.00000 3.90500 -3.90500 3 O1 5.52250 63 0.00000 -3.90500 -3.90500 3 O1 5.52250 64 3.90500 3.90500 1.95250 2 Ti1 5.85750 65 -3.90500 3.90500 1.95250 2 Ti1 5.85750 66 3.90500 -3.90500 1.95250 2 Ti1 5.85750 67 -3.90500 -3.90500 1.95250 2 Ti1 5.85750 68 0.00000 0.00000 5.85750 2 Ti1 5.85750 69 3.90500 3.90500 -1.95250 2 Ti1 5.85750 70 -3.90500 3.90500 -1.95250 2 Ti1 5.85750 71 3.90500 -3.90500 -1.95250 2 Ti1 5.85750 72 -3.90500 -3.90500 -1.95250 2 Ti1 5.85750 73 0.00000 0.00000 -5.85750 2 Ti1 5.85750 74 5.85750 0.00000 1.95250 3 O1 6.17435 75 -5.85750 0.00000 1.95250 3 O1 6.17435 76 0.00000 5.85750 1.95250 3 O1 6.17435 77 0.00000 -5.85750 1.95250 3 O1 6.17435 78 1.95250 0.00000 5.85750 3 O1 6.17435 79 -1.95250 0.00000 5.85750 3 O1 6.17435 80 0.00000 1.95250 5.85750 3 O1 6.17435 81 0.00000 -1.95250 5.85750 3 O1 6.17435 82 5.85750 0.00000 -1.95250 3 O1 6.17435 83 -5.85750 0.00000 -1.95250 3 O1 6.17435 84 0.00000 5.85750 -1.95250 3 O1 6.17435 85 0.00000 -5.85750 -1.95250 3 O1 6.17435 86 1.95250 0.00000 -5.85750 3 O1 6.17435 87 -1.95250 0.00000 -5.85750 3 O1 6.17435 88 0.00000 1.95250 -5.85750 3 O1 6.17435 89 0.00000 -1.95250 -5.85750 3 O1 6.17435 90 5.85750 1.95250 0.00000 1 Sr1 6.17435 91 -5.85750 1.95250 0.00000 1 Sr1 6.17435 92 1.95250 5.85750 0.00000 1 Sr1 6.17435 93 -1.95250 5.85750 0.00000 1 Sr1 6.17435 94 5.85750 -1.95250 0.00000 1 Sr1 6.17435 95 -5.85750 -1.95250 0.00000 1 Sr1 6.17435 96 1.95250 -5.85750 0.00000 1 Sr1 6.17435 97 -1.95250 -5.85750 0.00000 1 Sr1 6.17435 98 3.90500 3.90500 3.90500 3 O1 6.76366 99 -3.90500 3.90500 3.90500 3 O1 6.76366 100 3.90500 -3.90500 3.90500 3 O1 6.76366 101 -3.90500 -3.90500 3.90500 3 O1 6.76366 102 3.90500 3.90500 -3.90500 3 O1 6.76366 103 -3.90500 3.90500 -3.90500 3 O1 6.76366 104 3.90500 -3.90500 -3.90500 3 O1 6.76366 105 -3.90500 -3.90500 -3.90500 3 O1 6.76366 106 3.90500 0.00000 5.85750 2 Ti1 7.03984 107 -3.90500 0.00000 5.85750 2 Ti1 7.03984 108 0.00000 3.90500 5.85750 2 Ti1 7.03984 109 0.00000 -3.90500 5.85750 2 Ti1 7.03984 110 3.90500 0.00000 -5.85750 2 Ti1 7.03984 111 -3.90500 0.00000 -5.85750 2 Ti1 7.03984 112 0.00000 3.90500 -5.85750 2 Ti1 7.03984 113 0.00000 -3.90500 -5.85750 2 Ti1 7.03984 114 5.85750 3.90500 1.95250 3 O1 7.30559 115 -5.85750 3.90500 1.95250 3 O1 7.30559 116 3.90500 5.85750 1.95250 3 O1 7.30559 117 -3.90500 5.85750 1.95250 3 O1 7.30559 118 5.85750 -3.90500 1.95250 3 O1 7.30559 119 -5.85750 -3.90500 1.95250 3 O1 7.30559 120 3.90500 -5.85750 1.95250 3 O1 7.30559 121 -3.90500 -5.85750 1.95250 3 O1 7.30559 122 3.90500 1.95250 5.85750 3 O1 7.30559 123 -3.90500 1.95250 5.85750 3 O1 7.30559 124 1.95250 3.90500 5.85750 3 O1 7.30559 125 -1.95250 3.90500 5.85750 3 O1 7.30559 126 3.90500 -1.95250 5.85750 3 O1 7.30559 127 -3.90500 -1.95250 5.85750 3 O1 7.30559 128 1.95250 -3.90500 5.85750 3 O1 7.30559 129 -1.95250 -3.90500 5.85750 3 O1 7.30559 130 5.85750 3.90500 -1.95250 3 O1 7.30559 131 -5.85750 3.90500 -1.95250 3 O1 7.30559 132 3.90500 5.85750 -1.95250 3 O1 7.30559 133 -3.90500 5.85750 -1.95250 3 O1 7.30559 134 5.85750 -3.90500 -1.95250 3 O1 7.30559 135 -5.85750 -3.90500 -1.95250 3 O1 7.30559 136 3.90500 -5.85750 -1.95250 3 O1 7.30559 137 -3.90500 -5.85750 -1.95250 3 O1 7.30559 138 3.90500 1.95250 -5.85750 3 O1 7.30559 139 -3.90500 1.95250 -5.85750 3 O1 7.30559 140 1.95250 3.90500 -5.85750 3 O1 7.30559 141 -1.95250 3.90500 -5.85750 3 O1 7.30559 142 3.90500 -1.95250 -5.85750 3 O1 7.30559 143 -3.90500 -1.95250 -5.85750 3 O1 7.30559 144 1.95250 -3.90500 -5.85750 3 O1 7.30559 145 -1.95250 -3.90500 -5.85750 3 O1 7.30559 146 5.85750 1.95250 3.90500 1 Sr1 7.30559 147 -5.85750 1.95250 3.90500 1 Sr1 7.30559 148 1.95250 5.85750 3.90500 1 Sr1 7.30559 149 -1.95250 5.85750 3.90500 1 Sr1 7.30559 150 5.85750 -1.95250 3.90500 1 Sr1 7.30559 151 -5.85750 -1.95250 3.90500 1 Sr1 7.30559 152 1.95250 -5.85750 3.90500 1 Sr1 7.30559 153 -1.95250 -5.85750 3.90500 1 Sr1 7.30559 154 5.85750 1.95250 -3.90500 1 Sr1 7.30559 155 -5.85750 1.95250 -3.90500 1 Sr1 7.30559 156 1.95250 5.85750 -3.90500 1 Sr1 7.30559 157 -1.95250 5.85750 -3.90500 1 Sr1 7.30559 158 5.85750 -1.95250 -3.90500 1 Sr1 7.30559 159 -5.85750 -1.95250 -3.90500 1 Sr1 7.30559 160 1.95250 -5.85750 -3.90500 1 Sr1 7.30559 161 -1.95250 -5.85750 -3.90500 1 Sr1 7.30559 162 7.81000 0.00000 0.00000 3 O1 7.81000 163 -7.81000 0.00000 0.00000 3 O1 7.81000 164 0.00000 7.81000 0.00000 3 O1 7.81000 165 0.00000 -7.81000 0.00000 3 O1 7.81000 166 0.00000 0.00000 7.81000 3 O1 7.81000 167 0.00000 0.00000 -7.81000 3 O1 7.81000 168 7.81000 0.00000 1.95250 2 Ti1 8.05036 169 -7.81000 0.00000 1.95250 2 Ti1 8.05036 170 0.00000 7.81000 1.95250 2 Ti1 8.05036 171 0.00000 -7.81000 1.95250 2 Ti1 8.05036 172 3.90500 3.90500 5.85750 2 Ti1 8.05036 173 -3.90500 3.90500 5.85750 2 Ti1 8.05036 174 3.90500 -3.90500 5.85750 2 Ti1 8.05036 175 -3.90500 -3.90500 5.85750 2 Ti1 8.05036 176 7.81000 0.00000 -1.95250 2 Ti1 8.05036 177 -7.81000 0.00000 -1.95250 2 Ti1 8.05036 178 0.00000 7.81000 -1.95250 2 Ti1 8.05036 179 0.00000 -7.81000 -1.95250 2 Ti1 8.05036 180 3.90500 3.90500 -5.85750 2 Ti1 8.05036 181 -3.90500 3.90500 -5.85750 2 Ti1 8.05036 182 3.90500 -3.90500 -5.85750 2 Ti1 8.05036 183 -3.90500 -3.90500 -5.85750 2 Ti1 8.05036 184 7.81000 1.95250 1.95250 3 O1 8.28376 185 -7.81000 1.95250 1.95250 3 O1 8.28376 186 1.95250 7.81000 1.95250 3 O1 8.28376 187 -1.95250 7.81000 1.95250 3 O1 8.28376 188 7.81000 -1.95250 1.95250 3 O1 8.28376 189 -7.81000 -1.95250 1.95250 3 O1 8.28376 190 1.95250 -7.81000 1.95250 3 O1 8.28376 191 -1.95250 -7.81000 1.95250 3 O1 8.28376 192 5.85750 0.00000 5.85750 3 O1 8.28376 193 -5.85750 0.00000 5.85750 3 O1 8.28376 194 0.00000 5.85750 5.85750 3 O1 8.28376 195 0.00000 -5.85750 5.85750 3 O1 8.28376 196 7.81000 1.95250 -1.95250 3 O1 8.28376 197 -7.81000 1.95250 -1.95250 3 O1 8.28376 198 1.95250 7.81000 -1.95250 3 O1 8.28376 199 -1.95250 7.81000 -1.95250 3 O1 8.28376 200 7.81000 -1.95250 -1.95250 3 O1 8.28376 201 -7.81000 -1.95250 -1.95250 3 O1 8.28376 202 1.95250 -7.81000 -1.95250 3 O1 8.28376 203 -1.95250 -7.81000 -1.95250 3 O1 8.28376 204 5.85750 0.00000 -5.85750 3 O1 8.28376 205 -5.85750 0.00000 -5.85750 3 O1 8.28376 206 0.00000 5.85750 -5.85750 3 O1 8.28376 207 0.00000 -5.85750 -5.85750 3 O1 8.28376 208 5.85750 5.85750 0.00000 1 Sr1 8.28376 209 -5.85750 5.85750 0.00000 1 Sr1 8.28376 210 5.85750 -5.85750 0.00000 1 Sr1 8.28376 211 -5.85750 -5.85750 0.00000 1 Sr1 8.28376 212 1.95250 1.95250 7.81000 1 Sr1 8.28376 213 -1.95250 1.95250 7.81000 1 Sr1 8.28376 214 1.95250 -1.95250 7.81000 1 Sr1 8.28376 215 -1.95250 -1.95250 7.81000 1 Sr1 8.28376 216 1.95250 1.95250 -7.81000 1 Sr1 8.28376 217 -1.95250 1.95250 -7.81000 1 Sr1 8.28376 218 1.95250 -1.95250 -7.81000 1 Sr1 8.28376 219 -1.95250 -1.95250 -7.81000 1 Sr1 8.28376 220 7.81000 3.90500 0.00000 3 O1 8.73185 221 -7.81000 3.90500 0.00000 3 O1 8.73185 222 3.90500 7.81000 0.00000 3 O1 8.73185 223 -3.90500 7.81000 0.00000 3 O1 8.73185 224 7.81000 -3.90500 0.00000 3 O1 8.73185 225 -7.81000 -3.90500 0.00000 3 O1 8.73185 226 3.90500 -7.81000 0.00000 3 O1 8.73185 227 -3.90500 -7.81000 0.00000 3 O1 8.73185 228 7.81000 0.00000 3.90500 3 O1 8.73185 229 -7.81000 0.00000 3.90500 3 O1 8.73185 230 0.00000 7.81000 3.90500 3 O1 8.73185 231 0.00000 -7.81000 3.90500 3 O1 8.73185 232 3.90500 0.00000 7.81000 3 O1 8.73185 233 -3.90500 0.00000 7.81000 3 O1 8.73185 234 0.00000 3.90500 7.81000 3 O1 8.73185 235 0.00000 -3.90500 7.81000 3 O1 8.73185 236 7.81000 0.00000 -3.90500 3 O1 8.73185 237 -7.81000 0.00000 -3.90500 3 O1 8.73185 238 0.00000 7.81000 -3.90500 3 O1 8.73185 239 0.00000 -7.81000 -3.90500 3 O1 8.73185 240 3.90500 0.00000 -7.81000 3 O1 8.73185 241 -3.90500 0.00000 -7.81000 3 O1 8.73185 242 0.00000 3.90500 -7.81000 3 O1 8.73185 243 0.00000 -3.90500 -7.81000 3 O1 8.73185 244 7.81000 3.90500 1.95250 2 Ti1 8.94748 245 -7.81000 3.90500 1.95250 2 Ti1 8.94748 246 3.90500 7.81000 1.95250 2 Ti1 8.94748 247 -3.90500 7.81000 1.95250 2 Ti1 8.94748 248 7.81000 -3.90500 1.95250 2 Ti1 8.94748 249 -7.81000 -3.90500 1.95250 2 Ti1 8.94748 250 3.90500 -7.81000 1.95250 2 Ti1 8.94748 251 -3.90500 -7.81000 1.95250 2 Ti1 8.94748 252 7.81000 3.90500 -1.95250 2 Ti1 8.94748 253 -7.81000 3.90500 -1.95250 2 Ti1 8.94748 254 3.90500 7.81000 -1.95250 2 Ti1 8.94748 255 -3.90500 7.81000 -1.95250 2 Ti1 8.94748 256 7.81000 -3.90500 -1.95250 2 Ti1 8.94748 257 -7.81000 -3.90500 -1.95250 2 Ti1 8.94748 258 3.90500 -7.81000 -1.95250 2 Ti1 8.94748 259 -3.90500 -7.81000 -1.95250 2 Ti1 8.94748 260 5.85750 3.90500 5.85750 3 O1 9.15804 261 -5.85750 3.90500 5.85750 3 O1 9.15804 262 3.90500 5.85750 5.85750 3 O1 9.15804 263 -3.90500 5.85750 5.85750 3 O1 9.15804 264 5.85750 -3.90500 5.85750 3 O1 9.15804 265 -5.85750 -3.90500 5.85750 3 O1 9.15804 266 3.90500 -5.85750 5.85750 3 O1 9.15804 267 -3.90500 -5.85750 5.85750 3 O1 9.15804 268 5.85750 3.90500 -5.85750 3 O1 9.15804 269 -5.85750 3.90500 -5.85750 3 O1 9.15804 270 3.90500 5.85750 -5.85750 3 O1 9.15804 271 -3.90500 5.85750 -5.85750 3 O1 9.15804 272 5.85750 -3.90500 -5.85750 3 O1 9.15804 273 -5.85750 -3.90500 -5.85750 3 O1 9.15804 274 3.90500 -5.85750 -5.85750 3 O1 9.15804 275 -3.90500 -5.85750 -5.85750 3 O1 9.15804 276 5.85750 5.85750 3.90500 1 Sr1 9.15804 277 -5.85750 5.85750 3.90500 1 Sr1 9.15804 278 5.85750 -5.85750 3.90500 1 Sr1 9.15804 279 -5.85750 -5.85750 3.90500 1 Sr1 9.15804 280 5.85750 5.85750 -3.90500 1 Sr1 9.15804 281 -5.85750 5.85750 -3.90500 1 Sr1 9.15804 282 5.85750 -5.85750 -3.90500 1 Sr1 9.15804 283 -5.85750 -5.85750 -3.90500 1 Sr1 9.15804 284 END

1 0

Trouble of Path & Data List data of Artemis
by Joji Kuniya 15 Jun '07

15 Jun '07

Dear Bruce I tried fitting to my EXAFS date by Artemis program. Abruptly fitted and Path spectrum was broaden. So, I checked the paths in the Data & Path list and the feff calculated results. So that, the paths data in the Data & Path is differed from the left side feff calculated data(of course, number of # of the interpretation and the path of data & Path is the same). This troube is almostly? dissoleved when new Artemis was opened. But, scarcely this troubel have occured again. I reinstalled your feffit program, but I have been occasionally encountering. Did yo have some experience like this? Please teach me what to do to clear thus trouble. Thank you Joji Kuniya

2 1

XANES / NEXAFS with feff8.4
by s440697＠stud.uni-goettingen.de 15 Jun '07

15 Jun '07

Hallo @all, (first at all, sorry for my bad english) i'm a student working on my diploma thesis (nexafs/xanes) and my job is to simulate with FEFF 8.4 spectra, for example absorption as a function of energy (mu_(E)). I'm a newbie in this topic and i tried to get the k-edge of Sulfur for the substance gypsum (CaSO4 * 2(H2O)) and pyrite (FeS2). I'm interested in the XANES-range of the spectra not the EXAFS. I get everytime my peaks at ~2472 eV for Sulfur as absorber whatever substance i use (gypsum, pyrite,...). There are no differences with the peak position on the energy-scale or shifts. I'm really confused :-( I think, there should be differences in the spectra... I send you two feff.inp files from my feff-runs. My source is the mineralogy database (http://rruff.geo.arizona.edu/AMS/amcsd.php) where i get the data for the unitcell. Then i put the data in the XtalDraw program to get the positions of the Atoms in Angstrom, by the way i get i nice 3D-View of the unitcell :-). Then i put the values of the positions into feff... I simulated pyrite with 12 atoms and gypsum with 48. I'm appreciative for every help :-) ciao, Eckhard --------------------------------- Eckhard Bosman e.bosman(a)stud.uni-goettingen.de +49 (0)551-39-14441 Raum: E0.104 Institut für Röntgenphysik Friedrich-Hund-Platz 1 37077 Göttingen Germany

1 0

How to make a hole on feff.inp file
by Joji Kuniya 07 Jun '07

07 Jun '07

Dear members I have been treating with an EXAFS spectra of an oxide crystals. This crystal has some holes (defects) in the system.I have not a good idea in handling of the hole system, I put hydrogen instead of the hole. I think this procedure is not appropriated. Please teach me how to make hole on a feff.inp file. Thank you. Joji Kuniya

2 2

bond distance resolution and correlation of parameters in MS analyses?
by MarkBondin 06 Jun '07

06 Jun '07

Hi, I would like general opinions of some EXAFS practioners in regards to the most widely accepted methods for bond distance resolution and correlation of parameters in both single scattering (SS) and multiple scattering (MS) EXAFS refinements and if these can be said to differ? 1)Does the equation for bond distance resolution (r = pi/2deltak) only apply to SS? I have held the opinion that this can be applied to MS analysis however I have recently been informed that this equation does not correctly describe distance resolution in MS analyses. The paper in Coord. Chem. Rev. 2005, 249, 141-160 describes this and is this concordant with the views of the wider EXAFS community? 2) What is the actual equation which defines the determinacy of a fitting procedure and does this differ between SS and MS analyses? For MS analyses there has been a recently published equation (Coord. Chem. Rev. 2005, 249, 141-160) which takes into acount the number of dimensions used in the analyses and is this only relevant to MS analyses of data? This has also been expressed in the paper by Binsted (Biochemistry. 1992, 31, 12117-12125) however a different equation has been detailed by Stern (Phys. Rev. B. 1993, 48, 9825-9827) which I have been using as a guide in my MS analyses. Is this acceptable? Any thoughts and opinions would be greatly appreciated as this relates directly to corrections suggested to be made to my PhD thesis! Many thanks, Mark

3 3

help with CoCr bimetallic catalyst
by codruta.zoican＠yale.edu 06 Jun '07

06 Jun '07

I have been, working with a bimetallic Co/Cr catalyst supported on a silica template for synthesis of single wall carbon nanotubes. Recently I have performed some analysis at the NSLS. It is clear from the spectra in R space that the interatomic distances are modified compared to the monometallic catalyst therefore I am dealing with an alloy. Does anyone have or know about a model that would allow me to get a coordination nomber using Artemis. Thank you, Codruta.

2 1