Anomalous L channel...
 
Share:
Notifications
Clear all

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.

Anomalous L channel integration - suspect normalisation issue

3 Posts
2 Users
0 Reactions
1,082 Views
(@mestutters)
Neutron Star
Joined: 9 years ago
Posts: 175
Topic starter  

Hi,

I was processing a set of LRGB subs yesterday evening and encountered an odd result in the L channel.  R, G and B all look OK.

Screenshot 2021 04 23 07.50.23

 

While checking my input L subs I observe an issue with a few (c10-15  of 58) of them, when changing the viewer mode from 'l-c-registered' to 'l-c-r-normalised', so I suspect something is going amiss during Normalisation.

L-C-Registered:

Screenshot 2021 04 23 08.00.22

L-C-R-Normalised:

Screenshot 2021 04 23 07.59.58

I have processed c60% of the input subs previously without issue but managed to grab a few more during a recent clear night.   The calibration frame have all been used previously with other images without issue.  I ran the integration a second time with the same result.  Prior to starting this integration, I had done another target without issue and had simply cleared the previous subs and changed the working directory before starting NGC4244. 

I plan shortly to re-boot my lap-top and do a further rerun to see if the issue is still present.  



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Could you check the offset you used for the subs and the calibration data?



   
ReplyQuote
(@mestutters)
Neutron Star
Joined: 9 years ago
Posts: 175
Topic starter  

Hi Vincent,

Having rebooted and restarted APP the integration the results now look as expected. 

Screenshot 2021 04 23 10.06.05

I have no idea why it was only the L channel that had this odd result, or why it seemed to be only a small number of L subs that displayed very high contrast when switched to L-C-R-Normalised mode.

I guess there must have been some sort of initialisation or other transient issue as a result of switching targets without first restarting APP.

I have a CCD camera so offset is not something that I can set.

Regards

Mike



   
ReplyQuote
Share: