Heya,

I just had a project major crash. Not doing anything different to normal (I don't think) - sudden every window closed in an instant.

Exception in Tkinter callback
Traceback (most recent call last):
File "/Applications/ccpnmr_2.3.0/python2.6/lib/python2.6/lib-tk/Tkinter.py", line 1410, in __call__
    return self.func(*args)
File "/Applications/ccpnmr_2.3.0/ccpnmr2.3/python/ccpnmr/analysis/popups/LinkPeakLists.py", line 788, in nextTarget
    index = peaks.index(self.rootPeak)
ValueError: list.index(x): x not in list

"Always send" option
Exception in Tkinter callback
Traceback (most recent call last):
File "/Applications/ccpnmr_2.3.0/python2.6/lib/python2.6/lib-tk/Tkinter.py", line 1410, in __call__
    return self.func(*args)
File "/Applications/ccpnmr_2.3.0/ccpnmr2.3/python/ccpnmr/analysis/popups/LinkPeakLists.py", line 797, in prevTarget
    index = peaks.index(self.rootPeak)
ValueError: list.index(x): x not in list

"Always send" option
Exception in Tkinter callback
Traceback (most recent call last):
File "/Applications/ccpnmr_2.3.0/python2.6/lib/python2.6/lib-tk/Tkinter.py", line 1410, in __call__
    return self.func(*args)
File "/Applications/ccpnmr_2.3.0/ccpnmr2.3/python/ccpnmr/analysis/popups/LinkPeakLists.py", line 788, in nextTarget
    index = peaks.index(self.rootPeak)
ValueError: list.index(x): x not in list
NOTICE: Atom assignment 137Val N existed in a different shift list for a different resonance.
NOTICE: Resonance [52] has been merged with resonance [805].
X Error of failed request: BadIDChoice (invalid resource ID chosen for this connection)
Major opcode of failed request: 141 (RENDER)
Minor opcode of failed request: 4 (RenderCreatePicture)
Resource id in failed request: 0x689b66
Serial number of failed request: 29600307
Current serial number in output stream: 29601193

I was in process of using the assign from roots tool box and I think it crashed just before I clicked on the 'assign root resonances' button, but I can't be sure. The X11 (XQuartz) didn't close - just Analysis. I don't know how far back in the terminal window the critical error starts - but I remember that I was just working on residue 137Val and that shows up just before the X Error. (As a comment - how hard would it be to time stamp error reports in the console so you can easily see what is relevant to a particular problem?) I think that perhaps the Tkinter callbacks are due to me trying to click on the next Target/previous Target button in the assign root resonances window after deleting the 'current' peak so it doesn't know what the next one is, but I am not sure.

I am using an iMac running 10.6.8, with XQuartz 2.7.4, started analysis 2.3.0 with the terminal command "analysis -m 512 proj_file" - that file was closed and a new one was created (I have 20 GB ram available and memory hadn't maxed according to the os)

Arg - and it also turns out I hadn't saved yet, and therefore no backups saved either. A good few hours lost - dumb user error - no programming can fix that!!!

Cheers,
Tom