[Ifeffit] Re: A question about the new Artemis version

[Scott Calvin]

Hi,

Sean (my student) just had the same thing happen. It doesn't look like it
trapped anything when the problem occurred, but it did fail to create the
temporary folders that Artemis keeps the FEFF calculation in while running.
Sean came up with a simple fix that seems to have done the trick for us:

1) Point the data files back where they belong.

2) Try to run the fit. Artemis/IFEFFIT will complain (under the "messages"
pallet) that it can't find any of your paths, and it will tell you the
folder it looked for them in. Note the name of that folder! It will be
something like Ifeffit\horae\stash\artemis.project.17\data0.feff1.

3) Create a folder of the appropriate name in the appropriate location.

4) Copy the proper feff files back into it (assuming you have them
somewhere else; otherwise rerun FEFF and then copy them in).

5) Save the project and quit Artemis (not sure if you have to run a fit
once first).

6) The project should now work normally when you reopen Artemis.

Hopefully this also gives Bruce a clue as to what causes the problem. Since
those folders are clearly temporary folders used while the project is
running, presumably this kind of problem might be caused by a crash at just
the wrong moment, perhaps when Artemis was doing some bookkeeping with
those folders?

--Scott Calvin
Sarah Lawrence College
 
At 01:35 PM 4/1/2004 -0500, you wrote:
>On Wednesday 31 March 2004 09:50 pm, Peter Southon wrote:
>> I have found that very occasionally Artemis will save a project into
>> Bruces' new zip file format, but neglect to actually add in some (or
>> any) of the data and feff files. The first symptom is that the size
>> of the saved project is much smaller than it should be. Thus when
>> re-opened, the project looks fine, but Artemis cannot open any of
>> the required files when a fit is attempted. The data can be
>> replaced, but I can't find a way of replacing any feff calculations
>> without re-entering all of the parameters.
>
>That's news to me.  I have not yet seen that problem myself.  The next
>time it happens, if there is a trap file, please send it my way.
>
>If you are in that position again, I believe that you can recover
>without having to reenter all your path parameters.  When you finish
>the feff calculation and you get the dialog about how many paths to
>import, choose the "No paths" option.   You need to run feff again so
>that the feff data is in the project folder, but you don't need to
>import paths since you already have a list of them defined.
>
>That's the theory, anyway, and the reason for a "no paths" option.  If
>your milage varies, let me know.
>