Let me preface this by saying that I know SGL is not a Pixinsight support forum, but I have tried to register for the PI forum and cannot yet post to it, so I am turning to you guys instead. But if mods feel this thread is inappropriate, please just delete it.
I'm creating a project for a specific set of actions in PI (composed of some processes and some scripts). I'd like to be able to store an icon for each step on the right hand side so I know what order to do everything in and to be able to preserve the settings for each step. It's easy to create an icon from processes (by dragging the triangle to the desktop). This can be done with some scripts too. But not all the scripts have a little triangle in the corner (for example, EZ Denoise). So how can I create an icon for those?
That one is not so easy but can do something similar.
EZDenoise runs TGVDenoise and MLT using masks so you can open the history of the image as described and if you drag both instances of TGVDenoise and MLT over in the correct order it will also drag the masks but if you wanted the masks as well you would have to save instances of those seperately.
thank you. So far I am just following steps from other people, but it's giving me a sense of how things work, for sure. I've been going back over some old stacked images and re-processing them. For example,
The AutoIntegrate script is a powerful tool for astrophotographers looking to efficiently process their images while maintaining a high degree of control over the final output. It exemplifies the balance between automation and customization, making advanced image processing more accessible to a broader range of users.
AutoIntegrate is a PixInsight script to process FITS and other image files and run a basic imageprocessing workflow to create a final image. Script has a GUI interface where some processing options can be selected.AutoIntegrate can do the whole image processing workflow including image calibration.
It is possible to automatically install and update AutoIntegrate script by adding it to the PixInsight update repository.Whenever PixInsight is started it will then check for updates to AutoIntegrate.To enable automatic updates you need to add the following Url to the PixInsight Resources/Updates/Manage Repositories.
In a page GitHub releases you can findthe latest release and download it from there. Releases page has some detailed information of changes in each release.To download the source code click Source code (zip) and save the zip file. After download is complete, unzip the file.
You can also go to GitHub AutoIntegrate main page to find the latest development changes and download it from there. GitHub master branch may contain test changes that are not yet available as a release.
Starting from AutoIntegrate version 1.56 there is a dependency to ImageSolver scriptin the PixInsight distribution. This means that ImageSolver files must be in the ../AdPdirectory relative to AutoIntegrate directory. You can do this by creating a ../AdPdirectory and copying the contents of Pixinsight-install-directory/src/scripts/AdPthere.
Script accepts all files that are supported by PixInsight. It can be used with FITS files from telescopes, or RAW files from DSLR. It can be used with both calibrated and non-calibrated files. For non-calibratedfiles the script can do image calibration.
When using RAW or OSC files, the script by default does debayering of the files. It is recommended to use the Pure RAWsetting in PixInsight. If the files are already debayered you should choose None in the Debayer list.
There are separate buttons for each filter type recognized by the script. Also color/OSC/DSLR files can be added manually.Manual adding is useful if the FILTER keyword is missing or just for overriding the filter keyword.
Narrowband images are supported by the script. They are processed mostly the same way asother images. Main difference is that you can choose the color palette that is used when mappingnarrowband images to RGB channels.
Below is a sample output from AutoIntegrate script when using narrowband data and SHO color palette. Otherwise it was runwith default settings but Remove green cast and Fix star colors options were checked.
If there is only one file for bias, dark or flat dark it is assumed to be a master file.If you have multiple master files for example for different binning you can give multiplemaster files but in that case option Master files must be checked. When multiple master files are available, the script picks the one with the same resolution.
Using the New Flowchart button the script will generate a flowchart of the processing workflow. Flowchart uses the current settings and images. A partially simulated minimal workflow is run to generate the flowchart information. To run the simulated workflow all relevant files must be loaded to the Files tab. A graphical version of the flowchart is printed to the preview window and a text version is printed to the process console.
Full Flowchart is available after processing. It is saved to the AutosaveSetup file and also to the setup file when availableso it can be loaded later. A text version of flowchart is also printed to the AutoIntegrate log file.
Flowchart information is always generated during processing. It can viewed using Show Flowchartcheckbox. During processing Flowchart is updated after each step. By checking and unchecking the Show Flowchartcheckbox it is possible to switch between the current preview image and flowchart.
If System setting option Get flowchart data before processing is selected then flowchart data is collectedbefore processing. This is useful if you want to see the full flowchart during processing. Note that this option is notselected by default. Full flowchart is not available with AutoContinue orbatch processing.
A startup image is shown in the preview window when the script starts. This startup imagecan be changed to a user selected image in the Interface section. The startup imagecan also be disabled there.
It is also possible to view the processing history by loading the image as a target image in the AutoIntegrate script Extra processing tab. Then the processing history is printed to the process consoleusing the AutoIntegrate processing history button.
It is possible to automatically crop bad pixels on the sides of the images. This works by integratingall images, finding an area where all images are contributing and cropping channel images to that area.
Automatic cropping can be used also during AutoContinue. Cropping requires that the LowRejectionMap_ALL file is open in the PixInsight desktop. Cropping can be done only if starting from Integration_[LRGBHSO] or Integration_RGB_color files.
In the case of AutoContinue it is possible to edit the crop preview area in the LowRejectionMap_ALL image. AutoContinue will use the crop previewfrom LowRejectionMap_ALL. In this way it is possible to rerun the processing using a different crop if needed.
Sometimes the cropping also helps with automatic processing. Below is an example that shows the processing difference between non-cropped image (left) and cropped image (right). Since bad pixels on the side are cropped, automatic processing can better stretch the images since there is only real data in the image.
It is possible to manually choose reference images. A reference image for star alignment is used to align all light images. For each filter reference images are used for image integration and local normalization.
There is a button that can be used to calculate SSWEIGHT values for each file and automatically mark reference images to the file list. It is useful for checking which files would be chosen and fine tune the selection if needed. SSWEIGHT values are calculated for raw files that are not debayered or cosmetically corrected so they may differ from those calculated during processing. If no reference images are selected manually then automatically selected images are marked to the file list after processing.They can be found also from the AutoIntegrate log file.
Note that manually selecting reference images for filters do not work with OSC images if the Extract channels option is used. In that case extracted channel images should be loaded separately as LRGB images to choose correct reference images.
AutoIntegrate supports the new FastIntegration process. FastIntegration is a new process that is available in PixInsight version 1.8.9-2 or later. It is a faster version of the old ImageIntegration process. It is recommended to use FastIntegration instead of ImageIntegrationif you want quick results or if you have a huge number of images.
Masked Stretch is a good choice when Auto STF does not give a good image. For example with bright galaxy images Masked Stretch is a good choice as it keeps brightness in control and gives better saturation.
Histogram stretch is a very simple stretch that moves the histogram median or peak to the target value.Stretch is done iteratively in small steps. Also a selected amount of shadow clipping can be done.
Generalized Hyperbolic Stretching (GHS) is most useful on bright targets where AutoSTF may not work well.It often preserves background and stars well and also saturation is good. For very dim or small targetsthe implementation in AutoIntegrate does not work that well. Current implementation in AutoIntegrate is very experimental but may work on some images.
It is recommended that dark background is as clean as possible from any gradients with GHS.Consider using Gradient correction on combined images and maybe also BackgroundNeutralization to clean the image background. Local Normalization can be useful too.
c80f0f1006