Adding MRC header information into the exported files

[mgiammar]

Currently, no additional header information is being written to the output MRC files from template matching, namely the voxel size. The mrcfile package allows these metadata to be modified, and this should be implemented to increase interoperability with other packages using MRC metadata.

Some items to address:

• What if user pixel size in the OpticsGroup is different from the MRC voxel size attribute?
• What if there is a voxel size mismatch between the volumetric template MRC and the micrograph?
• How should metadata from an input MRC file be passed onto an output (e.g. should this happen before or after the core template matching call).
• Incorporating tests and fallbacks in case metadata cannot be read.

[jdickerson95]

Some thoughts on these:

1. User pixel size in the optics group should be used instead of MRC voxel size attribute, but there should be a warning.
2. If the template is a different voxel size, there should also be a warning. The user-defined pixel size should be used first. Micrograph pixel size should override template voxel size since this should be the real pixel size (the template pixel size can compensate for errors in the pdb model).
3. After core call.
4. Should always be: user-defined value > metadata > error