Project

General

Profile

Actions
Copy link

Bug #2595

closed

K2 frame alignment using wrong reference

Added by Saikat Chowdhury about 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Saikat Chowdhury
Category:
Image Processing
Target version:
-
Start date:
11/22/2013
Due date:
% Done:

0%

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

Description

K2 frame alignment on T3 is using the wrong reference for normalization.
The follwoing warning comes up during frame alignment:

!!! WARNING: Ref Session Path:/gpfs/group/em/leginon/tnieusma/13nov19_ref_a/rawdata
!!! WARNING: Use Norm Reference 13nov20a_20100056_03_3838x3710_norm_1
!!! WARNING: Corresponding Bright Reference 13nov20a_20100054_02_3838x3710_bright_1

Actions
Copy link
 #1

Updated by Anchi Cheng about 11 years ago

  • Assignee changed from Anchi Cheng to Sargis Dallakyan
  • Affected Version changed from Appion/Leginon 2.1.0 to Appion/Leginon 3.0.0

What made user think that this is the wrong reference?

The warning is standard. The reference session usually has different session name from the current session because reference session is used up to 60 days by the same user or whoever has write permission to it.

The bug description did not say which session, or better which image produced this suspicion.

I query the database and found the most recent session that has frame saved on tecnai3 is 13nov20a. It then make perfect sense to use norm reference calculated in the session as indicated by the prefix of the filename

Please clarify.

Actions
Copy link
 #2

Updated by Anchi Cheng about 11 years ago

  • Assignee changed from Sargis Dallakyan to Saikat Chowdhury
Actions
Copy link
 #3

Updated by Anchi Cheng about 11 years ago 

The session I am talking about is 13nov20a. 
I did hardware dark on DM and did bright using Leginon. They should be saved for that session.
My doubt was that if the frame alignment program was using these references or using from an old one. Just wanted to make sense of the warning.
Thanks and Regards,
Saikat

Should this issue be closed then?

Actions
Copy link
 #4

Updated by Anchi Cheng almost 11 years ago

  • Status changed from New to Won't Fix or Won't Do

The issue turned out to be a user-error in that the references taken during the 13nov20a was not 3838x3710. Therefore, they were not found in the query.

Actions
Copy link
 #5

Updated by Anchi Cheng almost 11 years ago

  • Status changed from Won't Fix or Won't Do to Closed
Actions
Copy link

Also available in: Atom PDF