[ ] In calculate_registration_image_based, handle if the table already contains the new registration columns (I think that wouldn't work atm)
[ ] In apply_registration_to_ROI_tables, check that table overwrite works . Likely works by default (=> add overwrite=True as default, but a check with the new table writing functions for the case that it's False)
In apply_registration_to_image: No overwrite support. Actually the reverse would make sense: Some metadata that allows us to check that the task has already run on an image and thus can't run again. Goal would be to use the same for illumination correction, may be out of scope for this issue
jluethi
commented
2 months ago
calculate_registration_image_based, handle if the table already contains the new registration columns (I think that wouldn't work atm)apply_registration_to_ROI_tables, check that table overwrite works . Likely works by default (=> add overwrite=True as default, but a check with the new table writing functions for the case that it's False)In
apply_registration_to_image: No overwrite support. Actually the reverse would make sense: Some metadata that allows us to check that the task has already run on an image and thus can't run again. Goal would be to use the same for illumination correction, may be out of scope for this issue