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.
I am new to both iTelescope and to APP. My first imaging session with iTelescope was using T18 on M81. Some of the calibrated files I received automatically from iTelescope appeared to be damaged when loaded them into APP. The 'damaged' ones where always images taken when the scope did a meridian flip. The images from the East side appeared fine, while the images from the West side appeared damaged. Below are some screen shots: Â
This is an image using red filter from the east side. Looks good.
This next image is from the same session using the same filter from the W side. Looks damaged with no data in the histogram.
Thinking that this was a problem with iTelescope, I contacted their support, and they sent me a screen shot of the rendering of the same image on their computer, which follows, and looks fine.
Clearly there is something strange going on on my end. This strange behavior happens with all W images. I had a session on T24 and the same thing is happening. The W images are all green.
Can anyone help me? I can upload the files if needed.
Thanks.
Thanks Wouter, however Mladen Dugec from iTelescope checked the image and he said the issue was with APP and not with iTelescope. Any chance you can take a look into this? I can upload the two files. Thanks.
Hi Sikander @alexdaryan,
Thank you very much for reporting this. I am aware of the issue and it will be fixed in the next APP release. The issue is in the iTelescope FITS header where maximDL is doing something that is not standard which confuses APP at the moment.
In some frames a BAYERPAT tag will be provided allthough it is no Bayer data at all.
There is an easy work around at the moment so you can still properly process your iTelescope data.
in menu 0) RAW/FITS on the left side, set the Bayer / X-Trans algortihm to no interpolation and all should be okay 😉
Mabula
Â
Thank you so much Mabula! That worked. I am glad that you are aware of the issue and that there will be a fix in the next release. I am enjoying both iTelescope and APP! I will let Mladen over at iTelescope know about this. Thanks again.
