Difference between revisions of "Binning tomograms"
(Created page with "Tomograms can be binned in different ways from the command line. == Loading the full tomogram into memory== This is the simplest approach: read the full tomogram file into...") |
|||
Line 19: | Line 19: | ||
== Creating chunks == | == Creating chunks == | ||
+ | |||
+ | An alternative way is to create several chunks that are read, binned and stored independently. The final (binned) volume is integrated after the different chunks have been processed separately. This happens transparently for the users. | ||
+ | |||
+ | An example of use is: | ||
+ | |||
+ | <tt>o = dpktomo.partition.bin(myFile.mrc,1,'of','binned.em','slabSize',100);</tt> |
Revision as of 17:13, 19 May 2016
Tomograms can be binned in different ways from the command line.
Loading the full tomogram into memory
This is the simplest approach: read the full tomogram file into memory, bin it, and write the result onto a file. This is useful for small tomograms, or when working in machines with large memory, but it will probably not work when the tomogram is too big to fit into your memory.
For instance the order:
dread myVolume.mrc a
reads the file myVolume.mrc into the variable a. For a volume (), it takes 6 minutes on a MacBookPro (i5), during which the computer is close to frozen.
After reading the full tomogram, you still need to bin it. You can do it with the command dbin
b=dbin(a,2);
... which will also take some time to comlplete.
Creating chunks
An alternative way is to create several chunks that are read, binned and stored independently. The final (binned) volume is integrated after the different chunks have been processed separately. This happens transparently for the users.
An example of use is:
o = dpktomo.partition.bin(myFile.mrc,1,'of','binned.em','slabSize',100);