Project

General

Profile

Actions
Copy link

Bug #657

closed

Post-processing does not work with FREALIGN jobs

Added by Neil Voss almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Amber Herold
Category:
-
Target version:
Appion/Leginon 2.0.2
Start date:
06/14/2010
Due date:
% Done:

0%

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

Description

Filename is passed wrong
fsc.eotest.## is not found

Actions
Copy link
 #1

Updated by Amber Herold almost 14 years ago

  • Target version set to Appion/Leginon 2.2.0
  • Affected Version set to Appion/Leginon 2.0.1
Actions
Copy link
 #2

Updated by Amber Herold almost 14 years ago

  • Target version changed from Appion/Leginon 2.2.0 to Appion/Leginon 2.0.2
Actions
Copy link
 #3

Updated by Neil Voss almost 14 years ago

  • Status changed from Assigned to In Code Review
  • Assignee changed from Neil Voss to Amber Herold
Fixed:
  • Filename was being uploaded incorrectly in uploadFrealign.py
  • Fixed database entries for only ap72, may be more.
  • FSC file is stored in subfolder iter###, updated postProc.py
Test:
  • Run frealign
  • Upload
  • Do postProc with b-factor
Actions
Copy link
 #4

Updated by Amber Herold almost 14 years ago

  • Status changed from In Code Review to In Test
  • Assignee changed from Amber Herold to Dmitry Lyumkis

Please test this ASAP as it is going into the Branch!

Actions
Copy link
 #5

Updated by Dmitry Lyumkis almost 14 years ago

  • Status changed from In Test to Merge
  • Assignee changed from Dmitry Lyumkis to Amber Herold

I tested this on an EMAN reconstruction using different parameters for postprocessing. Neil said that he had already done the Frealign, but just wanted to make sure that the EMAN reconstruction wasn't broken. Everything worked with the trunk version of Appion.

Actions
Copy link
 #6

Updated by Amber Herold almost 14 years ago

  • Assignee changed from Amber Herold to Neil Voss

Neil, can you or Dmitry test this merge to 2.0, preferably on Cronus3 tomorrow?
Seems a bit like overkill testing wise, but also seems foolish not to.

Actions
Copy link
 #7

Updated by Neil Voss almost 14 years ago

  • Status changed from Merge to In Test
  • Assignee deleted (Neil Voss)

This modifies python so cronus3 is unaffected. We need to wait for guppy to be updated.

Actions
Copy link
 #8

Updated by Amber Herold over 13 years ago

  • Assignee set to Amber Herold
  • Show in known bugs set to No
Actions
Copy link
 #9

Updated by Amber Herold over 13 years ago

  • Status changed from In Test to Closed
Actions
Copy link

Also available in: Atom PDF