Project

General

Profile

Actions

Bug #1461

closed

Post processing is not working anymore

Added by Arne Moeller about 13 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
11/10/2011
Due date:
% Done:

0%

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

Description

I ran a Xmipp refinement and uploaded it to the database. Postprocessing dies with this error message

... Time stamp: 11nov10i14
... Function name: postProc
... Appion directory: /opt/myamisnap/lib
... Load average is high 2.03
!!! WARNING: Using split database
Connected to database: 'ap341'
... Committing data to database
Traceback (most recent call last):
File "/opt/myamisnap/bin/postProc.py", line 309, in ?
postProc = PostProcScript()
File "/opt/myamisnap/lib/appionlib/appionScript.py", line 83, in init
self.checkConflicts()
File "/opt/myamisnap/bin/postProc.py", line 98, in checkConflicts
self.params['fscfile'] = self.getFscFile()
File "/opt/myamisnap/bin/postProc.py", line 178, in getFscFile
apDisplay.printError("failed to find fscfile: "+fscfile)
File "/opt/myamisnap/lib/appionlib/apDisplay.py", line 57, in printError
raise Exception, colorString("\n * FATAL ERROR *\n"+text+"\n\a","red")
Exception:
  • FATAL ERROR ***
    failed to find fscfile: /ami/data00/appion/11oct11d/recon/xmipp_recon24-C1/Xmipp_results/iter012/fsc.eotest.12
Actions

Also available in: Atom PDF