DBE: fails to generate background model image and misplaces extracted image

[LarryC]

I was using DBE just fine for a few months then in the middle of a project, clicking Apply, or dragging an instance to the image results in normal script behavior according to the Process Console, but neither the background model or the extracted new image image appear on the main workspace screen (I only have one monitor).  After many attempts, reboots, new DBE instances, deleting swap files, etc., I discovered that the new extracted image was being generated, but not shown on the screen.  Selecting it in the Image Selector brings it up on the main workspace where it used to appear automatically.  However, the background model image is nowhere to be found ("discard background image" is NOT checked).  Behavior is the same whether correction is "none", "subtraction", or "division".

This is what is generated in the Process Console:


DynamicBackgroundExtraction: Processing view: light_M20_M8_DC
Generating model channel #0
2-D surface spline interpolation: done
Generating model channel #1
2-D surface spline interpolation: done
Generating model channel #2
2-D surface spline interpolation: done
Applying background correction: done
Rescaling samples:   0%
Computing extreme sample values: done
6.261 s


i7 4770K OC to 4.3mHz, >2Tb available SSD/HDD space, 16gb ram.
PI:  1.08.04.1185

I've tried to attach a screen shot of my settings, but they are similar to the settings I have always used.

Larry

[Andres.Pozo]

It seems to be similar to this other bug report:
http://pixinsight.com/forum/index.php?topic=9187.msg59460#msg59460

[Juan Conejero]

Yes, this is the same bug that Andrés has pointed out. This problem is already fixed. I ask for just a bit more of patience: tomorrow we'll release version 1.8.4.1193 officially for all platforms.

[LarryC]

I updated to the latest release today but the behavior persists - no new image is presented on my workspace, though  I can find the new extracted image in the image selector, but the extracted background image is nowhere to be found.

[Juan Conejero]

I cannot reproduce this problem on Windows 7, 8.1 and 10 with 1.8.4.1193.

the extracted background image is nowhere to be found

Are you sure you haven't enabled the discard background model option?

[LarryC]

I can replicate this every time by opening an image, opening a new instance of DBE from the process console, resetting to get grid lines, increasing samples/row and radius to 20 and 10 (or leaving them at the defaults), selecting Subtraction as the correction method and clicking the Execute green check.  The new extracted image does not appear but is in the image selector, but there is no background image.  "Discard background image" is NOT checked. 

However, if I do the above but instead drag the new instance triangle to the image I get both the new image and the bkg image on my workspace.  This is how the "execute" green check mark also used to work until I reported the behavior in my original post.

I've attached a screenshot of what I see immediately after "executing" then opening the image selector.  There are no images behind the original image seen on the workspace.

Larry

[msmythers]

Larry

That is a strange one. I get the same result on my Windows 7 system.


Mike

[LarryC]

It gets stranger.  I can replicate the above over and over.  The file I'm working with is the particular saved PI generated integrated and dynamically cropped XISF image that I first experienced the odd DBE behavior with.  I DO NOT see this behavior  with several other similarly generated XISF images.  Also,  if I try the same DBE settings described above with this problem image but select "none" for correction, I do get the background image on the workspace.  If I then change correction to Subtraction, the behavior returns.

I have several versions of this image as intermediates with various other processing adjustments and of the three versions I tested, all result in the odd DBE behavior (I have not tested all of the various intermediates of the image, I have about 8).

[Juan Conejero]

I have tried to reproduce this problem again without success. This does not happen with 1.8.4.1193 on any of our machines, on any platform, with any of our test images. Very strange indeed.

Can you upload the image where you are seeing this behavior consistently?

[Cyclop_si]

Same problem here after upgrade to 1.8.4.1193

No problems before upgrade.

[msmythers]

Juan

here is a video showing the issue.
https://drive.google.com/file/d/0B13r3kYqTf8NSmE4Rm9oSzE4QXc/view?usp=sharing


Mike

[LarryC]

Juan,  Here's a Dropbox link to one of the XISF images that appears to be a problem for DBE.

https://dl.dropboxusercontent.com/u/70003962/Couture_M20_M8.xisf

Larry

[msmythers]

Larry

I just did a quick test and any image I have that is not a xisf works as expected. My xisf files don't. If I take the image I showed in the video and save it as a fit or tif and then try the same exact steps as I did with the xisf dbe works as expected. I only shoot with a DSLR(OSC) so I don't know if there is any issue there.

Mike

[Juan Conejero]

Thank you for uploading the image and the video. I can reproduce exactly the same problem that you have on Windows 10 with Larry's image. However, the same image works perfectly with DBE on OS X and Linux, and I cannot reproduce this problem with any other image on Windows, irrespective of file formats.

As Mike says, if I save Larry's image in TIFF format, then there is no problem with DBE. I have tried many different modifications to the image, including disabling color management, changing the embedded ICC profile, adding pedestals, cropping, resampling, interpolating the data in different ways, and destroying image properties. No matter what I do, this image always reproduces the same problem.

Frankly, this is one of the weirdest things I've seen in many years. Looks like paranormal Seriously, I want to get to the bottom of this problem. From my experience, I suspect this is a Visual C++ compiler bug. I'll try to switch to VC++ 2015 ASAP (currently we are using VC++ 2013), which probably will solve the problem "automagically". Anyway, it is clear that this image has something that triggers the bug in some way, and I want to discover it. If you could upload at least another image that causes the same problem, preferably a very different image if possible, that would help me a lot.

While I fix this issue, the workaround is simple: Instead of clicking "Execute" on DBE (green check mark button), drag the New Instance icon (blue triangle). On all my tests at least, DBE works perfectly with this image if applied this way.

[LarryC]

Juan,

I'm on Windows 8.1.   

Thanks for looking into this.  I'd don't have a lot of images (yet), but I'll check them all as well as re-create this image and see what happens.

I too have had no problem with any other process on this image, but further processed progeny of this image maintain the DBE problem. 

Larry