Hello Wayne,
>The variable 'value', which for some reason is None in the line where the
>exception has been thrown, is set by a call to getValue() on a peakDim
>object (so the information stored for one dimension of a peak). The
>function getValue() returns None in two places.
>
>It returns None if the 'dataDimRef' of the peakDim has not been set, which
>effectively means the referencing has not been set up for the peakDim.
>
>It also returns None if the position (in points) of the peakDim has not
>been defined. (So the 'position' is the peak position in points and the
>'value' is the peak position in ppm.)
I guess I need to check all my peaks for a weird assignment. A quick look at
the resonances revealed some unassigned resonances with a default name given
by Analysis. I think their existence should be valid for dataShifter. I'll
look more carefully at all peaks.
>When you say you shifted the peak list, do you mean with the "Copy Peaks"
>functionality or with the "Copy Peak Assignments" functionality?
I used an arrow next to "Select peak list to copy" and had the appropriate
peak list selected from my spectrum. I have just done the copy of the
assignments with "Select measurment list to copy" to a new project and it
was successful (took me ~40 min and it says the size in Measurements Lists
popup is 2144(#,kB,...?))
>On the performance issue, how many peaks were there in the 3d Cnoesy peak
>list?
The peak list contains ~3900 peaks.
Thank you,
Vitaliy
|