fixed WBPP 2.8.5 and Grouping Keywords from FITS Headers

Additional info:
Before restoring the system, I reset WBPP to factory settings and deleted the calibration files. After re-inserting the files into WBPP, the errors occurred again in the same way.
 
here's the status errors (basically symptoms of the error):

WARNINGS

Cosmetic correction enabled with a mismatching master dark.
Cosmetic correction will use a master dark with a significant exposure time difference, this may lead to an inaccurate result.

Light frame's exposure differs from the Master Dark's exposure.
You can add a compatible Master Bias and optimize the Master Dark in order to achieve a better dark current estimation.
 
Unfortunately, the errors mentioned above for 2.8.5 also occur after the 2.8.6 update.
Here are some snapshots:
Tks
P.s. I have cleared the required memory (Diagnostics message), but no change
 

Attachments

  • WBPP284.jpg
    WBPP284.jpg
    334.3 KB · Views: 21
  • WBPP284_Pipeline.jpg
    WBPP284_Pipeline.jpg
    299.2 KB · Views: 22
  • WBPP286_Calibration.jpg
    WBPP286_Calibration.jpg
    389.5 KB · Views: 20
  • WBPP286_Diagnostic.jpg
    WBPP286_Diagnostic.jpg
    43.6 KB · Views: 19
  • WBPP286_Flats_.JPG
    WBPP286_Flats_.JPG
    119.8 KB · Views: 20
  • WBPP286_Pipeline_.JPG
    WBPP286_Pipeline_.JPG
    163 KB · Views: 22
bubab said:
Unfortunately, the errors mentioned above for 2.8.5 also occur after the 2.8.6 update.
Here are some snapshots:
Tks
P.s. I have cleared the required memory (Diagnostics message), but no change
Click to expand...

Hi @bubab

The bug described in this thread concerns keywords. It's confusing to describe a problem that's clearly unrelated. It would be better to open a separate thread.

It seems to me that your problem is the following: you have master files that aren't identified as such, but they're master files that weren't created with Pixinsight. I imagine you converted them to xisf, but nothing allows Pix to identify them as masters. If you add "master" to their names, then they should be recognized as such.
 
Hi Nico, tks
all the master files where generated by PI, but I renamed them for easier idenfication; all of them are working with WBPP2.8.4 (see screenshots WBPP284 & 284_pipeline), so it is caused by the update. I will try the original (unrenamed) files ASAP and give a report.
 
bubab said:
all the master files where generated by PI
Click to expand...
They have been generated with WBPP? Can you share one of these masters?

bubab said:
all of them are working with WBPP2.8.4 (see screenshots WBPP284 & 284_pipeline), so it is caused by the update.
Click to expand...
Yes, I noticed a difference in behavior between versions 2.8.4 and 2.8.6, but that doesn't (necessarily) mean there's a bug. Your workflow seems quite unusual.
 
The bug reported by the OP has been definitely fixed. Reusing an existing thread to report a completely different issue is unfortunate and causes a lot of confusion and trouble to follow the history of bug reports and fixes. Please create a new thread to report a new problem.
 
bubab said:
Unfortunately, the errors mentioned above for 2.8.5 also occur after the 2.8.6 update.
Here are some snapshots:
Tks
P.s. I have cleared the required memory (Diagnostics message), but no change
Click to expand...
Could you kindly open a new thread for this problem? I have few questions to ask.


thanks!
Robyx
 
Juan Conejero said:
This bug is now fixed in WBPP 2.8.6 and FBPP 1.1.9, which I have just released as an update for all platforms.
Click to expand...
I have verified that the bug I reported in the initial post has been fixed in 2.8.6 and I have successfully used 2.8.6 for a WBPP session utilizing FITS keywords for grouping. Thanks Juan for the quick turnaround!
 
You must log in or register to reply here.
Back
Top