Just a quick question...did you have a chance to go through FastTrack Training?
I ask because you mention "No Filter" . Do you know where that is coming from?
WBPP will attach filter names to master lights. "No Filter" is the filter name in your file header (or it is given this by default if there isn't any information).
So you have:
1. The regular integration (masterlight). This is the result of stacking your files in ImageIntegration.
2. The Drizzled version is what you get when you check CFA Drizzle in WBPP. I am assuming you are using an OSC camera. If you are drizzling 1x1 the benefit will not be seen by comparing it to the regular integration (above). Instead, it is later after color calibration that color fidelity is better when you drizzle 1x1. Drizzling with larger scales is a *different* kind of activity. I do not recommend this in general unless you know what you are doing and why.
3. The Cropped versions of #1 and #2 are the INTERSECTION of the stacked images. Where at any pixel where all frames do not overlap...it is cropped.
The regular integration #1 is ALWAYS created. The CFA drizzled version could be an improvement on the regular version when it is color calibrated. The cropped frame is a further option that you have checked.
So the Drizzled-cropped image is the "final" one you want. I personally do not care for the cropped images- I can crop myself later and save myself from extra images that do not serve a purpose.
The list of answers to "what could be causing that..." is very very long!
The generation of master lights occurs at the end of a succession of steps.
The failure will be at one of the previous steps usually.
You should have some some indication of irregularities when WBPP was running (the execution monitor)- and those issues are saved in the logfile that is in your LOG folder.
You will need to start with some screencaptures. You will not be able to upload them here- you will need to upload to your own cloud drive and share them (with public permissions).
You need to upload your file(s) to a cloud drive like Google Drive, OneDrive, DropBox...etc etc.
In that way you can share with me. If it said it failed.... it will say why. However, it may not seem to answer "why" in common parlance...but the answer(s) is/are there.
At a minimum... you *always* need to step through the output of the data. FastIntegration is a little less easy to diagnose since you are purposefully not outputting the intermediate data. So to solve your issues.. you should use a smaller subset and not enable FastIntegration.
In the beginining this is the kind of time that is required to move forward. It is a bit tedious...but this is really how it works. So looking first at the calibrated data... then at the registered data... look at the numbers... zoom in...etc etc.
Thank you for posting the link. However, you need to do one more thing. You need to set the permission to the filtes/link to be "viewable by anyone with the link" ...
I just ran wbpp again and I posted the .log file. When I turned my machine on this morning and started PI there was an update for wbpp. I ran the update and now after this run it worked. This must of been a bug from the last update which was about a week ago.
There are a number of things at play here. Not bugs.
I looked at the actual log file you finally posted (thank you).
This run DID NOT USE FASTINTEGRATION.
Everything succeeded. It did not use FastIntegration because it appears you used grouping keywords and the groups of files being stacked were less than 150 frames.
The question is... why did you use FastIntegration previously. You would have forced it to do so manually since the automatic threshold is 150 frames.
I was using wbpp and it was taking 2.5 hours to process. I couldn't figure out what I was doing wrong. I started using fbpp just to save time and I was still getting the same result...no master lights. I've been using PI for over a year and I've been shooting OSC with dual narrow band ever since I started using PI. I had a problem understanding keywords back then...last year some time and you helped me through that, and haven't had a problem since. 2 things have changed recently, (1) was the recent update for wbpp, I dont know if that had something to do with it or not. Coincidence that an update came through this morning and then it works???
The 2nd change is I started using NINA and I started thinking last night am I saving the subs in the wrong format? But no...they're fine. I'm really at a loss here as to why this was happening. If it happens again would you mind if I sent you the log file again. I really appreciate your help.........
Well.. yes, you can send the log. However that is a heap of information to wade through.
I suggest trying to become adept at identifying pain points (of failure). Seeing a message that WBPP basically failed at that *last* step isn't helpful. If it didn't stack- then you need to look at the step before that (perhaps normalization) and the step before that (registration). Then it will be obvious why it failed in the end.
Another point here is recognizing patterns. You now have a data point. You KNOW you can run your data through WBPP without FastIntegration and it works. You also know that running your data through FastIntegration with a small number of files might be problematic- it was not intended for this use- but you did it which was a red flag. You raised a flag- but you called for a bug.
Really the only solution is doing things over and over and varying only one small parameter at a time. I know it takes time and effort and is tedious- but it is the only way to really be in control.
Comments