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.
Hello There!
Can anyone explain it to me why is my Ha image is 3 pixels smaller than the rest of the images (SII and OIII)?
The subs are the same and I'm trying to make a Hubble palette image from my OSC data.
The 3 algorithms I used was "Ha-OIII extract Ha", "Ha-OIII extract OIII" and "Ha-OIII mono" and the one I made with the "Ha-OIII extract Ha" turned out to be 3 pixels shorter in the Y dimension than the rest and now I cannot combine it to RGB image, because it says the dimensions are not the same.
I'm using the 2.0.0-beta14 version of APP.
Edit: Same result with beta19.
Edit2:
When I crop the images in APP to match the dimensions then I get the following error message when I press the calculate button in the combine RGB menu:
When I close APP then open it up again and the only menu I'm using is the combine RGB then when I select az image to add, the channel assign window pops up 3 times at every image. There's clearly something I'm doing wrong or something is wrong. 🙂
Please, help!
Thank you!
Hi @rapid,
This problem occurs because you probably registered the stacks indepently from each other.
You need to register the "Ha-OIII extract Ha", "Ha-OIII extract OIII" and "Ha-OIII mono" results first. Then they will have the same dimensions. The difference in image dimensions are caused by the full composition mode in 6) integrate where it will create a field of view for the stack so no data is lost.
Even if the stacks had the same resolution, they would not be registered yet to each other as well.
So load the 3 stacks as lights, and register them in 4) Register, then save registered lights at the bottom in menu 4). Those saved registered lights are competely compatibel for a composite now 😉
If you add an image to RGB combine and the channel assing window pops up 3x, you are loading a color image which has 3 channels and you need to assign all 3 channels then.
Mabula
Thank you!
Now the combine RGB went flawlessly with the registered FITS.
Yes, it seems the cropped FITS was saved in RGB with APP, but the registered files are mono now.
I love your program! It's the most user friendly software out there with tremendous knowledge and functions packed inside.
Keep up the good work!
Hi @rapid,
The above issues will all be fixed in the next 2.0.0-beta25 release 😉
I will try to release it soon !
Mabula
Hi all,
Please try 2.0.0-beta25 which has been released with the fix for this issue.
https://www.astropixelprocessor.com/downloads/
Mabula
