WBPP pipeline Execution Monitor

This  question might be answered in one of the videos.  Sorry, I am still working my way through the class videos.

I made a mistake and ended up with a mono autocrop.  I had debayered but not combined.  I went back to my WBPP and checked the CFA and restarted the script.  Now I noticed that the "#" showing the number of operation in the pipeline is gone.    I think it's handy to have the operations in the pipeline numbered.    When and why are the pipeline operations numbered in the WBPP Execution monitor?    The script is still running. 

Comments

  • Hi Karen,

    For questions like this, it is helpful to make screenshots available to accompany your question. 
    One thing I would recommend (and I do suggest in FastTrack somewhere) is to NOT rely on the caching in the beginning. It just become too confusing. If you make a configuration error... it is better to delete the output files and restart clean. Specifying CFA is a configuration that effects processing (pipeline) all the way back to the beginning. 

    Let me know...
    -the Blockhead  
  • Thanks for the fast response.  
    I got the result I expected/intended.  I have my combined channel, cropped image.   I went back and opened the WBPP from my saved icon so I could do a screen capture of the pipeline from the monitor....Now every step has a number.  I should have done a screen capture earlier but now I know.   I'm not sure why the steps are numbered now because I know the monitor showed no numbered steps in the pipeline earlier.     Before I ran the WBPP, I did not delete the old files as you suggested.   All those previous files were there,  so that may have caused the steps to be un-numbered.     I'll remember to screen capture next time I know I am going to ask a question.      At least I can use the file explorer now!
  • Oh..  I realize that the WBPP execution monitor has never shown numbered steps.  The numbered steps are shown in the pipeline.

Sign In or Register to comment.