Open Brow71189 opened 3 years ago
According to the docstring here: https://github.com/nion-software/nionswift-instrumentation-kit/blob/ff56ebeaa9bd6dc5fd40a8e8dc5798f8b7ea1c67/nion/instrumentation/camera_base.py#L293, cameras should be able to supply spatial calibrations explicitly in the data_element returned by "acquire_image". But the current implementation (https://github.com/nion-software/nionswift-instrumentation-kit/blob/ff56ebeaa9bd6dc5fd40a8e8dc5798f8b7ea1c67/nion/instrumentation/camera_base.py#L506) completely ignores anything coming from the camera except for a couple of pre-defined keys. Spatial calibrations are not among those keys, so they are ignored, too.
According to the docstring here: https://github.com/nion-software/nionswift-instrumentation-kit/blob/ff56ebeaa9bd6dc5fd40a8e8dc5798f8b7ea1c67/nion/instrumentation/camera_base.py#L293, cameras should be able to supply spatial calibrations explicitly in the data_element returned by "acquire_image". But the current implementation (https://github.com/nion-software/nionswift-instrumentation-kit/blob/ff56ebeaa9bd6dc5fd40a8e8dc5798f8b7ea1c67/nion/instrumentation/camera_base.py#L506) completely ignores anything coming from the camera except for a couple of pre-defined keys. Spatial calibrations are not among those keys, so they are ignored, too.