I have been trying to fit a Co(OH)2 reference sample and think I have a good fit, but I have a couple reservations about it and wanted to run it by some people for an expert opinion. If you are interested, I have included the Athena file, an image of the fit, and the fit log file. Please read on! If not, sorry I spammed you. As you can see, the fit contains four paths. They are all single scattering paths, and the paths with the four largest ranks according to feff. All paths share the same SO2 and deltaE. Each path has its own delR and ss. After some work, I got it to the point that the fit looks pretty (R-factor<0.02), but I have several reservations about it: 1) Generally, the ss values are all higher than I would like. 0.007 even seems high to me for a metal-O bond. Am I right about this? Would this indicate that this may have been a poor choice for reference sample (I should mention it is a powder) and it is not very crystalline? Could it mean there was something we overlooked when we recorded the data? 2) The biggest problem with the fit is the large error on ss_O2 and ss_O3. The largest feature at ~2.75 is obviously Co-Co scattering, but the Co-O paths help to fit the shoulder (or feature at ~3.1 in the Real part) in R-space. If I take them out, then the Co path has a large ss with an equally large error. So here is my question. If I add more paths, the error of ss_O2 and ss_O3 will go down, but then the errors on the new path will consequently be large, so when do I stop adding paths? For the purpose of my samples, I am only interested in the first Co-O path and the Co-Co path. Is this fit good enough you would publish it? Please feel free to critique any other aspect of the fit too. Thanks for your input! Neil
Oh yeah, the scattering paths were calculated from the crystal structure of Co(OH)2 using feff in Artemis. Neil From: Ifeffit [mailto:ifeffit-bounces@millenia.cars.aps.anl.gov] On Behalf Of Neil M Schweitzer Sent: Friday, September 02, 2016 3:18 PM To: ifeffit@millenia.cars.aps.anl.gov Subject: [Ifeffit] Co fitting questions I have been trying to fit a Co(OH)2 reference sample and think I have a good fit, but I have a couple reservations about it and wanted to run it by some people for an expert opinion. If you are interested, I have included the Athena file, an image of the fit, and the fit log file. Please read on! If not, sorry I spammed you. As you can see, the fit contains four paths. They are all single scattering paths, and the paths with the four largest ranks according to feff. All paths share the same SO2 and deltaE. Each path has its own delR and ss. After some work, I got it to the point that the fit looks pretty (R-factor<0.02), but I have several reservations about it: 1) Generally, the ss values are all higher than I would like. 0.007 even seems high to me for a metal-O bond. Am I right about this? Would this indicate that this may have been a poor choice for reference sample (I should mention it is a powder) and it is not very crystalline? Could it mean there was something we overlooked when we recorded the data? 2) The biggest problem with the fit is the large error on ss_O2 and ss_O3. The largest feature at ~2.75 is obviously Co-Co scattering, but the Co-O paths help to fit the shoulder (or feature at ~3.1 in the Real part) in R-space. If I take them out, then the Co path has a large ss with an equally large error. So here is my question. If I add more paths, the error of ss_O2 and ss_O3 will go down, but then the errors on the new path will consequently be large, so when do I stop adding paths? For the purpose of my samples, I am only interested in the first Co-O path and the Co-Co path. Is this fit good enough you would publish it? Please feel free to critique any other aspect of the fit too. Thanks for your input! Neil
hi Neil: The sigma squared values for your first Co-O path and the Co-Co path are not out of line with those I have seen for Co(OH)2. Personally, I would not include the last Co-O path and cut the fitting range down to 3.5A or so. It is possible that the second Co-O path is also not relevant. The distance shift seems to be very large and simply compensating for the peak at 2.7A. Again, I have seen this in my Co(OH)2 samples as well. The question is what do you need to glean from these data. Carlo On Fri, 2 Sep 2016, Neil M Schweitzer wrote:
I have been trying to fit a Co(OH)2 reference sample and think I have a good fit, but I have a couple reservations about it and wanted to run it by some people for an expert opinion. If you are interested, I have included the Athena file, an image of the fit, and the fit log file. Please read on! If not, sorry I spammed you.
As you can see, the fit contains four paths. They are all single scattering paths, and the paths with the four largest ranks according to feff. All paths share the same SO2 and deltaE. Each path has its own delR and ss. After some work, I got it to the point that the fit looks pretty (R-factor<0.02), but I have several reservations about it:
1) Generally, the ss values are all higher than I would like. 0.007 even seems high to me for a metal-O bond. Am I right about this? Would this indicate that this may have been a poor choice for reference sample (I should mention it is a powder) and it is not very crystalline? Could it mean there was something we overlooked when we recorded the data?
2) The biggest problem with the fit is the large error on ss_O2 and ss_O3. The largest feature at ~2.75 is obviously Co-Co scattering, but the Co-O paths help to fit the shoulder (or feature at ~3.1 in the Real part) in R-space. If I take them out, then the Co path has a large ss with an equally large error. So here is my question. If I add more paths, the error of ss_O2 and ss_O3 will go down, but then the errors on the new path will consequently be large, so when do I stop adding paths? For the purpose of my samples, I am only interested in the first Co-O path and the Co-Co path.
Is this fit good enough you would publish it? Please feel free to critique any other aspect of the fit too.
Thanks for your input!
Neil
-- Carlo U. Segre -- Duchossois Leadership Professor of Physics Interim Chair, Department of Chemistry Director, Center for Synchrotron Radiation Research and Instrumentation Illinois Institute of Technology Voice: 312.567.3498 Fax: 312.567.3494 segre@iit.edu http://phys.iit.edu/~segre segre@debian.org
Thanks Carlo,
For this sample specifically, I am only trying to get a reasonable estimate of SO2 for use with my samples, which are supported, Co oxide clusters (catalysts).
You are right. If it take out the extra O scattering paths and reduce the R-range, the fit becomes significantly better (both R-factor and Reduced chi-square are reduced). However, now the SO2 is ~1.11. Does this make physical sense? What would be the cause of it being too big?
Neil
-----Original Message-----
From: Ifeffit [mailto:ifeffit-bounces@millenia.cars.aps.anl.gov] On Behalf Of Carlo Segre
Sent: Friday, September 02, 2016 3:42 PM
To: XAFS Analysis using Ifeffit
I have been trying to fit a Co(OH)2 reference sample and think I have a good fit, but I have a couple reservations about it and wanted to run it by some people for an expert opinion. If you are interested, I have included the Athena file, an image of the fit, and the fit log file. Please read on! If not, sorry I spammed you.
As you can see, the fit contains four paths. They are all single scattering paths, and the paths with the four largest ranks according to feff. All paths share the same SO2 and deltaE. Each path has its own delR and ss. After some work, I got it to the point that the fit looks pretty (R-factor<0.02), but I have several reservations about it:
1) Generally, the ss values are all higher than I would like. 0.007 even seems high to me for a metal-O bond. Am I right about this? Would this indicate that this may have been a poor choice for reference sample (I should mention it is a powder) and it is not very crystalline? Could it mean there was something we overlooked when we recorded the data?
2) The biggest problem with the fit is the large error on ss_O2 and ss_O3. The largest feature at ~2.75 is obviously Co-Co scattering, but the Co-O paths help to fit the shoulder (or feature at ~3.1 in the Real part) in R-space. If I take them out, then the Co path has a large ss with an equally large error. So here is my question. If I add more paths, the error of ss_O2 and ss_O3 will go down, but then the errors on the new path will consequently be large, so when do I stop adding paths? For the purpose of my samples, I am only interested in the first Co-O path and the Co-Co path.
Is this fit good enough you would publish it? Please feel free to critique any other aspect of the fit too.
Thanks for your input!
Neil
-- Carlo U. Segre -- Duchossois Leadership Professor of Physics Interim Chair, Department of Chemistry Director, Center for Synchrotron Radiation Research and Instrumentation Illinois Institute of Technology Voice: 312.567.3498 Fax: 312.567.3494 segre@iit.edu https://urldefense.proofpoint.com/v2/url?u=http-3A__phys.iit.edu_-7Esegre&d=CwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=oD5QfHEvBMM5YYrnfMF2YrJNX5aSKvlIRGd2B3iC9kQ&m=UHovCVboippuwjHS83MUbFyIwD3zbmNtLtJdSaRupGY&s=vR2qFm6nzIZ4Hvsa87KtvYjUzdKhqohA72GQpeTS-wg&e= segre@debian.org _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov https://urldefense.proofpoint.com/v2/url?u=http-3A__millenia.cars.aps.anl.gov_mailman_listinfo_ifeffit&d=CwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=oD5QfHEvBMM5YYrnfMF2YrJNX5aSKvlIRGd2B3iC9kQ&m=UHovCVboippuwjHS83MUbFyIwD3zbmNtLtJdSaRupGY&s=0zz-kQkc5YsoGwUAbnlBmAh-FL0edswrqe2m8WHLMY4&e= Unsubscribe: https://urldefense.proofpoint.com/v2/url?u=http-3A__millenia.cars.aps.anl.gov_mailman_options_ifeffit&d=CwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=oD5QfHEvBMM5YYrnfMF2YrJNX5aSKvlIRGd2B3iC9kQ&m=UHovCVboippuwjHS83MUbFyIwD3zbmNtLtJdSaRupGY&s=O7NfUTdRgH9IJMhcNbrkMTJBBXYNzXtNppPwcG2TkYc&e=
Hi Neil: I took your data and fit it with the Co(OH)2 structure but only the first two paths: Co-O and Co-Co. I used a k-range of 2-10 and dk=3 and the r-range of 1-3.5 with dr=0.2. The fit results are as follows R-factor = 0.024528565 Guess parameters +/- uncertainties (initial guess): amp = 1.0648700 +/- 0.1581370 (1.0000) enot = -1.2653240 +/- 1.2834050 (0.0000) dr_o = -0.0140240 +/- 0.0139460 (0.0000) ss_o = 0.0090020 +/- 0.0025450 (0.0030) dr_co = -0.0090720 +/- 0.0119710 (0.0000) ss_co = 0.0078130 +/- 0.0016030 (0.0030) The sigma squared values for both paths are not unreasonable. This is a fairly disordered structure becuase each of the oxygens has a hydrogen attached to it and they sort of get in each other's way. If you remove one of the hydrogens by oxidizing it, you get CoOOH which is much more ordered as each hydrogen is now close to 2 oxygens. If I add a second Co-O path, I do see a slight improvementin the Co-Co sigma squared but the second Co-O path has a large negative shift in distance and has a huge sigma squared so it has dubious value. The very large sigma squared of this second Co-O path (0.024) is consistent with the disorder I mentioned above. If this is your standard for a catalyst, then you probably only care deeply about the Co-O near neighbor path. That is pretty much independent of what you do with the Co-Co and other Co-O paths. however, note that this structure hae Co-O6 octahedra which may not be relevant for a catalyst on a surface. Cheers, Carlo On Fri, 2 Sep 2016, Neil M Schweitzer wrote:
Thanks Carlo, For this sample specifically, I am only trying to get a reasonable estimate of SO2 for use with my samples, which are supported, Co oxide clusters (catalysts).
You are right. If it take out the extra O scattering paths and reduce the R-range, the fit becomes significantly better (both R-factor and Reduced chi-square are reduced). However, now the SO2 is ~1.11. Does this make physical sense? What would be the cause of it being too big?
Neil
-----Original Message----- From: Ifeffit [mailto:ifeffit-bounces@millenia.cars.aps.anl.gov] On Behalf Of Carlo Segre Sent: Friday, September 02, 2016 3:42 PM To: XAFS Analysis using Ifeffit
Subject: Re: [Ifeffit] Co fitting questions hi Neil:
The sigma squared values for your first Co-O path and the Co-Co path are not out of line with those I have seen for Co(OH)2. Personally, I would not include the last Co-O path and cut the fitting range down to 3.5A or so. It is possible that the second Co-O path is also not relevant. The distance shift seems to be very large and simply compensating for the peak at 2.7A. Again, I have seen this in my Co(OH)2 samples as well.
The question is what do you need to glean from these data.
Carlo
On Fri, 2 Sep 2016, Neil M Schweitzer wrote:
I have been trying to fit a Co(OH)2 reference sample and think I have a good fit, but I have a couple reservations about it and wanted to run it by some people for an expert opinion. If you are interested, I have included the Athena file, an image of the fit, and the fit log file. Please read on! If not, sorry I spammed you.
As you can see, the fit contains four paths. They are all single scattering paths, and the paths with the four largest ranks according to feff. All paths share the same SO2 and deltaE. Each path has its own delR and ss. After some work, I got it to the point that the fit looks pretty (R-factor<0.02), but I have several reservations about it:
1) Generally, the ss values are all higher than I would like. 0.007 even seems high to me for a metal-O bond. Am I right about this? Would this indicate that this may have been a poor choice for reference sample (I should mention it is a powder) and it is not very crystalline? Could it mean there was something we overlooked when we recorded the data?
2) The biggest problem with the fit is the large error on ss_O2 and ss_O3. The largest feature at ~2.75 is obviously Co-Co scattering, but the Co-O paths help to fit the shoulder (or feature at ~3.1 in the Real part) in R-space. If I take them out, then the Co path has a large ss with an equally large error. So here is my question. If I add more paths, the error of ss_O2 and ss_O3 will go down, but then the errors on the new path will consequently be large, so when do I stop adding paths? For the purpose of my samples, I am only interested in the first Co-O path and the Co-Co path.
Is this fit good enough you would publish it? Please feel free to critique any other aspect of the fit too.
Thanks for your input!
Neil
-- Carlo U. Segre -- Duchossois Leadership Professor of Physics Interim Chair, Department of Chemistry Director, Center for Synchrotron Radiation Research and Instrumentation Illinois Institute of Technology Voice: 312.567.3498 Fax: 312.567.3494 segre@iit.edu https://urldefense.proofpoint.com/v2/url?u=http-3A__phys.iit.edu_-7Esegre&d=CwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=oD5QfHEvBMM5YYrnfMF2YrJNX5aSKvlIRGd2B3iC9kQ&m=UHovCVboippuwjHS83MUbFyIwD3zbmNtLtJdSaRupGY&s=vR2qFm6nzIZ4Hvsa87KtvYjUzdKhqohA72GQpeTS-wg&e= segre@debian.org _______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov https://urldefense.proofpoint.com/v2/url?u=http-3A__millenia.cars.aps.anl.gov_mailman_listinfo_ifeffit&d=CwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=oD5QfHEvBMM5YYrnfMF2YrJNX5aSKvlIRGd2B3iC9kQ&m=UHovCVboippuwjHS83MUbFyIwD3zbmNtLtJdSaRupGY&s=0zz-kQkc5YsoGwUAbnlBmAh-FL0edswrqe2m8WHLMY4&e= Unsubscribe: https://urldefense.proofpoint.com/v2/url?u=http-3A__millenia.cars.aps.anl.gov_mailman_options_ifeffit&d=CwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=oD5QfHEvBMM5YYrnfMF2YrJNX5aSKvlIRGd2B3iC9kQ&m=UHovCVboippuwjHS83MUbFyIwD3zbmNtLtJdSaRupGY&s=O7NfUTdRgH9IJMhcNbrkMTJBBXYNzXtNppPwcG2TkYc&e=
_______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit Unsubscribe: http://millenia.cars.aps.anl.gov/mailman/options/ifeffit
-- Carlo U. Segre -- Duchossois Leadership Professor of Physics Interim Chair, Department of Chemistry Director, Center for Synchrotron Radiation Research and Instrumentation Illinois Institute of Technology Voice: 312.567.3498 Fax: 312.567.3494 segre@iit.edu http://phys.iit.edu/~segre segre@debian.org
participants (2)
-
Carlo Segre
-
Neil M Schweitzer