WBPP 2.4.5 Released
- Thread starter robyx
- Start date
gregwjones
Well-known member
The new Execution Monitor is great!
I did notice that there is a "Measurement" step in there just after the calibration and cosmeticCorrection steps. I reviewed the logs and saw that this step was measuring the CosmetricCorrection images. I assume this is to find the best frame to use for the star alignment process. But, I had manually defined the star registration image within WBPP.
Is this Measurement step necessary when the star reference image is manually defined?
See the attached screenshot. In this example the measurement step only took about 3 minutes, but for a larger dataset it could be a significant amount of time.
I did notice that there is a "Measurement" step in there just after the calibration and cosmeticCorrection steps. I reviewed the logs and saw that this step was measuring the CosmetricCorrection images. I assume this is to find the best frame to use for the star alignment process. But, I had manually defined the star registration image within WBPP.
Is this Measurement step necessary when the star reference image is manually defined?
See the attached screenshot. In this example the measurement step only took about 3 minutes, but for a larger dataset it could be a significant amount of time.
Attachments
Hi @gregwjones,
in your case Local Normalization is active, this step requires the selection of the best reference frame so the measurements are needed for this purpose
sbenz
Active member
Hi Roberto,
I wonder, what words is the script looking for in order to detect a folder containing flat darks?
I have my images sorted into four folders "darks", "flats", "flat darks" and "lights.
When I add them via "+ Directory" all files are detected, but the flat darks are sorted into "flats" instead of "darks". What do I need to do so that they are automatically detected as darks?
Thanks
Stefan
I wonder, what words is the script looking for in order to detect a folder containing flat darks?
I have my images sorted into four folders "darks", "flats", "flat darks" and "lights.
When I add them via "+ Directory" all files are detected, but the flat darks are sorted into "flats" instead of "darks". What do I need to do so that they are automatically detected as darks?
Thanks
Stefan
Ho @sbenz, flat darks are simply darks, put them under the darks folder ?
sbenz
Active member
Unfortunately that didn't work, they are still detected as Flats.
The reason might be that they are marked as "Flat Frames" in the FITS header (I took them right after the Flats, using the very same setting in the capture SW).
What are the criteria that the script is looking for?
Is there an order (FITS header, file name, folder name)?
What key words is the script looking for? Is there a list somewhere?
Thanks
Stefan
Ok in such case add them directly as darks using the Add Darks button on the bottom.
sbenz
Active member
This works, of course.
But I am trying to find out what I need to do different in the future, so that this works automatically.
In addition, I plan to give a little course on WBPP in our local astronomy club, so I am also looking into this for educational reasons…
Therefore I am interested in the logic behind.
Could you please help me with these questions?
What are the criteria that the script is looking for?
Is there an order (FITS header, file name, folder name)?
What key words is the script looking for? Is there a list somewhere?
thanks
Stefan
Last edited:
I just posted a thread that digs into the details on how WBPP retrieves the information of an added file, please check here the following
How WBPP retrieves the information of files in the session
Hi all, this post describes how WBPP recognizes the basic information and the associated grouping keywords value for each file added to the session. This process was subject to several incremental updates and the overall logic implemented in v2.4.5 has never been fully explained, so I hope this...
pixinsight.com
Let me know if this answers
sbenz
Active member
I just posted a thread that digs into the details on how WBPP retrieves the information of an added file, please check here the following
How WBPP retrieves the information of files in the session
Hi all, this post describes how WBPP recognizes the basic information and the associated grouping keywords value for each file added to the session. This process was subject to several incremental updates and the overall logic implemented in v2.4.5 has never been fully explained, so I hope this...pixinsight.com
Let me know if this answers
this is very helpful, thank you very much.
gregwjones
Well-known member
Hi @gregwjones,
in your case Local Normalization is active, this step requires the selection of the best reference frame so the measurements are needed for this purpose
Yes, but the measurements are on the cosmetically corrected images and the Local Normalization process works on the registered images.
Since I manually specified the registration reference image that is a significantly cropped frame, wouldn't the measurements also be significantly different?
measurements on images that are heavily cropped can be highly unreliable because the missing cropped part could significantly affect the measure. This is a situation that should be avoided.
As an alternative, if you really want to measure the registered frames, you can proceed with WBPP up to the registration, then re-add the registered files in a new session and proceed from there with LN and II. In both cases, the measurements are non-optimal either due to the high cropping or due to the registration interpolation (if measurements are performed after the registration).
Try and see which one produces the best result since there is not a general answer on which of the two is best, it really depends on the dataset.
Last edited:
sbenz
Active member
I still seem to understand something wrong, I still cannot get it to work.
As this topic is related to how WBPP retrieves information in general and not just to version V2.4.5, I posted my findings there (How WBPP 2.4.5 retrieves the information of files in the session).
I hope this causes not too much mixup.
What is not working? Post your screenshots if needed!I still seem to understand something wrong, I still cannot get it to work.
sbenz
Active member
I had posted this already in the other thread (I had thought that it matches there better), so apologies for double posting:
Thank you very much for posting this explanation.
I still struggle though, as I do not manage to have my flatdarks detected correctly.
They have the filename "FlatDark xxx.fit" inside a folder named "FlatDarks", but the FITS header contains a keyword "Flat Frame".
Therefore I selected "Smart naming override", but still all frames are sorted in as flats, not as darks.
I even renamed them into "Dark xxx.fit" and the folder into "Dark", still did not work.
What am I doing wrong?
Thanks
Stefan
Could you share 1 of these flat dark files?
Hello friends,
I haven't used WBPP for months and never had problems but with version 2.4.5 I get the following error in the Integration phase:
************************************************************
* Begin integration of Light frames
************************************************************
Group of 12 Light frames (12 active)
SIZE : 4144x2822
BINNING : 2
Filter : SII
Exposure : 300.00s
Keywords : []
Mode : post-calibration
Color : Gray
Rejection method auto-selected: Winsorized Sigma Clipping
Operation queue error: Error: ImageIntegration.weightMode(): invalid argument type: unsigned integer value expected.
* WeightedBatchPreprocessing: 04:06.95
Any suggestion?
I haven't used WBPP for months and never had problems but with version 2.4.5 I get the following error in the Integration phase:
************************************************************
* Begin integration of Light frames
************************************************************
Group of 12 Light frames (12 active)
SIZE : 4144x2822
BINNING : 2
Filter : SII
Exposure : 300.00s
Keywords : []
Mode : post-calibration
Color : Gray
Rejection method auto-selected: Winsorized Sigma Clipping
Operation queue error: Error: ImageIntegration.weightMode(): invalid argument type: unsigned integer value expected.
* WeightedBatchPreprocessing: 04:06.95
Any suggestion?
Attachments
Hi,
reset the parameters once, at least the ones of Image Integration!