Bug 396182 - manual filter wheel or filter drawer option
Summary: manual filter wheel or filter drawer option
Status: REPORTED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: TallFurryMan
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-07-05 06:22 UTC by Tommy LKW
Modified: 2020-09-08 06:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tommy LKW 2018-07-05 06:22:56 UTC
Hi,

I am hoping Kstars can add manual filter wheel or filter drawer option for those who doesn't have EFW.

1. Manual Filter Wheel is used when we have a filter wheel that is not computer controlled, but
still want to have the benefit of the sequencing, file naming, and FITs headers found within EKOS.
2. We may setup the Manual Filter Wheel just like a normal filter wheel in the Filter Setup dialog in EKOS.
3. Whenever a filter change is requested a dialog box will pop up asking us to manually change the filter.
4. This dialog will pause the sequence and any other actions currently taking place until "OK" has been
clicked.
Comment 1 TallFurryMan 2018-08-23 11:06:38 UTC
I agree on adding a settings option to the Capture module to allow manual change of a filter.

If such option is set, a pop-up requesting the change would block the Capture module for the end-user to run the change, as stated in point 3 from the OP.

Point 1 can be handled with the Filter Wheel Simulator with no implementation change, as long as the request to the end-user is made before requesting the Simulator to change the filter (because that changes the state of the Capture module too soon). It is the responsibility of the end-user to configure the filter names in the Filter Wheel Simulator so that they match the sequence because that has an impact on capture storage files, as mentioned in point 1 from the OP. Proper numbering of the filter on the wheel is not needed, but is recommended for clarity.

Point 3 is already covered if we use the Filter Wheel Simulator.

Point 4 cannot be achieved, but actually only the Capture module requires operations to be blocked. That's probably what the OP meant anyway.

Default value must be disabled, no blocking of the Capture module for manual filter change.

Location of the option in the UI is not easy. We need an option that pertains to the Capture module, and related to the filter, so the first idea would be to implement it with a checkbox in the Filter Settings, under the focus offset table. While it might be easily forgotten here, the fact that a pop-up would remind the end-user of this option is probably enough.

Open question: in the implementation, are filter offsets relevant for a single filter selection, or general to all filters?

Open question: would it be interesting to have the feature even for automated filter wheels, to allow tinkering in that case too? (nothing in this post suggestions prevents this)
Comment 2 Tommy LKW 2018-08-23 11:57:27 UTC
Open question: in the implementation, are filter offsets relevant for a single filter selection, or general to all filters?

It is best if filter offsets relevant for single filter selection.
Comment 3 Tommy LKW 2018-09-05 14:09:28 UTC
Hi, sorry for asking. Any progress on this request so far? Thanks.
Comment 4 TallFurryMan 2018-09-05 15:04:00 UTC
No, no yet. That feature is properly specified, but we are busy fixing issues in the Scheduler.
Comment 5 Tommy LKW 2018-09-05 15:40:42 UTC
(In reply to TallFurryMan from comment #4)
> No, no yet. That feature is properly specified, but we are busy fixing
> issues in the Scheduler.

Thanks for the reply. Good to hear that. Thank you.
Comment 6 Andrew Crouthamel 2018-09-28 03:09:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Tommy LKW 2018-09-28 03:30:54 UTC
I have also no idea what is the progress of this request. It looks like it takes forever to fullfil the request. :( All depends on the Kstars developer now.
Comment 8 TallFurryMan 2018-09-28 13:02:40 UTC
Indeed it does depend on the free time of the handful of developers :)
We need to prioritize, and currently most of the work is fixing side-effects following the D-Bus changes. We won't introduce new features until the most serious ones are patched. But we will gladly review implementation patches.
Comment 9 TallFurryMan 2018-09-28 13:04:28 UTC
Marking reported, so that the ticket doesn't go away.
Comment 10 Tommy LKW 2018-09-28 16:27:42 UTC
Thank you.
Comment 11 TallFurryMan 2020-08-24 06:48:39 UTC
I am under the impression that this issue is still current.

There is a workaround that consists in adding a Filter Wheel Simulator with enough movement time to allow manual intervention.
Comment 12 Bug Janitor Service 2020-09-08 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 TallFurryMan 2020-09-08 06:41:33 UTC
Keeping reported, I didn't have bandwidth to check.