Dear Andy,
What is wrong is clear - how it got there less so. I am leaving tonight,
so Tim can maybe give some better advice tomorrow, but for what it is
worth:
This is one of those things that should not happen, unless 1) someone has
been bypassing the API or going into the XML files with an editor, or 2)
we have a bug. Has anyone been doing somethying non-standard, lately? or
have you had any strange crashes?
Unfortunately, you need to do nasty things to fix this bug, as you cannot
load the data into memory. I would propose
1) make a backup copy of all the XML files (tar and gzip, for instance),
so you can always come back to the situation such as it is now
2) keep any error messages, and make a note of what you did just before
this happened. Then we can maybe figure it out later.
3) go into the Nmr.xml file with an editor. Find a line that contains the
string
maxAliasedFreq="113.47
and make sure that minAliasedFreq (same line) is smaller than
maxAliasedFreq. If there is one of those, that should fix the problem. Of
course, there might be further problems in the file.
Or, if you are unsure about this, wait till you get an answer from somone
else tomorrow.
Cheers,
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 Thu, 12 May 2005, Dr Andy Herbert wrote:
> Hi,
>
> I have just tried to reopen my project and get the following error
> message:
>
> Project invalid, please quit, fix and re-start:
> ccp.Nmr.ExpDimRef.maxAliasedFreq constraint
> value_is_not_smaller_than_minAliasedFreq
> violated by value
> 113.475...
>
> Any help would be appreciated.
>
> Cheers
>
> Andy
>
>
> --
> Dr Andy Herbert
> Department of Chemistry
> University of Edinburgh
> West Mains Road
> Edinburgh
> UK
> EH9 3JJ
> Tel: +44 (0)131 650 4704 or 650 7372
> Email: [log in to unmask]
>
|