Re: [Ifeffit] Generating single scattering paths in Artemis
<
This can be fixed by editing the feff.inp file to remove the Fe potential 1, but that's not enough--the oxygen scatterers then have to have their potential renumbered to 1 to make things work. That's a lot of work to do what should be simple.
So I vote for changing the way Artemis works in such circumstances so that less editing is needed: if the absorbing atom is not present in the scattering list, then it shouldn't have a second entry in the potential list.
I second this vote, since I also have had this same problem. New users
could become quickly disgruntled by the Fatal Error message when
attempting to put in simple systems or just by choosing a short cluster
distance to only include the first shell in the FEFF calculation. At a
minimum, it would be nice if Artemis trapped this error and reported a
more friendly popup error message.
Dave
_________________________________
David Barton, PhD.
The Dow Chemical Company
Catalysis R&D
_______________________________________________
Ifeffit mailing list
Ifeffit@millenia.cars.aps.anl.gov
http://millenia.cars.aps.anl.gov/mailman/listinfo/ifeffit
<
One of the nice things about FEFF3 is that single scattering calculations were pretty well automated. Since then it's been possible, but not that easy. The OVERLAP cards, in particular were hacked together to get reasonable potentials, but even I don't find them friendly. It seems to me that one could/should arrange the defaults in FEFF>3 to permit a FEFF3 type calculation, e.g., with specification of coordination approx number near neighbor distance (that could be estimated by default too) and backscatterer type only. Since Artemis calls FEFF6, perhaps (?) such defaults could be built into a special call. That seems to me to be what a number of people in the list are asking for. John Rehr
participants (2)
-
Frenkel, Anatoly
-
John J. Rehr