Project

General

Profile

Actions

Bug #1535

open

danger in losing recon volume result from failed reconupload

Added by Anchi Cheng almost 13 years ago. Updated over 11 years ago.

Status:
Assigned
Priority:
Normal
Category:
-
Target version:
-
Start date:
01/23/2012
Due date:
% Done:

0%

Estimated time:
Affected Version:
Appion/Leginon 2.2.0
Show in known bugs:
No
Workaround:

Description

When uploadEMANRefine.py is run and failed in the middle of the run, reruning it would not work giving the following error because EMAN_result directory is removed and recreated at the beginning of the script while threed.1a.mrc in recon directory has been replaces as a link to the now non-existing volume in the new EMAN_result.

Dmitry, please at least give your thought on what you'd like it to do even if you can't work on it now.

Traceback (most recent call last):
  File "/usr/bin/uploadEMANRefine.py", line 605, in <module>
    upload3D.start()
  File "/usr/bin/uploadEMANRefine.py", line 592, in start
    self.createChimeraVolumeSnapshot(newvol, iteration)
  File "/usr/lib/python2.6/site-packages/appionlib/reconUploader.py", line 589, in createChimeraVolumeSnapshot
    sym='c1', mass=self.params['mass'])    
  File "/usr/lib/python2.6/site-packages/appionlib/apChimera.py", line 89, in filterAndChimera
    apDisplay.printError("Volume file is not valid")
  File "/usr/lib/python2.6/site-packages/appionlib/apDisplay.py", line 57, in printError
    raise Exception, colorString("\n *** FATAL ERROR ***\n"+text+"\n\a","red")
Exception: 
 *** FATAL ERROR ***
Volume file is not valid

Actions

Also available in: Atom PDF