How does Leginon Name the Files » History » Version 1
Amber Herold, 04/23/2010 08:54 AM
1 | 1 | Amber Herold | h1. How does Leginon Name the Files |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | Leginon image files are typically named |
||
6 | 09mar16a_atlas1_00005gr_00003sq_00001hl_v1_00002en.mrc |
||
7 | |||
8 | |||
9 | This name includes |
||
10 | * sessionname: 09mar16a |
||
11 | |||
12 | |||
13 | * grid atlas label: atlas1 |
||
14 | |||
15 | |||
16 | * target number in the target list: 00005; 00003; 00001; 00002 |
||
17 | |||
18 | |||
19 | * presetname with which the image is aquired: gr; sq; hl; en |
||
20 | |||
21 | |||
22 | * target version: v1 |
||
23 | |||
24 | |||
25 | |||
26 | |||
27 | |||
28 | Since Leginon always defines target on an image, and an image is acquired at the |
||
29 | location of the target offsets from the parent image of the target, a family tree is |
||
30 | estabilished. The filename therefore carries this family tree of the multi-scaled imaging. |
||
31 | * Grid atlas label is always unique in the session. When robotic grid |
||
32 | insertion/extration or Grid Entry node class is used for large-scale |
||
33 | screening, the atlas label is replaced by the grid label, unique within the |
||
34 | project, and the insertion number. |
||
35 | |||
36 | |||
37 | * Each target in the target list an Acquisition node class or subclass |
||
38 | receives has a unique number. Ocassionally a target in the list is out of |
||
39 | range of the goniometer or is aborted for various reasons before acquired. |
||
40 | The filename will therefore skip the number. |
||
41 | |||
42 | |||
43 | * When drift is declared, a new version of the target is obtained through |
||
44 | the node of TransformManager class, therefore the image acquired using that |
||
45 | target carries the version number to distinguish it from the |
||
46 | original. |