Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Time to next step #2821

Open
utimcraig opened this issue Dec 13, 2018 · 2 comments
Open

Feature request: Time to next step #2821

utimcraig opened this issue Dec 13, 2018 · 2 comments
Labels
api Affects the `api` project app Affects the `app` project blocked Ticket or PR is blocked by other work feature Ticket is a feature request / PR introduces a feature

Comments

@utimcraig
Copy link

utimcraig commented Dec 13, 2018

overview

The currently the "Run time" is displayed when running a protocol.

image
It is known that this time does not actually correspond to the time from when the user pushed start protocol. It would be nice to have a "time to next step" or a "time to protocol is complete" timer that counts down.

current behavior

Currently timer does not really display a "useful to the user" time.

steps to reproduce

Load any protocol, calibrate, and push start.

expected behavior

I would like to have a display of the time until the next step in the protocol happens, and a time until the protocol is completed. In terms of precision of the time measurement, I would like to know if I can go get a coffee, or if I need to sit and watch the protocol go.

┆Issue is synchronized with this Wrike Task by Unito

@mcous mcous added feature Ticket is a feature request / PR introduces a feature app Affects the `app` project api Affects the `api` project blocked Ticket or PR is blocked by other work labels Dec 18, 2018
@mcous
Copy link
Contributor

mcous commented Dec 18, 2018

Hi @utimcraig, thanks for the feature request. This is something that has been on our minds for a long time but is not yet technically feasible due to the way the current system is architected. We'll follow up in this thread when we have actually have plans / timelines for this feature

@utimcraig
Copy link
Author

utimcraig commented Dec 18, 2018

@mcous Thanks. I'm guessing the dynamic time needed to fix this error 2822 would be the time that needs to be displayed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Affects the `api` project app Affects the `app` project blocked Ticket or PR is blocked by other work feature Ticket is a feature request / PR introduces a feature
Projects
None yet
Development

No branches or pull requests

2 participants