›

How do you get the procees Icons to work

Mark Webster
in PixInsight
Ok Ive gone to download the process Icons on the NGC3486 workflow
when I press download all I see is a load of script....how do I turn this into Process Icons

Comments

  • BlockHeadBlockHead
    Hi Mark,

    When you download the file you should have something called "Process_Icons_used_in_workflow.xpsm "
    Once you have this file in PixInsight you right click on the desktop and under the section called Process Icons you "Load Process Icons." Select the file and the icons will load. You will need to look in your Workspace #2 (don't forget) and you should have a screen that looks like my picture at


    When you double click on any Icon you will see the same settings I used. The Icons are also basically arranged in order. However you will need to do it for yourself on your own machine since the files locations and dependencies are unique to my computer/session.

    These icons will only be useful to you after you have reviewed the (entire) Workflow content. 

    I considered making the entire project available for download- but of course it is really quite large if you include all of the raw data and everything... something on the order of 15Gb. 

    The options I considered (but I really need some direction from customers on this...I have been waiting!)

    1. I make just the raw data available. This is on the order of 3Gb. There may be some copyright things I need to deal with...but it allows for customers to follow from the beginning on their own with the same data.

    2. I make the project available. This will not have the raw data...but it will have the files I create from them and everything you see me do with the combined files forward. This is around 3Gb as well. No copyright problems here.

    3. Perhaps so other option I haven't consider or am not aware of...

    So some feedback would be awesome. But first, please let me know if you are able to get the icons loaded in your PI session. 

    -the Blockhead

  • Mark Webster
    Thanks Adam , I love your tutorials they are awesome. My only problem is my memory span ....it’s terrible. I constantly have to watch your videos whilst processing as I just can’t remember. Even somethings I do several times over. I suppose it wouldn’t be so bad if I was doing it more or less day after day. But the weather here in the Uk is hit and miss and along with my shifts it can be weeks if not months before I get new data.
    It would be nice to see some processing of OSC images. What I’m doing at the moment is separating them into RGB and lum then following your process. Don’t know if this is the best way though
  • Scott Iver
    Hi Adam,

    I think for me personally I like Option 2, especially if you could start us out with the stacked images (IE, we'd start at lesson "DBE Luminance").  For me personally it's from that point on where I get tripped up in Pi. 

    Thanks! 
  • BlockHeadBlockHead
    Mark,

    I head you. If I had MORE time, I could probably create different kinds of content to help. Quick reference guides and other things. . Concerning OSC... yes, once you debayer into RGB images... the workflow is pretty much the same. You would of course create a "synthetic" luminance from your combined RGBs... but other than that- everything else is pretty much the same. I will eventually get around to and OSC example.

    Scott,
    Thanks for the input. I would like a few more people chime in..but I agree this is a good way to go. The only "issue" is that my projects are "organized" in the way that I think. This might be scary... :)

    -the Blockhead
  • Sedat Bilgebay
    Second option is good Adam!
  • Rick Kuntz
    I get the same "script" when clicking on the "Download" button....
  • John Williams
    Hi Adam, new student here to your PI series. While in the beginning segments for Blinking and Calibrations etc. My data comes from two different camera set ups. I use a Mono along with L,R,G,B,Ha,Oiii and Sii. So those raw image files are fine throughout.  I also have OSC color image files and I also quite often am using an Optolong L-eXtreme where I can separate the lights into their several components. I don't know how to do those processes yet in PI, but that can come in the future. Here are two questions right away I have in this early learning stage for PI.

    Is there a way to open the raw image files in places like Blink and also in your manual calibration type of processes etc and debayer them so I don't have to be looking at the bayer patterned greyscale images that normally open up?  I see that the Batch Preprocess has a box to check for CFA files, but no where else. This is important as the popularity of OSC cameras and dual band filters are increasingly in use.

    Also, every time I take flats, I also take dark flats. Using NINA which has a Flats wizard to help you capture your flats, it makes it easy to take dark flats as well.  Why aren't dark flats being addressed in PI? In the Batch Preprocessing, there is no tab for Dark Flats? I first learned how to do raw data processing using APP and still am using that while now trying to learn PI, Dark Flats are fully integrated into their preprocesses.

    Thanks for your detailed video tutorials!
    John
  • BlockHeadBlockHead
    Hi John,

    Regarding the debayering- my suggestion is to look at the raw data in its greyscale form *until* you have calibrated it. As you know, the debayering happens after the files have been calibrated. Often beginners "destroy" the bayer matrix (raw file) and get confused as to why calibration , cosmetic correction and many other things don't work.  If you want to peek at the images  you can use the debayer process to temporarily see some color in a raw image. There isn't a blink method, that I am aware of, that will debayer and blink on the fly (which would take forever with alot of memory with the image sizes of most cameras!!)

    Regarding the Flat Darks- this is a new thing to cover with the CMOS cameras. I have covered it in a number of videos (WBPP, and some problem solving ones you will found later). However, the lack of this information in the beginning is due to the lag that inherent with the march of time of hardware/software improvements. This week in particular I hope to release more information on this stuff.

    -the Blockhead
  • Roger Smith
    Adam
    Your skillful weaving into the Fundamentals and WBPP2.0 videos the considerations for one shot color camera considerations was the perfect blend for understanding the differences vs Mono and also vs CCD. 

    We all appreciate your natural ability to explain what is going on, and why.
    Thank you!

    Roger
  • Dale Ouimette
    Adam,

    I am a student of your Fundamentals course and have come to the "Process Icons" part. I have successfully saved and loaded my own Process Icons, but when I download your Process Icons (or Process Icons from other websites), I can load them and see them listed in the Process Console. But they don't appear on my workspace. The Arrange Icons button is grayed-out as though they are not there. But the Process Console show that they are. What am I doing wrong?

    Dale
  • Dale Ouimette
    Adam,

    Sorry, I just figured it out. When I load my own Process Icons, they appear in my current workspace as I would expect. But when I load a Process Icon file from the web, it appears in my right-most workspace as indicated by a small blue square in the workspace icon at the bottom of my screen. Not sure why that is. But at least I can access them now.

    Dale
  • BlockHeadBlockHead
    Yeah...
    Process icons have their location's encoded within them when you save them. I learned this after I distributed some... so in the future I need to be careful and not create icons in weird places or other workspaces...it just confuses people.
    -the Blockhead (living up to the moniker!)
Sign In or Register to comment.