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.
Hi Mabula,
Apologies for coming back with another issue quite so soon but I am seeing some odd results when I view 3 of the 19 iTelescope M1 RAW subs that I uploaded to you server just recently!Â
As you can see from the below screen shots of 2 x OIII and 2 x Ha frames, all the images look very similar when viewed in Linear mode but of the total set of 19, 3 look radically different in l-Calibrated mode. I thought at first that this might somehow be related to the 'flip' state setting you mentioned in my previous posting but this does not seem to be the case.
Is this just a glitch with the viewer or will miscalibration feed through into the integrated stacks?
Four l-calibrated screenshots - two good, two suspect
Four linear image screenshots - all look quite similar
Regards
Â
Mike
That is very odd, almost like someone put the lights on or something. I've seen that happen at iTelescope in Spain once. 🙂 Anyway, in this case it's the calibration it seems but is very likely due to the data itself. Somehow these frames are different, it would be great if you could upload them to our server. Login/password: appuser and create a folder with your name+"iTelescopeCalIssue".
Thanks in advance!
Hi Vincent,
Files uploaded as requested:
- 19 Lights
- Master Bias, Master Dark and 2 x MasterFlats
- BPM and 2 x MFs created by APP
Regards
Mike
Â
Thanks Mike! Either me or Mabula will check it out soon.
Hi Mabula,
I've just downloaded v1.078 to see if this problem I reported recently while experimenting in 1.077 with some iTelescope RAW image files of Crab nebula had been resolved.   I guess the earlier report has been overlooked or regarded as a low priority, which I hasten to say is not an issue for me.
You will probably also recall this target from dealing with this earlier problem which occurred while processing the corresponding iTelescope Calibrated files:
Anyway, I observe that 3 of the 19 RAW image files show this issue all show FLIPSTAT= 'Flip ' in the FITS header whereas the remainder all show FLIPSTAT= '   ' .  This seems a likely pointer to the trigger for the problem!
I believe I already loaded the file set for this issue to your server but can reload if needed.
Regards
Mike
Â
Â
Dear Mike @mestutters,
Your problem is a MaximDL problem really. You will need to report this data problem to iTelescope.net I think. Something was not done correctly due to that FLIPSTAT header tag of MaximDL.
APP can handle the flipstat tag of MaximDL, but in this case something odd happened at iTelescope I think.
You could apply the flip yourself with the Batch Rotate tool on the problematic frames I think though...
Mabula
