Hi David,
Sorry for the lack of noise this end. Would you be able to send us a copy of the project (minus spectra) - this way I can see if we get the same issues.
Thanks, Dan
On 17 Dec 2010, at 10:25, David Yadin wrote:
> Hi Dan
>
> I e-mailed about the problem below a while back and have since been working with a different project without problems. However, the same problem has appeared in my new project. It doesn't seem to happen with a slightly older version of the same project though.
>
> I was just wondering if anyone had found the source of this error or anyone else has seen this. Do you think it would be possible for me to send you a project to have a look at?
>
> Best wishes
>
> David
>
> -----Original Message-----
> From: CcpNmr software mailing list [mailto:[log in to unmask]] On Behalf Of David Yadin
> Sent: 19 August 2010 10:04
> To: [log in to unmask]
> Subject: Re: Error displaying 3D spectrum
>
> Hi Dan
>
> I was just wondering if you'd found the source of problem I reported last month about the import of new 3D spectra into my Analysis project. I've also tried copying a peaklist to a newly opened spectrum and this generates the following error:
>
> Exception in Tkinter callback
> Traceback (most recent call last):
> File "Tkinter.pyo", line 1410, in __call__
> File "C:\Program Files (x86)\CCPN\python\memops\gui\ScrolledMatrix.py", line 7
> 36, in mouseClick
> File "C:\Program Files (x86)\CCPN\python\memops\gui\ScrolledMatrix.py", line 1
> 829, in selectCell
> File "C:\Program Files (x86)\CCPN\python\ccpnmr\analysis\popups\EditPeakLists.
> py", line 1190, in selectCell
> File "C:\Program Files (x86)\CCPN\python\ccpnmr\analysis\core\PeakBasic.py", l
> ine 1247, in copyPeakList
> File "C:\Program Files (x86)\CCPN\python\ccpnmr\analysis\core\PeakBasic.py", l
> ine 1627, in pickPeak
> File "C:\Program Files (x86)\CCPN\python\ccp\api\nmr\Nmr.py", line 59765, in n
> ewPeak
> File "C:\Program Files (x86)\CCPN\python\ccp\api\nmr\Nmr.py", line 45936, in _
> _init__
> File "C:\Program Files (x86)\CCPN\python\ccpnmr\analysis\Analysis.py", line 76
> 3, in setupCPeak
> File "C:\Program Files (x86)\CCPN\python\ccpnmr\analysis\Analysis.py", line 72
> 5, in setCPeakNumAliasing
> error: num_aliasing must be int list or tuple of size 0
> Drawing real canvas WinPeakList error: xdim must be >= 0 and < 0
> Drawing real canvas WinPeakList error: xdim must be >= 0 and < 0
>
>
> I am now running Analysis 2.1.5 on Windows 7 64 bit.
>
> Many thanks
>
> David
>
>
> -----Original Message-----
> From: CcpNmr software mailing list [mailto:[log in to unmask]] On Behalf Of David Yadin
> Sent: 19 July 2010 20:14
> To: [log in to unmask]
> Subject: Re: Error displaying 3D spectrum and problem with Format Converter export of CNS restraint files
>
> Hi Dan
>
> Thanks very much for your reply. Yes, this has happened multiple times with more than one spectrum. The effect appears to be reversible if I delete the new spectrum.
>
> I have had other problems before with contours becoming permanently invisible for one spectrum in a window. I was able to get around this by opening the spectrum again under a different name and copying the peaks across. Unfortunately this didn't give an error message in the terminal window so I didn't report it.
>
> Best wishes
>
> David
>
>
>
> -----Original Message-----
> From: CcpNmr software mailing list [mailto:[log in to unmask]] On Behalf Of Daniel O'Donovan
> Sent: 19 July 2010 11:55
> To: [log in to unmask]
> Subject: Re: Error displaying 3D spectrum and problem with Format Converter export of CNS restraint files
>
> Hi David,
>
>> error: first must be float list or tuple of size 0
>> Drawing real canvas WinPeakList error: xdim must be >= 0 and < 0
>
>
> Ouch - that sounds like some pretty odd logic! This error has been auto-generated from inside the code so don't worry, we (developers) wouldn't actually write 'if x >= 0 and x < 0' !
>
> We think that something must have gone wrong earlier in the program and triggered this (I haven't tested this on Windows 7 64-bit as we don't have such a machine yet!). It would be good to know if this is
>
> 1) reproducible and
> 2) if your project is still usable after quitting and restarting analysis.
>
> Hopefully we will have a fix for you soon.
>
> I think Wim will be best placed to fix your other problem, I'll leave that for him (I see he has just sent an email).
>
> Thanks,
>
> Dan
>
> Daniel O'Donovan
> [log in to unmask]
Daniel O'Donovan
[log in to unmask]
|