BatchPreprocessing not doing *only* registeration/integration

[pbkwee]

Hi.  I load up the preprocessing dialog with a selection of different binning and filtered lights.  No darks/flats/biases/etc. 

When I select run it warns about the lack of flats, etc.  That's fine.

Then errors out with:
Reason: No master calibration frames or overscan regions have been specified.

It would be useful if the batchpreprocessing tool supported the registration and/or integration of lights (without also requiring calibration).

[Juan Conejero]

Hi,

Calibration is not an optional step in the BatchPreprocessing script, so this error is the expected behavior when no calibration frames have been selected

It would be useful if the batchpreprocessing tool supported the registration and/or integration of lights (without also requiring calibration).

The StarAlignment tool already allows you to select a set of disk files for registration. Unless you have to tweak some StarAlignment parameters (which is rare, and if that happens then BatchPreprocessing isn't useful either), it's a matter of selecting the images, select an output folder, and pressing F6, so I can't see any advantage in doing this through a script.

Image integration is a critical task that requires manual fine tuning and some trial-error work to achieve the best possible image from a data set. This cannot be done with the BatchPreprocessing script. The integrated result of this script should never be used as the starting point of a production image. It is just a convenience preview.

[pbkwee]

I am using filters.  So the batch preprocessing method would save me up to 5 x align processes.  And then up to 5 x stacking processes.  Or even more if I had been taking different exposure lengths on each filter.  The whole process I need to be at the PC since each step requires manual intervention.

If it were easy/possible to do align and combine (and not calibrate) then I think this would save me a bit of time.  I can just load the images, hit a button, then walk away and do whatever while the batchpreprocessing does its thing. 

And it doesn't necessarily seem that wrong/hard to do in the batchpreprocessing dialog.

[pbkwee]

Actually, yeah, alignment is only one process.  And I see your point re the fine tuning of stacking.  So, yeah, hmmm.

It still seems to me that it would be 'nice' if the batchpreprocessing didn't have calibration as a mandatory step.