Using the extension .mrcs instead of .mrc
Added by Patrick Goetz about 6 years ago
Hi -
The local users would like movies to be named .mrcs instead of .mrc, as they suggest this is becoming the industry standard convention. Presumably this is something that would be changed in rawtransfer.py?
Replies (2)
RE: Using the extension .mrcs instead of .mrc - Added by Anchi Cheng about 6 years ago
There is no industry standard for naming image stack as mrcs. According MRC2014 standard, image stack is identified in the file header with mz larger than 1 and nz=1, not by file extension name.
File extension is only used by generic program to decide on how to read the header. If you want to change rawtransfer.py to satify local user requirement, please do so yourself. It will break motion correction Appion processing because Appion expects it to be the generic mrc extension. I was involved in that standardization and will not want to be the one breaking it.
One possible way to get around it is to add a soft link for it in rawtransfer.py
RE: Using the extension .mrcs instead of .mrc - Added by Patrick Goetz about 6 years ago
One of the PIs sent me this from the relion documentation:
"RELION writes individual images and image stacks in MRC format. Because there is no distinction between 3D maps or stacks of 2D images in the MRC format, 3D maps are indicated with a .mrc extension, and stacks with a .mrcs extension."
I'll try find out what the use case is and will figure out what to do from there. Renaming the files is not an option, as this will break Appion. It would need to be done before the information in recorded in the database.