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
I have uploaded my data on "upload1:upload1" and tried the LRGB tutorial. But integration fails with "registeration failed". I do have some bad frames, but indivdual fits look okay
Â
Uploaded the lights and darks under a folder "tsk1979 upload". Upload going on at 2.7mbps currently, may take entire night I guess
Â
Vincent, can you please help?
You can just upload a subset of your data, like 20 frames of each data type, that should already show the problem.
@vincent-mod
Thanks. i have uploaded a few frames now. I see directory has quite a bit of data of various lengths to integrate
Â
Hello @vincent-mod did you get a chance to look at my data. I tried various settings again, yet registeration fails. I used a QHY183m with a ES102ED and no flattner
Â
I tried the beta and now 191 our of 256 images got registered. but final combined image is a blank. I uploaded the fits for individual channels and the integrated combined image to my folder
Â
@vincent-mod were you able to see my dataÂ
Not yet Tanveer, busy days. I'll have a look today!
@vincent-mod
Â
Thank you. With the Beta I was able to get past the no registration issue. Now I have the issue of individual channel FITS being unreadable in ASIFITSview and stacked combined image being totally black
Â
Yes I see that in your other post, still downloading (slow connection), I'll have to get back to it tomorrow unfortunately. Will do asap then.
Hi Tanveer,
Can I see the issue with a smaller dataset as well? Unfortunately I'm having trouble downloading everything, could you point out the data that should be enough to see the issue so I can download a part? Sorry for the inconvenience.
@vincent-mod
Â
What about the combined fits. I was able to do an integrate per channel but those files return a dark combined fits.
Â
Let me upload 3 files from each channel and update you
Â
I'll download the combined fits to double-check and yes 3 files from each should be fine, if you can point out which ones exactly then I can work on those. Thanks a lot for your patience!
@vincent-mod Thanks!
Â
You can download 3 files of each type I uploaded here
Files are named as <channel>_time
Â
There are a few 300s FITS and a few 60 second fits
Â
Download three of each (any three)
Â
The tool could not register any of the Ha FITS. But Lum and other channels had 75%+ registeration
Â
The issue now I am facing is that the combined FITS for a channel is not openable in ASIFITSviewer, and even the total combined FITS is not openable.
Â
So since bandwidth is an issue can you please see
Â
1. Why is the Ha channel not being registered, why are the FITS rejected?
2. Why the per channel FITS not openeable?
3. Why is the combined FITS black
Â
Â
Thanks, yes I'll have a close look and come back to you tomorrow and hopefully have an actual answer. 😉
Ok Tanveer. I had a look and didn't need to process as I found the signal already looking very strange in a red light frame. Looking at the FITS data, the offset on your camera is set to 0, which is not right. You need a proper offset for it (and all calibration frames).
@vincent-mod
Â
Thanks!
Â
Looks like I messed up in acquisition. I did an offset of "0" while acquisition. Looks like I need to re-acquire the data with proper offset
Â