-
Notifications
You must be signed in to change notification settings - Fork 3
/
readme.txt
67 lines (53 loc) · 2.83 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
How to use the scripts
======================
To perform two-colour or multi-colour registration using these scripts,
use the script getTransform.m to get the transforms, move the transform
to the folder where you keep the localization files that need to registered
and use the function useTransform.m.
The registered localization files can again be imported into ThunderSTORM
to do additional post-processing if necessary.
getTransform.m
==============
This script uses the localisation files from a series of bead images to
calculate a transform that can be used to register multi-colour images.
In order for the code to work, you have to follow a specific naming
convention. For example, for 3-col registrations, the names of the
localization files in the directory you specify should be:
a1_488.csv
a1_561.csv
a1_647.csv
One channel is chosen to be the reference channel, so in the example above,
if 647 is the reference channel, you would get 2 transform as output:
Trafo_tform_488.mat
Trafo_tform_561.mat
If you acquired many bead images and want to do batch registration, you can
put all the bead images in one folder:
a1_488.csv, a2_488.csv, a3_488.csv,
a1_561.csv, a2_561.csv, a3_561.csv, etc.
a1_647.csv, a2_647.csv, a3_647.csv,
and calculate all the transforms in batch. A summary of the transform
parameters will in that case also be written away as a csv table.
Plots the raw optical offset between the associated coordinates in the two
bead channels and also the transform used to register the coordinates as a
vector field within the field of view of the system.
useTransform.m
==============
This script registers localisation files from multi-colour single molecule
localisation experiments. The script reads the localisation files and uses
a the transform from getTransform.m to register its coordinates to the
images of a reference channel.
In order for the code to work, you have to follow a specific naming
convention, and put the transform in the same folder as your images that
need to be transformed. The naming convention for the localization files
for 3-col registration would be:
a1_488.csv, a2_488.csv, a3_488.csv,
a1_561.csv, a2_561.csv, a3_561.csv, etc.
a1_647.csv, a2_647.csv, a3_647.csv,
The names of the transforms should then be something like this:
Trafo_tform_488.mat
Trafo_tform_561.mat
if 647 is your reference channel. The 'Trafo_tform' in the transform
filename can be any string. Only the '_488.mat' and '_561.mat' are
important for the script to know which transform to use on which data.
You can register all localization files in a folder using a transform,
or chose to register only one.