Problem with WBPP

Richard Sauerbrun

I have used WBPP successfully for quite a while, but have run into an issue I am unable to resolve. With the image files and settings being used, I am unable to generate any masters. Here are some details:

• ASI183MC Pro
• 60 - 60s lights with gain 111
• 30 - 60s darks at 111 gain
• 30 - .48s flats
• 30 - .48s flat darks

Verified all FIT file headers as correct.

Using Adam's settings for processing OSC images. I am willing to share data if needed.

Assistance very much appreciated.

BlockHead

Everything looks correct to me.

It appears you have run out of memory. My best guess is that this is a hardware issue.

ImageIntegration loads and manipulates images entirely in memory. According to the log the integration of the darks simply fails without any other comment. Everything fails after this as a consequence...so all other issues can be ignored.

-the Blockhead

Richard Sauerbrun

Interesting ... my Windows 11 Pro system has 32gb of RAM runing on an Intel i7 processor. No other apps running at the same time.

BlockHead

You should try to just integrate this darks "manually" with ImageIntegration.

(I show how to do this correctly in Fundamentals.)

Just verify you can or cannot do this outside of WBPP. WBPP isn't doing anything different than manual...but if you find there is a difference in behavior..it will be a BIG clue.

-the Blockhead

Richard Sauerbrun

I found the issue ... the 4TB hard drive I use to store all my images for processing was full. "No drive space - No Masters".

I deleted a bunch of older projects and now I am back in business ...

BlockHead

That is a form of memory and it is a hardware issue... 

This makes sense. 

Now... to clean up this thread...

"Adam's settings for processing OSC" are not in error and are perfectly OK. :)

You might consider a concluding remark on YouTube as well.

-the Blockhead

Richard Sauerbrun

Hello Adam (the Blockhead),

I understand your desire to clean this up and set the record straight on YouTube. However, it seems there is still an issue with my settings.

I have cleaned up my 4TB SSD and now have 50% free space, but the WBPP script still ends in an error with no master light being created.

Last night I gathered 3 hours of data on M96, then took flats and flat darks early this morning. I used Blink to take a look at the images, and all seemed OK. I then looked at a few image headers and all the key data was intact. I then loaded all the files into WBPP (using the directory method) and started the process. I did manually select the reference image to save time.

I will attach one of the .FIT files, a few screen shots as well as the logs from my last run.

I very much appreciate your assistance,

Richard

BlockHead

Richard,

In your previous comment you indicated you have 32Gb of memory.

This does not appear to be true according to the logfile. In addition, the logfile is indicating that you ran out of memory. This still appears to be a hardware issue. 16Gb is not nearly enough to process this many images in PixInisght (unless you use FastIntegration and set the parameters accordingly). Just loading this data takes 13Gb of your memory. There isn't enough headroom.

[2024-04-16 18:09:33] * Available physical memory: 16.531 GiB   <---------

[2024-04-16 18:09:33] * Allocated pixel buffer: 4176 rows, 12.927 GiB  <---------

[2024-04-16 18:09:33] * Using 12 concurrent pixel stack(s), 0.148 GiB

[2024-04-16 18:09:33] 

[2024-04-16 18:09:33] 

[2024-04-16 18:09:33] * Integrating channel 1 of 3:

[2024-04-16 18:09:33] Integrating pixel rows:     0 ->  4175:   0%

[2024-04-16 18:27:21] <* failed *>

[2024-04-16 18:27:21] ** Warning: ImageIntegration failed.

-the Blockhead

BlockHead

Let me add, these issues can all be reproduced with ImageIntegration alone. If you just attempt to use image integration on this number of files you will reproduce the error. You do not need to run all of the WBPP tasks to investigate this issue. You will know the answer in minutes rather than *hours*.

-the Blockhead

Richard Sauerbrun

Thank you once again ...

I will diagnose the memory issue and test with the imageintegration process.

I will run with the task manager's performance screen active and the memory utilization selected.

Neil Schulman

FWIW depending upon your version of PI there was a bug where PI did not recognize all the machine’s available memory. So if you aren’t on the more recent builds (might as well go with the latest) it may be worth considering..ad-slot {
display: none !important;
}
.nxst-retrans-banner {
display: none !important;
}