I just processed the same files I did 3 days ago and they had worked very good on 1.78 but on 1.79 the AutoRGB is almost 100% monochrome. I have tried it several ways all with the same results. I have had a few other strange things like the Autointegrate window suddenly got larger than the PI window and I could not get to the buttons on the bottom to load Lights, Bias, etc.
Is there a way to go back to 1.78 for a while?
Hi,
Hmm, that sounds bad. I did run my test set with the version and it worked ok. Also I believe I have not changed any processing since 1.78.
I really would like to take a quick look and try to understand what goes wrong in your case. Would it be possible for you to send me the AutoIntegrate.log file? I would like to take a look and see if I can see anything, like a way to reproduce the problem. AutoIntegrate.log file is written to the AutoProcessed directory.
Sometimes with tab changes it is possible that too many sections are open in the same tab and the dialog gets too big. So could you close some sections in tabs and see if it helps? At the top right corner there is also a button that collapses all sections.
I can create a repository for an older version. Too bad that I did not save the old repository information, so I need to recreate those and it takes some time. As a temporarty solution, you can also download the old version from GitHub and just overwrite the files in the PixInsight scripts directory.
Regards,
Jarmo
Hi Jarmo,
I deleted the file, but will re run autointegrate and send you the file.
Gary
It will not let me attach the Autointegrate.txt file. How do I send it to you??
The jpg file attached has the stars with normal color but the Shrimp Nebula is gone.
The second jpg is that from the first run of Autoexecute script before the update. This was post processed and has the colors more saturated and is cropped but as you can see, the nebula is colored and as clear as I could get with 8 hours and near full moon.
Sorry, I forgot the add the email. You can use this email address: info@astroimagetools.net
I wonder if it could be different stretching used. I actually changed the target types from [ ‘Default’, ‘Galaxy’, ‘Nebula’ ] to [ ‘Default’, ‘Galaxy’, ‘Small bright nebula’, ‘Large nebula’, ‘Star cluster’ ]. I wonder if a non-listed type would pick a wrong sterching. I kind of forgot to check that it does not cause problems.
Regards.
Jarmo
This problem seem to related to the new target list selection. The new list is ‘Default’, ‘Galaxy’, ‘Small bright nebula’, ‘Large nebula’ and ‘Star cluster’. The problem is that ‘Small bright nebula’ selection was processed with Masked stretch which was an incorrect choice for many cases.
In the next version I will revert the list to ‘Default’, ‘Galaxy’, ‘Nebula’ and ‘Star cluster’. Both ‘Small bright nebula’ and ‘Large nebula’ will be mapped to ‘Nebula’. As a general rule it is always useful to try different streching options to get the best results.