Project

General

Profile

Actions

Bug #496

open

Why does alignSubStack.py need include/exclude class list?

Added by Anchi Cheng almost 14 years ago. Updated almost 14 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
-
Start date:
05/17/2010
Due date:
% Done:

0%

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

Description

It makes no sense to me. Particle alignment does not put particles into classes. Why does the script and its webpage insist on inputting at least one of the two?

Actions #1

Updated by Anchi Cheng almost 14 years ago

Also, even with clustered particles, if I select all classes, it won't let me create a substack. viewstack.php button for creating substack does not function in this case. Why not? I want to use the linked substack with the alignment information for subtomogram averaging.

Actions #2

Updated by Neil Voss almost 14 years ago

  • Status changed from New to Assigned

Particle alignment DOES put particles into classes. Without defining a exclude or include list you are including ALL particles which not really a substack. The max shift and max score/spread function were added later.

If max shift and max score/spread are not defined then exclude and include are not required. Otherwise they have to be there. We will need to check both the python and php code for this.

Actions #3

Updated by Neil Voss almost 14 years ago

  • Target version set to Appion/Leginon 2.0.0
Actions #4

Updated by Anchi Cheng almost 14 years ago

O.K., I will use all particles to generate the reference classes and then use them as fake include classes to make my special substack, then. How about just fix the deactivated button in stackviewer to allow selection of all classes?

Actions #5

Updated by Amber Herold almost 14 years ago

  • Target version changed from Appion/Leginon 2.0.0 to Appion/Leginon 2.0.1
Actions #6

Updated by Amber Herold almost 14 years ago

  • Target version changed from Appion/Leginon 2.0.1 to Appion/Leginon 2.0.2
  • Affected Version set to Myami 2.0.1
Actions #7

Updated by Amber Herold almost 14 years ago

  • Target version changed from Appion/Leginon 2.0.2 to Appion/Leginon 2.1.0
Actions #8

Updated by Amber Herold almost 14 years ago

  • Target version changed from Appion/Leginon 2.1.0 to Appion/Leginon Future Version
  • Affected Version changed from Myami 2.0.1 to Appion/Leginon 2.0.1
  • Show in known bugs set to No
Actions

Also available in: Atom PDF