You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rejection sampling. Integrative postprocessing. XML/Star support for ctf / tilt specification in match_template. GPL license. Streamlined analyzer and composable filters.
Copy file name to clipboardExpand all lines: doc/quickstart/installation.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Installation
5
5
6
6
.. _installation-section:
7
7
8
-
This section provides instructions on how to install |project|. We recommend creating an installation enviroment for a clean and isolated setup. Available options for different use cases are outlined in the tabs below.
8
+
We recommend creating a virtual environment for a clean and isolated setup.
Copy file name to clipboardExpand all lines: doc/quickstart/matching/cluster.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,11 @@ The following subsections provide templates for the execution of |project| on di
10
10
11
11
.. note::
12
12
13
-
The ``estimate_ram_usage.py`` script computes an initial memory estimate on a given template matching case for clusters that require memory reservations.
13
+
The ``estimate_memory_usage.py`` script computes an initial memory estimate on a given template matching case for clusters that require memory reservations.
Copy file name to clipboardExpand all lines: doc/quickstart/postprocessing/motivation.rst
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
Motivation
5
5
==========
6
6
7
-
Postprocessing identifies regions of high similarity from the template matching output, which we refer to as peaks. Each peak corresponds to an occurence of the template in the target, which is fully characterized by a translation and rotation vector. Identifying peaks is challenging by itself, hence |project| implements a variety of analysis strategies for optimal performance.
7
+
Postprocessing identifies regions of high similarity from the template matching output, which we refer to as peaks. Each peak corresponds to an occurence of the template in the target, which is fully characterized by a translation and rotation matrix. Identifying peaks is challenging by itself, hence |project| implements a variety of analysis strategies for optimal performance.
8
8
9
9
10
10
Background
@@ -18,14 +18,14 @@ Lets recall an example from the preprocessing section. The highest peak is locat
Copy file name to clipboardExpand all lines: doc/quickstart/postprocessing/summary.rst
+31-23Lines changed: 31 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,41 +4,31 @@
4
4
Summary
5
5
=======
6
6
7
-
The ``postprocess.py`` command-line tool can be used to analyze the results generated by ``match_template.py``.
7
+
The ``postprocess.py`` tool analyzes results generated by ``match_template.py`` to identify and characterize top-scoring peaks from template matching.
8
8
9
9
.. code-block:: bash
10
10
11
11
postprocess.py --help
12
12
13
-
Top-scoring peaks can be identified using
13
+
.. tip::
14
14
15
-
.. code-block:: bash
16
-
17
-
postprocess.py \
18
-
--input_file output.pickle \
19
-
--output_prefix output \
20
-
--output_format orientations \
21
-
--min_distance 30 \
22
-
--min_boundary_distance 20 \
23
-
--num_peaks 1000
24
-
25
-
Identifying no more than 1,000 top-scoring peaks that are separated by at least 20 voxel from each other and 30 voxel from the boundaries. Different peak calling strategies can be chosen from using the ``--peak_caller`` argument.
15
+
From version 0.3.0 onwards, postprocessing supports advanced multi-input and background correction. Multiple input files can be specified to distinguish between different macromolecular species, with corresponding class identifiers made available in orientations and RELION output formats. Additionally, multiple background corrections can be applied simultaneously via ``--background_file``, enabling users to account for various noise sources beyond single backgrounds (e.g., from ``--scramble_phases``) and incorporate complex cellular environments such as membrane backgrounds.
26
16
27
17
Depending on the subequent use case, different ``output_format`` options are available and outlined below.
28
18
29
19
.. tab-set::
30
20
31
21
.. tab-item:: Orientations
32
22
33
-
A tab-separated file *output.tsv* will be created in the process containing eight columns. The z, y and x column correspond to the translation, the euler_z, euler_y and euler_x column to the rotation used to obtain the column score. The detail column contains peak caller specific information.
23
+
A tab-separated file *output.tsv* will be created in the process containing eight columns. The x, y and z column correspond to the translation, the euler_x, euler_y and euler_z column to the rotation used to obtain the column score. The detail column contains peak caller specific information.
34
24
35
25
.. code-block:: bash
36
26
37
27
postprocess.py \
38
28
--input_file output.pickle \
39
29
--output_prefix output \
40
30
--output_format orientations \
41
-
--min_distance 30 \
31
+
--mask_edges \
42
32
--min_boundary_distance 20 \
43
33
--num_peaks 1000
44
34
@@ -52,7 +42,8 @@ Depending on the subequent use case, different ``output_format`` options are ava
52
42
--input_file output.pickle \
53
43
--output_prefix output \
54
44
--output_format relion4 \
55
-
--min_distance 20 \
45
+
--mask_edges \
46
+
--min_boundary_distance 20 \
56
47
--num_peaks 1000
57
48
58
49
@@ -66,6 +57,8 @@ Depending on the subequent use case, different ``output_format`` options are ava
66
57
--input_file output.pickle \
67
58
--output_prefix output \
68
59
--output_format alignment \
60
+
--mask_edges \
61
+
--min_boundary_distance 20 \
69
62
--num_peaks 10
70
63
71
64
.. tab-item:: Extraction
@@ -78,9 +71,9 @@ Depending on the subequent use case, different ``output_format`` options are ava
78
71
--input_file output.pickle \
79
72
--output_prefix output \
80
73
--output_format extraction \
81
-
--min_distance 20 \
82
-
--num_peaks 500 \
83
-
--peak_caller PeakCallerMaximumFilter
74
+
--mask_edges \
75
+
--min_boundary_distance 20 \
76
+
--num_peaks 100
84
77
85
78
.. tab-item:: Average
86
79
@@ -92,13 +85,28 @@ Depending on the subequent use case, different ``output_format`` options are ava
92
85
--input_file output.pickle \
93
86
--output_prefix average \
94
87
--output_format average \
95
-
--min_distance 20 \
96
-
--num_peaks 500 \
97
-
--peak_caller PeakCallerMaximumFilter
88
+
--mask_edges \
89
+
--min_boundary_distance 20 \
90
+
--num_peaks 100
91
+
92
+
93
+
.. tab-item:: Pickle
94
+
95
+
The code below will apply background correction, and create a new pickle file containing the corrected scores. The output is intended for visual assessment of the normalization procedure, and can be reused for postprocessing.
Orientations are following the conventions outlined in [1]_. We use a right-handed coordinate system with orthogonal X, Y and Z axes. Euler angles are expressed using intrinsic ZYZ convention, with the first rotation around the Z-axis, the second around the new Y-axis and the third around the new Z-axis (see :py:meth:`euler_to_rotationmatrix <tme.rotations.euler_to_rotationmatrix>`). The default orientation the z-unit vector (0, 0, 1).
107
+
Orientations are following the conventions outlined in [1]_. We use a right-handed coordinate system with orthogonal X, Y and Z axes. Euler angles are expressed using intrinsic ZYZ convention, with the first rotation around the Z-axis, the second around the new Y-axis and the third around the new Z-axis (see :py:meth:`euler_to_rotationmatrix <tme.rotations.euler_to_rotationmatrix>`). The default orientation is the z-unit vector (0, 0, 1).
0 commit comments