KStars issueshttps://invent.kde.org/education/kstars/-/issues2023-07-14T16:31:55Zhttps://invent.kde.org/education/kstars/-/issues/155Failure strategy2023-07-14T16:31:55ZJasem MutlaqFailure strategyWe need to adopt a more formal failure strategy for transient operations. Basically, any transient operation can result in three outcomes:
1. Success
2. Failure
3. Timeout
As a long term goal, I believe we should encapsulate any such tr...We need to adopt a more formal failure strategy for transient operations. Basically, any transient operation can result in three outcomes:
1. Success
2. Failure
3. Timeout
As a long term goal, I believe we should encapsulate any such transient requests in an object container and specify what happens exactly in of the three cases. This would probably require a lot of asynchronous design re-tooling for functions that expect synchronous responses.
This issue is prevalent most in Guide and Focus modules, where sometimes the module keeps retrying almost indefinitely without actually failing. This might not allow external controls (e.g. scheduler) to take corrective actions to reset the sequence. Please share your thoughts on this. Shall we begin by ensuring the modules DO fail when they need to instead of retrying needlessly, or shall we work on creating the infrastructure for transient operations and then apply such cases to it?
@murveit @wreissenberger @edejouhanetv3.6.4Jasem MutlaqJasem Mutlaqhttps://invent.kde.org/education/kstars/-/issues/95Exchangeable data block representing capture parameters2022-01-03T07:00:39ZEric DejouhanetExchangeable data block representing capture parametersWe observe that multiple Ekos modules embed the ability to capture a single frame. Implementation after implementation, the parameters describing the capture diverge between those modules. For instance, the Capture module has a very deta...We observe that multiple Ekos modules embed the ability to capture a single frame. Implementation after implementation, the parameters describing the capture diverge between those modules. For instance, the Capture module has a very detailed list of parameters, and includes groups of INDI properties that can be applied. The Align module, on the opposite, only has binning, exposure and gain.
One solution is that we use a set of profiles for capture characteristics that may be stored, exchanged and referred to by modules. Those profiles would work the same way as detection profiles for the Focus module, and ensure proper reconfiguration for each capture.
Another solution is to use Sequence files generated by the Capture module for exposure operations in other modules. Obviously, Sequence files may contain multiple instances of capture parameters, but this is easy to overcome and that property could even be useful in some cases.v3.5.8