Hi Johan, Sorry for the trouble. Apparently I haven't tested with a wide enough range of Feff files! For reference, this feff.dat file did not have labeled atoms, which is allowed in Feff but which I hadn't considered. The attached feffdat.py solves this problem (and fixed in the github repository). If you put this file into /usr/share/larch/plugins/xafs/ on linux (or, if you were using Windows, to C:\Program Files\larch\plugins\xafs) and restart larch, you should be able to read the feff.dat file. Cheers, --Matt On Wed, Apr 9, 2014 at 9:03 AM, Johan Nilsson wrote:

Hello,

I'm experimenting a bit with exafs fitting in Larch but I've come across a problem when I try to import my feff paths. Basically what happens is:

$ larch Larch 0.9.22 (12-Dec-2013) M. Newville, T. Trainor using python 2.7.5, numpy 1.7.1, wx-enabled, wx version 2.8.12.1 larch> path = feffpath('feff0001.dat') file <stdin>, line 0 IndexError: list index out of range path = feffpath('feff0001.dat') ^^^ larch>

I don't know if this is an issue with my input file to feff or if this is some sort of bug in Larch. I wrote the feff.inp from scratch using a template and the structure is supposed to be bulk PdO. I've attached my feff.inp and feff0001.dat if someone wants to try and reproduce the problem. I tried another set of paths that was calculated for FeO using an input file from webatoms and those appear to import without issues. I've attached those as well in a zip if someone wants to compare the two sets. I'm running Ubuntu 13.10 on my PC.

Best regards, Johan

_______________________________________________ Ifeffit mailing list Ifeffit@millenia.cars.aps.anl.gov http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit