integration images change size from original raw sizes

That is certainly a bit strange, I don't think it should do that. You processed them entirely in APP, not touched by anything else?

yes straight fit files from the the camera (AA 183M).
just double checked the original dta fit files are all 5440 x 3648
which is the resolution size for that camera..

David

Also for this issue I will have to tag our programmer, @bula-admin . 🙂 Never heard the issue before though.

Hi David and Vincent @prioryart @vincent-mod

This is not strange, this is due to the full composition mode in 6) Integrate.

Most applications, by default use the reference composition mode.

In 6) integrate, the full composition mode will have the effect that all integrations will contain all pixels (therefore it's called full ) of all the frames in the integration. So, unless all frames have the exact same composition on a pixel basis, integrations will be larger than the reference frame.

On the other hand, reference composition mode, will only integrate to the field of view of the reference frame which will result in integrations that have the exact same size as the reference frame. Which David is expecting here.

If you are fine with losing data at the borders of the field of view and simply have the same dimensions as the reference frame, you can use the reference composition mode.

But....., this is really not recommended.

APP has a multi-channel workflow to ensure that all data (all pixels) is used, also at the borders, and it will give you several integrations per channel/filter that are registered to each other and that will have the same image dimensions.

Please check this tutorial:

https://www.astropixelprocessor.com/fully-automatic-multi-channel-processing-in-astro-pixel-processor-by-mabula/

It’s using broadband filters, but the principle is the same. This is the best and most automated workflow for your cause  😉

Please let us know if you need more assistance.

Kind regards,

Mabula