Project

General

Profile

Actions

Bug #1536

open

reconuploader should check file needed exists before inserting apRefineiterData

Added by Anchi Cheng over 12 years ago. Updated over 10 years ago.

Status:
Assigned
Priority:
Normal
Category:
Python scripting
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

Got Error like this after rerunning a failed eman recon upload. There is a database entry in apRefineIterData with Null in refineClassAverages in the failed run and therefore unique and the iteration ended up with two entries and therefore the program attempted to calculate EulerJumps. Since missing results would be common in recon when it fails, the checking of valid file should be done as early as possible during upload to prevent problems like this.

Traceback (most recent call last):
  File "/usr/bin/uploadEMANRefine.py", line 605, in <module>
    upload3D.start()
  File "/usr/bin/uploadEMANRefine.py", line 599, in start
    self.calculateEulerJumpsAndGoodBadParticles(uploadIterations)        
  File "/usr/lib/python2.6/site-packages/appionlib/reconUploader.py", line 621, in calculateEulerJumpsAndGoodBadParticles
    eulerjump.calculateEulerJumpsForEntireRecon(reconrunid, self.runparams['stackid'])
  File "/usr/lib/python2.6/site-packages/appionlib/apEulerJump.py", line 59, in calculateEulerJumpsForEntireRecon
    jumpdata = self.getEulerJumpData(reconrunid, stackpartid=stackpart.dbid, stackid=stackid, sym=sym)
  File "/usr/lib/python2.6/site-packages/appionlib/apEulerJump.py", line 107, in getEulerJumpData
    jumpdata = self.calculateJumpData(stackpartid, reconrunid=reconrunid, sym=sym)
  File "/usr/lib/python2.6/site-packages/appionlib/apEulerJump.py", line 214, in calculateJumpData
    jumpdata['min'] = distarray.min()
ValueError: zero-size array to ufunc.reduce without identity

Actions #1

Updated by Amber Herold about 12 years ago

  • Target version changed from Appion/Leginon 2.2.0 to Appion/Leginon 3.0.0

This sounds like a really annoying bug...I'm going to move it to 3.0, but lets merge a fix into the 2.2 branch soon.

Actions #2

Updated by Amber Herold over 10 years ago

  • Target version changed from Appion/Leginon 3.0.0 to Appion/Leginon Future Version
  • Affected Version changed from Appion/Leginon 2.2.0 (trunk) to Appion/Leginon 2.2.0
Actions

Also available in: Atom PDF