https://bugs.kde.org/show_bug.cgi?id=424360
--- Comment #2 from mountainai...@outlook.com --- I believe this may be operating as designed. In the simulator tonight, I was able to reproduce the issue when I changed the temperature via INDI. Over the course of the night, cooling ambient temperatures will cause the camera temp to drop, invalidating darks in the library. Starting exposures can also cause the sensor temp to increase, having a similar effect in the other direction. There's no getting around matching your dark and light temperatures, but this is a real inconvenience. Over 20 minutes I had to put the cover on 7 or 8 times, and my temp threshold was set to 1°C. I wonder if there could be two settings for the dark library: a tighter tolerance for the cooled main imaging cam (0.5C, for example) and a looser setting (3°C, for example) for the uncooled guide cam. Would that wide range affect dark frame subtraction too much? In addition to the above idea, I would recommend allowing users to disable the auto-close option in the guiding module's "Cover the telescope in order to take a dark exposure" dialog. This way, the dark is not automatically taken when we're distracted in the field and do not put the telescope cover on. Some kind of persistent audio alert would be great, too -- to call attention to the issue in case the user is sleeping, working on another scope, etc. I think this can be closed unless you think the above ideas have merit. -- You are receiving this mail because: You are watching all bug changes.
