Bug 397562

Summary: Sequence job CCD specification is not served
Product: [Applications] kstars Reporter: TallFurryMan <eric.dejouhanet>
Component: generalAssignee: Jasem Mutlaq <mutlaqja>
Status: RESOLVED FIXED    
Severity: major    
Priority: NOR    
Version: 2.9.7   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description TallFurryMan 2018-08-17 20:55:48 UTC 
Consider a sequence job file specifying a CCD on a multi-CCD setup.

When the sequence job is loaded in the Capture module, the CCD dropbox is properly set to the CCD name indicated in the XML file, but no capture characteristics are updated.

Particularly, if available CCDs don't have the same frame dimensions, the dimensions of the last CCD are retained, and most of the time end up wrong.

When the end-user manually selects the CCD from the dropbox, characteristics update properly. A workaround is to select the proper CCD in the dropbox manually, then to load the sequence job XML file that is using that CCD.
Comment 1 TallFurryMan 2018-08-17 20:59:29 UTC 
This issue prevents the Scheduler from processing jobs that make use of different CCDs. Example of such jobs is automation of darks for the guider and imager.

This issue would probably disappear by itself if we decide to have one Capture module per CCD in the setup (to provide the ability to process captures in parallel). In that case the sequence job would be loaded by the Scheduler in the Capture module corresponding to the CCD, and characteristics would always be proper.
Comment 2 TallFurryMan 2018-09-14 06:18:12 UTC 
Should be fixed by https://phabricator.kde.org/D15492