UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
At times I use 2 different scopes and cameras on the same target. I saw mention of reference crop but I need clarification.
Is it possible at any point prior to Integration to crop the images to the desired final size (specifically to the frame size from the camera/scope with the smaller field of view?
Thanks as always.
Andy
@andynowlen Andy,
There are three possible final frame sizes possible: full, reference and crop. When you choose reference, the size of the reference frame will be used for the final crop but it will also match the field of view of the reference frame. If you apply dithering then it is likely that the area of the reference frame will be different than the final area that all images of the smaller camera contribute to. This means that areas of the sky will be included where not all images contribute to.
Why would you want the integration result to be cropped for you?
I notice that in the final "all session" stack the smaller field of view is always noticeable. Whether it is darker or lighter.
Usually, I have to then crop to the smallest field of view - which I knew I would have to do at any rate.
As a test, I tried a project with three different fields of view. APP dimensions the stack according to the widest field of view. Then if I crop to the narrowest field of view the cropped image is very small.
I.E. final three scope stack dimensions = 5100x3600 for instance. Dimensions are fictitious for illustration only
Cropped to the smallest field of view = 2300 x 1700 for instance. Dimensions are fictitious for illustration only
Normally my smallest field of view is 3,000 x 3,000. (Asi533MCpro). So, it seems some resolution and detail might be lost if I am always cropping to the smallest field of view in the end. But I am a total amateur.
This led me to ask the original question.
As always, Thanks much!
Andy
@andynowlen Thanks for the explanation. Have you tried integrating the data of the two telescopes in two separate sessions or completely separately, removing light pollution from them and then integrating them? To do the latter, load them as lights (don't load calibration data), go to tab 6 and click integrate. That may take care of the difference in background brightness between the two of them.
