Rasmus and Wayne,
I tried to reproduce the error message and found that it works fine
now, whether I edit the paths at the startup (as before) or do so
after the project loaded (as suggested below). I am not sure whether
some of the fixes that Wayne applied did affect this problem or I did
things in a different order this time..
Either way, things appear to work as they should.
Patrick
On Oct 5, 2009, at 4:56 AM, Rasmus Fogh wrote:
> Dear All,
>
> There is a special aspect to the start-up. When the files are not
> found where the CCPN data says they should be, Analysis serches the
> startup directory and nearby directories to see if it can find a set
> of files with the same names. If it can it propose4s those as teh
> new location. It is possible that editing directly after startup
> messes up something. I would recommend finishing the load first, and
> reorganising later. If that works maybe we should look at either
> fixing the problem or inactivating the editing buttins on start-up.
>
> Yours,
>
> Rasmus
>
> ---------------------------------------------------------------------------
> Dr. Rasmus H. Fogh Email: [log in to unmask]
> Dept. of Biochemistry, University of Cambridge,
> 80 Tennis Court Road, Cambridge CB2 1GA, UK. FAX (01223)766002
>
> On Fri, 2 Oct 2009, Patrick van der Wel wrote:
>
>> I'll try to see if I can reproduce it myself then. If so, I can try
>> to send you the files and/or any additional details I figure out.
>>
>> And yes, it was on startup.
>>
>> Thanks,
>> Patrick
>>
>> On Oct 2, 2009, at 3:33 PM, Wayne Boucher wrote:
>>
>>> Hello,
>>> For the life of me I cannot reproduce that problem. But I did
>>> find another bug which meant that the shift left was shifting all
>>> the directories instead of just the "top" one, so I've fixed that
>>> (I think).
>>> Did the problem below happen on start-up? Because you can also
>>> get at the same dialog, later, via the Experiment --> Edit Spectra
>>> dialog, in the Data Locations tab. Hopefully even if the start-up
>>> one messed up, you can fix it later.
>>> Wayne
>>> On Fri, 2 Oct 2009, Patrick van der Wel wrote:
>>>> Hi,
>>>> I tried to update the paths in a moved project (where the data
>>>> also moved). So I opened the project, and it popped up the
>>>> window where it asks for the locations of the datafiles (which
>>>> were not where it expected them).
>>>> I noticed that this window nicely has the option to shift parts
>>>> of paths between relative and absolute, seemingly to allow a
>>>> common absolute path. This worked ok to some extent...
>>>> I was able to shift various path segments from absolute to
>>>> relative, and then tried to update the absolute 'root' path to
>>>> the new location. Unfortunately, this worked fine for the first
>>>> dataset that used the common absolute path, but the next several
>>>> datasets seemed to have their relative paths default back to what
>>>> it was originally, before I shift parts of paths from absolute to
>>>> relative. As a result, the paths are now completely incorrect,
>>>> and largely missing.
>>>> Strangely, this did work fine for some part of the datasets, and
>>>> I did not see any error messages on the console. I am sorry that
>>>> I don't really have a clearer description of what exactly went
>>>> wrong, but I am not really sure.
>>>> Patrick
>>>> PS. Schematically:
>>>> original setup:
>>>> ABSOLUTE RELATIVE
>>>> /nfsdrv1/path/path/path/path sub/sub/sub/data1
>>>> /nfsdrv1/path/path/path/path sub/sub/sub/data2
>>>> /nfsdrv1/path/path/path/path sub/sub/sub1/data3
>>>> /nfsdrv1/path/path/pathB/pathB sub/sub/sub1/data4
>>>> Desired new setting:
>>>> ABSOLUTE RELATIVE
>>>> /nfsdrv2/path/path/ path/path/sub/sub/sub/data1
>>>> /nfsdrv2/path/path/ path/path/sub/sub/sub/data2
>>>> /nfsdrv2/path/path/ path/path/sub/sub/sub1/data3
>>>> /nfsdrv2/path/path/ pathB/pathB/sub/sub/sub1/data4
>>>> Actual new setting:
>>>> ABSOLUTE RELATIVE
>>>> /nfsdrv2/path/path/ path/path/sub/sub/sub/data1
>>>> /nfsdrv2/path/path/ sub/sub/sub/data2 <==== incorrect!
>>>> /nfsdrv2/path/path/ path/path/sub/sub/sub1/data3
>>>> /nfsdrv2/path/path/ pathB/pathB/sub/sub/sub1/data4
|