Unexpected Dynamic Background Extraction Behavior

[niteman1946]

I've searched to see if anyone else has commented on this, but have found nothing.  Apologies if this has been discussed and resolved.
I've just upgraded my Dell 64bit Windows 7 desktop to Windows 10.  I've also just upgraded from the PI v1.8.04.1170 to v1.8.04.1185.
Previously in DBE:
1.  Change the Target Image Correction "Correction" to Subtract (or rarely Divide), leave the rest of the choices at default, and leave "Normalize", "Discard ..." and "Replace ..." unchecked.
2.  The displayed result after dropping the blue triangle into the target image was --  the original Target image, the new Background image and the new DBE'd image.

Now in DBE (with same approach as above):
1.  Results (sometimes) -- the original Target image, the new DBE'd image, no new Background image.
2.  Results (sometimes) -- the original Target image, the new Background image, no apparent DBE'd image (although it becomes listed in the PI taskbar at the bottom of the page, just left of the four workspace panels, and can be retrieved from there).
3.  Results (sometimes) -- the original Target image, no Background image (not even hidden), and no apparent DBE'd image (but hiding as stated in above no. 2).

In each case Pi does not throw an error and appears to believe it has completed the process.
Any thoughts on this?  Reckon this may be a graphics issue? 
Thanks for you help,
Mark

[Juan Conejero]

Nothing remotely similar to this problem can be reproduced on any machine that I have access to.

There have been several problems with driver incompatibilities on Dell computers after upgrading to Windows 10. See for example this thread, where a user has reported an immediate solution after updating drivers.

Sorry for not being able to offer a clear solution to this problem, but please understand that I can't solve problems that I am unable to reproduce.

Anyone else is having similar problems ??

[niteman1946]

Thanks for the quick response.  And if anyone has anything else to offer, I will keep an eye on my post.
Meanwhile, I'll see if the graphic drivers are my solution.

Mark

[Office97]

I'm having exactly the same problem on a Windows 7 64 bit machine with an AMD graphics card. Nothing has been changed other than updating PixInsight.
On version 1170 DBE behaves as it should and produces a new target image and a background model image on the workspace (assuming the relevant tick boxes are left unchecked).
On versions 1185 and 1190 DBE usually fails to produce either of the new images on the workspace but as Mark above notes the new target image is listed in the view explorer and view selector (and can be accessed) but sadly not the background model.
Rolling back to version 1170 immediately fixes it.

Any thoughts?

Mark B

[Juan Conejero]

Bug confirmed. I have managed to reproduce it on Linux and Windows (only result #2 as described by the OP). Fixing it right now, sorry for the inconvenience.

[Juan Conejero]

This bug is now fixed in version 1.8.4.1192, which will be released this week. Thank you for reporting.

[Office97]

Excellent news!

Thank you for fixing it.

Mark B

[niteman1946]

Hi Juan,
unfortunately this bug persists with 1193.

Mark

[Juan Conejero]

Hi Mark,

I cannot reproduce this problem with 1.8.4.1193 on any platform, including Windows 8.1 and Windows 10 - and I have tried hard to reproduce it. However, I have added a safeguard that should make this problem impossible to happen anymore (in theory). It will be available in the next 1.8.4.1194 version, which is due this week. Sorry for the inconvenience.

When this problem happens, please note that the images can be selected from the View Explorer window without problems.

[niteman1946]

Thanks for the effort, Juan.

A couple of things:
1.  Since I first posted, I decided to revert to Win 7 -- too much hinkiness (in general) with the Win 10 upgrade.  So Win 7 is what I tested with 1193.
2.  My workaround from day one has been to select "replace target image" in the Target Image Correction.  This has consistently produced a background image.  And, of course, the original image becomes the DBE'd image.

Mark

[RalphPaonessa]

I am also having this problem on 1193 and Windows 10. I recently upgraded to the latest nVidia drivers for my system. I'm not sure if the problem started after my latest PI update or the video update.

I am able to find the corrected image in the View Explorer; but not the background.

It seems that this problem does not occur the first time I use DBE after opening it; but then it happens after I tweak the settings and try another extraction.

[Juan Conejero]

Looks like I have found and fixed this problem. While I prepare the next release, I have a workaround to prevent this from happening on Windows: Simply remove all FITS header keywords from the image you are going to apply DBE to. You can do this with the FITSHeader tool, or even faster, select the desired image and execute this command from the Process Console:

j ImageWindow.activeWindow.keywords = [];

This will be fixed in the incoming 1.8.4.1195 version. Sorry for the inconvenience.