Version 1.076 beta not working on my laptop

Interesting, could you provide some more details as to what system it is running on and what you're trying?

Dear @lammertus,

Can you please share more information? The console output shows that registration was stopped and thus the pending normalization and integration are stopped as well. The reason for stopping in registration should be found earlier in the console output.

13:50:18 - 5) NORMALIZE:: REGISTER was stopped, cancelling normalization task as well
...
13:50:18 - 6) INTEGRATE: normalization was broken down, so cancelling integration as well.

The OpenGL /GL3 button only affects image viewing in the image viewer, it does not affect data processing b.t.w. 😉

Mabula

Hi Vincent and Mabula,

To start with, I tried several times installing trying and failing, then

going back to version 1.075 and all ok again.

Now I reinstalled version 1.076 again and it fails again so it is repeatable

at least for me on my laptop.

Laptop is running W10 x 64 is a I7 old laptop with 4 cores, 8Gb Ram

and a smallish 500Gb SSD ( 20Gb or more free space on C-partition )

Now I copied more info from the console window and will paste it here

if that is allowed. ( if not please mail me where to mail it to )

With best regards,

Lammertus

********************* Console output ******************

18:05:35 - 3) ANALYSE STARS: 16 image loaders created...
18:05:35 - GENERAL IMAGE LOADER: loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-13-05__-15.00_120.00s_0002.fits
18:05:35 - GENERAL IMAGE LOADER: loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-11-03__-15.10_120.00s_0001.fits
18:05:36 - 2) CALIBRATE: Adaptive Data Pedestal: enabled
18:05:36 - 2) CALIBRATE: Adaptive Data Pedestal set at: 0
18:05:36 - 2) CALIBRATE: Adaptive Data Pedestal re-initialized at: 0
18:05:36 - GENERAL IMAGE LOADER: loading frame D:\Imagenes DSO 2019\Librerias 2018\Libreria-Darks\Gain 139 Offset 10 Bin 1x1\MD-ISO_gain_139.0-exp_120.0s-15subs-ZWO_ASI1600MC-Cool-4656x3520-NR-avg.fits
18:05:38 - GENERAL IMAGE LOADER: frame D:\Imagenes DSO 2019\Librerias 2018\Libreria-Darks\Gain 139 Offset 10 Bin 1x1\MD-ISO_gain_139.0-exp_120.0s-15subs-ZWO_ASI1600MC-Cool-4656x3520-NR-avg.fits was loaded successfully
18:05:38 - 2) CALIBRATE: Adaptive Data Pedestal re-initialized at: 0
18:05:38 - GENERAL IMAGE LOADER: loading frame D:\Imagenes DSO 2019\NINA\011120\Pannstars\MF-ISO_gain_139.0-exp_2.433419s-19subs-ZWO_ASI1600MC-Cool-4656x3520-NR-noBl-avg.fits
18:05:40 - GENERAL IMAGE LOADER: frame D:\Imagenes DSO 2019\NINA\011120\Pannstars\MF-ISO_gain_139.0-exp_2.433419s-19subs-ZWO_ASI1600MC-Cool-4656x3520-NR-noBl-avg.fits was loaded successfully
18:05:40 - 2) CALIBRATE: performing calibration in 32bits normalized floats...
18:05:40 - 2) CALIBRATE: converting data to 32bits normalized floats...
18:05:40 - 2) CALIBRATE: converting MasterFlat to 32bits normalized floats...
18:05:40 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-13-05__-15.00_120.00s_0002.fits
18:05:41 - 2) CALIBRATE: Adaptive Data Pedestal: enabled
18:05:41 - 2) CALIBRATE: Adaptive Data Pedestal set at: 0
18:05:41 - 2) CALIBRATE: performing calibration in 32bits normalized floats...
18:05:41 - 2) CALIBRATE: converting data to 32bits normalized floats...
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-11-03__-15.10_120.00s_0001.fits
18:05:42 - 3) ANALYSE STARS: was cancelled
18:05:42 - FRAME DETAILS UPDATER: starting...
18:05:42 - FRAME DETAILS UPDATER: no new frames to add
18:05:42 - FRAME DETAILS UPDATER: rebuilding all frame details...
18:05:42 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-18-35__-15.00_120.00s_0001.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-20-37__-15.00_120.00s_0002.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-22-38__-15.00_120.00s_0003.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-24-40__-15.00_120.00s_0004.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-26-41__-15.00_120.00s_0005.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-28-43__-15.00_120.00s_0006.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-30-44__-15.00_120.00s_0007.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-32-46__-15.00_120.00s_0008.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-34-47__-15.00_120.00s_0009.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-36-49__-15.00_120.00s_0010.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-44-18__-15.00_120.00s_0011.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-46-19__-15.00_120.00s_0012.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-48-21__-15.00_120.00s_0013.fits
18:05:42 - GENERAL IMAGE LOADER: cancelled loading frame D:\Imagenes DSO 2019\NINA\020620\NGC2403\LIGHT\UGC 3918_2020-02-06_21-50-22__-15.00_120.00s_0014.fits
18:05:42 - FRAME DETAILS UPDATER: updated succesfully
18:05:42 - CONSTRUCT FRAME DETAILS LIST: starting...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: finished
18:05:42 - 4) REGISTER: 3) ANALYSE STARS was cancelled, cancelling registration task as well
18:05:42 - 2) CALIBRATE: VERIFY CALIBRATION MASTERS: all frames are verified
18:05:42 - 4) REGISTER: cancelled!
18:05:42 - FRAME DETAILS UPDATER: starting...
18:05:42 - FRAME DETAILS UPDATER: no new frames to add
18:05:42 - FRAME DETAILS UPDATER: rebuilding all frame details...
18:05:42 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
18:05:42 - FRAME DETAILS UPDATER: updated succesfully
18:05:42 - CONSTRUCT FRAME DETAILS LIST: starting...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
18:05:42 - CONSTRUCT FRAME DETAILS LIST: finished
18:05:43 - FRAME DETAILS UPDATER: starting...
18:05:43 - FRAME DETAILS UPDATER: no new frames to add
18:05:43 - FRAME DETAILS UPDATER: rebuilding all frame details...
18:05:43 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
18:05:43 - FRAME DETAILS UPDATER: updated succesfully
18:05:43 - CONSTRUCT FRAME DETAILS LIST: starting...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: finished
18:05:43 - 5) NORMALIZE:: REGISTER was stopped, cancelling normalization task as well
18:05:43 - 5) NORMALIZE: was cancelled...
18:05:43 - FRAME DETAILS UPDATER: starting...
18:05:43 - FRAME DETAILS UPDATER: no new frames to add
18:05:43 - FRAME DETAILS UPDATER: rebuilding all frame details...
18:05:43 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
18:05:43 - FRAME DETAILS UPDATER: updated succesfully
18:05:43 - CONSTRUCT FRAME DETAILS LIST: starting...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
18:05:43 - CONSTRUCT FRAME DETAILS LIST: finished
18:05:43 - 6) INTEGRATE: normalization was broken down, so cancelling integration as well.
18:05:43 - FRAME DETAILS UPDATER: starting...
18:05:43 - FRAME DETAILS UPDATER: no new frames to add
18:05:43 - FRAME DETAILS UPDATER: rebuilding all frame details...
18:05:43 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
18:05:44 - FRAME DETAILS UPDATER: updated succesfully
18:05:44 - CONSTRUCT FRAME DETAILS LIST: starting...
18:05:44 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
18:05:44 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
18:05:44 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
18:05:44 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
18:05:44 - CONSTRUCT FRAME DETAILS LIST: finished

Hi @lammertus,

Thank you for the console output. That really helps.

I can clearly see the issue, i just fixed this and released a new beta. It concerns data calibration in 32bits and it is a bug in the first beta as reported here:

https://www.astropixelprocessor.com/community/rfcs-request-for-changes/preview-and-saving-calibrated-images-errors /

Download here (when logged in):

https://www.astropixelprocessor.com/community/appreleases/downloads/

Please download 1.076 beta 3 and let me know if all is fine now 😉

Mabula

Hi Mabula,

Yes, the latest beta 3 works, but the final result shows up a bit strange,

please check attached image! Lower right cuadrant is the image! The

other cuadrants don't know where they come from!

Regards,

Lammertus

Strangely enough when loading the stack into Pixinsight there is only

the correct image and not what was shown in the earlier posted image!

With 4 cuadrants, lower right was the image.

Good thing: now it is very easy processing in Pix, colors seem to be

spot on!!

Can't wait to see the final version of 1.076, good work!!

Best regards,

Lammertus

Interesting, could it be it's a mosaic and that you're zoomed in on the lower left or is it really just showing up like that?

And thanks for the congrats! 🙂

Posted by: @vincent-mod

Interesting, could it be it's a mosaic and that you're zoomed in on the lower left or is it really just showing up like that?

And thanks for the congrats! 🙂

Hi Vincent,

No, it was not a mosaic, only 16 frames straight forward.

When loading the resulting stack into Pixinsight all is ok, only

after integration in beta 3 it showed up like I posted

Regards,

Lammertus

Ok, well thanks a lot for the post and I'll make sure @mabula-admin knows about it.

Hi  @lammertus & @vincent-mod,

Thank you for your feedback again Lammertus.

I think we have a problem here with OpenGL3 on your machine. So the image viewer is showing things not correctly...

Can you check the following for me: when APP starts, the console panel shows some information about OpenGL initialization. What does it say?

Mine says:

Does it look allright when your disable OpenGL by clicking on the top left GL3 button ?

Kind regards,

Mabula

Hi Mabula,

Here is the console outputscreen:

I will try to process later with the same dataset and select OPENGL

instead of GL3 and will let you know!

Thanks for following up!

Lammertus

Posted by: @lammertus

Hi Mabula,

Here is the console outputscreen:

I will try to process later with the same dataset and select OPENGL

instead of GL3 and will let you know!

Thanks for following up!

Lammertus

Hi Lammertus @lammertus,

I see that the OpenGL is provided by Intel. So I assume that your computer has a motherboard or CPU with integrated graphics like an Intel HD6000/620/630 etc... ? Is that correct?

I know that a couple of the Intel graphical drivers have OpenGL bugs... can you verify if you are using the latest Intel graphical drivers and if not, update them and test again?

I know that in several cases of APP installations, this solved any OpenGL problems.

Mabula

Hi Mabula,

There is a sticker on the laptop stating NVIDIA GFORCE GT520M, don't know

if that is true.

When processing with OPENGL all goes well:

Likely another user error of me 😕

Regards and thanks for your patience!!

Lammertus

I do have the NVIDIA drivers installed but will now check for updates!

I reinstalled from Windows7 to Windows10 so maybe here is some error

with drivers not updated, will check now and let you know!

Lammertus

Ok, I just reinstalled the driver for Windows10x64 ( alas the same version number )

for the Nvidia GT520M.

Reprocessed everything with the exact same settings and the same error occurs

with GL3 selected:

Processing ( specially normalizing ) went quick, the slowest part was the

integration. It looks to be quit some faster then in version 1.075!

Strangely enough the final real image is now on the lower right cuadrant.

When now selecting OPEN GL the image reloads and shows up fine, no cuadrants

whatsoever, when reselecting GL3 again the cuadrants apear again.

Hope that clarifies something, likely my laptop is too old? ( 4 core I7 )

Regards,

Lammertus

Posted by: @lammertus

Ok, I just reinstalled the driver for Windows10x64 ( alas the same version number )

for the Nvidia GT520M.

Reprocessed everything with the exact same settings and the same error occurs

with GL3 selected:

Processing ( specially normalizing ) went quick, the slowest part was the

integration. It looks to be quit some faster then in version 1.075!

Strangely enough the final real image is now on the lower right cuadrant.

When now selecting OPEN GL the image reloads and shows up fine, no cuadrants

whatsoever, when reselecting GL3 again the cuadrants apear again.

Hope that clarifies something, likely my laptop is too old? ( 4 core I7 )

Regards,

Lammertus

Hi @Lammertus,

If you have an Nvidia graphical chip in your computer, the OpenGL should be provided by Nvidia, not by Intel. Somehow, APP is not able to use the Nvidia chip.

Upgrading from windows 7 to 10 can cause all sorts of issues, and to me, this sounds like misconfigured/installed drivers. I can't be sure off course, but it does sounds rather suspicious... 🙄 

In addition, even an older graphical intel chipset should work fine and provide GL4. OpenGL is old technology and GL3 and GL2 are over 10 years old...

https://en.wikipedia.org/wiki/OpenGL

I would not be surprised if you can manage to clean the drivers up and install fresh new one, that all will be okay.

Check with device manager, if you indeed have both Intel and Nvidia chipsets. If so, remove for both Intel and Nvidia all currently installed software for those chipsets.

Then I would recommend to start first by installing the Intel chipset drivers, make sure that you get the latest Intel drivers from Intel's website.

Then check what happens with OpenGL in APP.

Next step would be to install the latest Nvidia drivers, if all is okay, APP will use those drivers for OpenGL.

Kind regards,

Mabula

Hello Mabula,

Thank you for your help and information in order to get this sorted out.

Now, after reinstalling all the drivers and even chipset drivers as modern as

I could get ( remember my laptop has more then 10 years of life ) it still

behaves the very same with version 1.076 beta 3.

However, I reinstalled 1.075 and used GL3 and it works good! No

4 cuadrants shown or whatever, does that imply that there might be something

wrong still in beta3??

I mean to say if I use GL3 in version 1.075 and it works fine, then the drivers

implied should be ok, do I miss something here??

Thanks again for your interest in solving this!! Much apreciated

Lammertus

No, seems like you're doing it right, might be some issue with GL3 and older hardware maybe? I'll tag Mabula so he can chime in later @mabula-admin