smart-underworld
commented
5 days ago I started a feature branch to work on this, and have finalized the logic. Key parameter will be panel_time_sec.
In federation mode mosaic, there will be a parameter for max_devices_used. If set to 1, then everything is normal meaning a mosaic item will be sent to the first available device. No mosaic splitting will be done.
If max_devices_used > 1, then one can choose 1 of 2 split modes: split_panels or split_time.
Split_panels will split all selected panels across available devices up to max count.
Split_time will have each available device acquired the full set of selected panels, but acquisition time for each will be reduced by this same factor (num_devices_used)
I should finish my implementation for ALP tomorrow. Changes to SSC will be need, and may be wrapped into your schedule refactoring.
A heads up on an upcoming change to mosaic setting. The session time will be changed to panel collection time. This means Alp will attempt to spend this much time collectively to capture data for each panel, keeping in mind how to divide the task among Seestars in the federation, or if selected panels is set.
SSC will attempt to display the estimated run time when a schedule starts.