image calibration issues
- Thread starter blang68
- Start date
fredvanner
Well-known member
My guess is that you are loading a saved set of process icons at startup. You have upgraded to a newer PI version, and the saved icons include some paramaters that are no longer defined for the specified processes. The solution is to create new process instances of these processes with the parameters updated to the latest version, and resave your process icons with these updated icons.
Is there a process (pun unintended) people follow to do this methodically?
Can you just open the process icon, adjust parameters, and save it, or does that also save garbage from the prior version that may be inappropriate?
Do you save a screen shot or text/code version of each icon before the upgrade, and compare details on each one?
I have definitely had work messed up by not appropriately adjusting process icons, to the point I keep thinking about saving off notes or screen shots instead of icons. I'm delighted that we keep getting new functionality, but the last few updates have really impacted both workflows and process icons badly.
Is there a better way to deal with it than just starting over and recreating each icon for which there is a warning (or... does one do it for each icon even without warning, because it may have new parameters that did not get initialized appropriately)?
Can you just open the process icon, adjust parameters, and save it, or does that also save garbage from the prior version that may be inappropriate?
Do you save a screen shot or text/code version of each icon before the upgrade, and compare details on each one?
I have definitely had work messed up by not appropriately adjusting process icons, to the point I keep thinking about saving off notes or screen shots instead of icons. I'm delighted that we keep getting new functionality, but the last few updates have really impacted both workflows and process icons badly.
Is there a better way to deal with it than just starting over and recreating each icon for which there is a warning (or... does one do it for each icon even without warning, because it may have new parameters that did not get initialized appropriately)?
You are making a mountain out of nothing here. There are no problems at all, these are just warning messages, not errors, and the functionality of the icons is guaranteed. Otherwise an error would be reported.
These warnings simply inform about a change in the parameters of a process. In this particular case, several parameters of the PhotometricColorCalibration process no longer exist in the current version of this tool. Since these parameters have been serialized in the icons file, the core application informs about this fact with the corresponding warning messages. This is an automatic response to a detected change.
PixInsight is an always-evolving platform. Existing process parameters may change, be removed or replaced with new ones when a process is undergoing intense development. This is perfectly normal and will happen again. In the current version of PixInsight we have implemented a new star detection engine, which is much more robust and efficient. The new star detector introduces many new parameters and changes the meaning of some existing ones (such as sensitivity, peak response and maximum star distortion). All processes that depend on star detection have been adapted to the new detector, which involves parameter changes in most cases. PhotometricColorCalibration and SubframeSelector are two of these processes.
We take our work very seriously when we release a new version of PixInsight, or of any of its standard processes or scripts. If we remove process parameters or replace them with new ones, we always try to guarantee that no breaking change will happen. When this is not possible, we in general have two options: either inform about the changes that can be expected appropriately (see for example the description of the new star detector included in the official announcement for version1.8.9-1), or replace the process with a new one.
Other applications try to hide information to the user. This has never been and is not our philosophy of development. Our style is exactly the opposite: we always try to provide as much relevant information as possible to the user. If in doubt, we always prefer to take the risk of providing too much information instead of too few. The fact that a process parameter has been removed and is not available when an icons file is loaded is relevant, hence we issue a warning message to inform about it. Understanding the information provided by our platform is essential to work with PixInsight.
These warnings simply inform about a change in the parameters of a process. In this particular case, several parameters of the PhotometricColorCalibration process no longer exist in the current version of this tool. Since these parameters have been serialized in the icons file, the core application informs about this fact with the corresponding warning messages. This is an automatic response to a detected change.
PixInsight is an always-evolving platform. Existing process parameters may change, be removed or replaced with new ones when a process is undergoing intense development. This is perfectly normal and will happen again. In the current version of PixInsight we have implemented a new star detection engine, which is much more robust and efficient. The new star detector introduces many new parameters and changes the meaning of some existing ones (such as sensitivity, peak response and maximum star distortion). All processes that depend on star detection have been adapted to the new detector, which involves parameter changes in most cases. PhotometricColorCalibration and SubframeSelector are two of these processes.
We take our work very seriously when we release a new version of PixInsight, or of any of its standard processes or scripts. If we remove process parameters or replace them with new ones, we always try to guarantee that no breaking change will happen. When this is not possible, we in general have two options: either inform about the changes that can be expected appropriately (see for example the description of the new star detector included in the official announcement for version1.8.9-1), or replace the process with a new one.
Other applications try to hide information to the user. This has never been and is not our philosophy of development. Our style is exactly the opposite: we always try to provide as much relevant information as possible to the user. If in doubt, we always prefer to take the risk of providing too much information instead of too few. The fact that a process parameter has been removed and is not available when an icons file is loaded is relevant, hence we issue a warning message to inform about it. Understanding the information provided by our platform is essential to work with PixInsight.
Hey, no need to apologize. Of course this is technical. I understand why many people may not know how to handle warning and error messages and what they mean in context. From time to time it's good that this topic comes to light so that we can explain these important issues, which have to do with our philosophy of development. This type of discussion is great to have because it helps people understand what PixInsight is like.