Closed HaoyangRong closed 7 years ago
They aren't useful anymore; they are relics of an old Andor CCD camera. We could expunge them from the header written by Imagine. CC @kdw503.
If someone can post a "modern" .imagine file one of us can add a fix for ImagineFormat.
This means we don't need these two fields in the .imagine header file anymore, right? I will remove the lines in the Imagine code.
Yes, I think they can safely be removed. Our CMOS cameras actually do have a readout rate, but this isn't really useful information--people will only use the exposure time. I've opened an issue in the Imagine repo.
The new version of ImagineFormat has been made the default in METADATA, and site packages have been updated on cannon. It doesn't seem that ImagineFormat was installed previously, so either delete your own copy or make sure you update your packages.
I'm reporting an bug with
ImagineFormat.save_header(string(basename, ".imagine"), fn, img, Float32)
during the warping phase and offering a temporary fix. The error message is as follows:Basically, this function tries to read information from the original
.imagine
file and writes the new.imagine
file for the newly created, warped image. If we dig into the source files:When these two functions are called to create a dictionary in
ImagineFormat.jl
, theround()
function complains. If we look back to the original.imagine
file, it seems the Imagine on neither OCPI1 or 2 writes anything followingvertical shift speed=
andreadout rate=
. So a quick fix is to add some number you make up along with the corresponding unit (in the original.imagine
file), such asvertical shift speed= 1 us
andreadout rate= 0 MHz
.I'm not sure if these two fields could affect downstream data processing. If they are no longer useful, maybe they can be removed from the function for saving Imagine header. Or we can allow flexible reading and writing in that function.