Hello,
Sorry for the slow reply but we've been busy with visitors.
I tried to reproduced this problem but failed except for the last problem,
which I have now fixed.
I took a 2D HSQC and a pseudo-3D with 17 planes in it. I picked some
peaks in the 2D and used the Peaks --> Peak Lists dialog with the Peak
Lists tab Copy Peaks button to move the peaks over to the pseudo-3D.
I first tried copying over into just the first plane (that became the
first peak list) and then copying over into all the planes (that became
the second peak list).
The Peak Table tab then showed correct values in the Shift F1 and Shift F2
columns and the correct parameter value in the Sampled column.
And I didn't get an exception when I tried to delete pseudo-peaks (but
it's quite possible this is something where it needs to be done in a
certain way to cause the problem and I'm doing it differently).
If I pick the first plane of the pseudo-3D by ctrl-shift-drag rather than
by copying them from the 2D, this also seems to work (but I'm not sure I
understand what you are saying went wrong there).
The ctrl picking method definitely failed for a pseudo-3D. It was also
failing for a 2D spectrum being displayed in the pseudo-3D window. So
I've fixed that (hopefully!).
I guess one option is for you to pack up the 2D and pseduo-3D data files
(and the par files) that you are trying to use and send that to me so that
I can try and reproduce the problems with your data. (I don't need an
Analysis project, just the data files.)
Wayne
On Fri, 20 Feb 2009, Steven Vance wrote:
> To clarify further, what I get when copying from 2D to 3D is that all the
> peaks have the correct 1H shift (dim 1 for me) and they are distributed
> through the planes (dim2 in the AZARA file & under File Details), but the
> 15N shift of the peaks is not set at all. I guess the mapping from the 2D to
> the 3D is going wrong.
>
> I also managed to provoke a couple of other problems:
>
> >>> C <-> Python peak mismatch. Selected C peak was not in currentPeaks.
>
> happens when deleting peak(s) in the pseudo 3D - doesn't seem to happen in
> other spectra. The peak(s) go though.
>
> Then in my pseudo 3D, if I try to pick the peaks by hand (ctrl shift click
> drag), most peaks are picked in most planes, but some big ones that should
> be aren't. Then if I try to go in and pick any additional peaks by hand
> (ctrl click) I get:
>
> >>> Exception in Tkinter callback
> Traceback (most recent call last):
> File "/usr/lib/python2.4/lib-tk/Tkinter.py", line 1345, in __call__
> return self.func(*args)
> File
> "/usr/local/ccpnmr/temporaryReleaseDir/ccpnmr/ccpnmr2.0/python/memops/gui/ScrolledWindow.py",
> line 1007, in <lambda>
> File
> "/usr/local/ccpnmr/temporaryReleaseDir/ccpnmr/ccpnmr2.0/python/memops/gui/ScrolledWindow.py",
> line 980, in releaseFunc
> File
> "/usr/local/ccpnmr/temporaryReleaseDir/ccpnmr/ccpnmr2.0/python/memops/gui/ScrolledWindow.py",
> line 1559, in selectLocation
> File
> "/usr/local/ccpnmr/ccpnmr2.0/python/ccpnmr/analysis/popups/WindowPopup.py",
> line 2269, in selectSingle
> self.createNewPeak(a, b, row, col)
> File
> "/usr/local/ccpnmr/ccpnmr2.0/python/ccpnmr/analysis/popups/WindowPopup.py",
> line 2305, in createNewPeak
> for dataDimRef in dataDim.dataDimRefs:
> AttributeError: 'SampledDataDim' object has no attribute 'dataDimRefs'
>
> Finally, the first plane of the pseudo 3D seems particularly funny! When
> picking peaks (ctrl shift click drag) peaks get picked on every point above
> the picking threshold (or every other point etc if the exclusion buffer is
> set >0).
>
|