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

Operation Progress #41

Closed
MattReimer opened this Issue Feb 7, 2018 · 9 comments

Comments

@MattReimer
Copy link
Member

MattReimer commented Feb 7, 2018

We need some sort of progress for long-running processes.

It doesn't have to be fancy but we need the used to know things are happening.

Cancellation can happen at a later date

@MattReimer MattReimer added this to the GCD 7.0.05 milestone Feb 7, 2018

@MattReimer MattReimer self-assigned this Feb 7, 2018

@MattReimer

This comment has been minimized.

Copy link
Member

MattReimer commented Feb 20, 2018

Since we speed up the rasterize ion this is much lower priority. Let's push it

@MattReimer MattReimer modified the milestones: GCD 7.0.05, GCD 7.1.0 FC Feb 20, 2018

@philipbaileynar philipbaileynar modified the milestones: GCD 7.1.0 FC, GCD X.X.X Next Version Mar 5, 2018

@joewheaton

This comment has been minimized.

Copy link
Contributor

joewheaton commented Mar 7, 2018

I still want my request for:

  • Status bar...
  • and running log of what step in process I'm at (e.g. for a simple process like calculating error grid for a mask, things like Creating Error Raster..... Calculating Error Values for FIS in Mask 1.... Assigning Spatially Uniform Error Values in Mask 2... etc. This is really important as it helps in trouble shooting and expectation management and educating users. Not sure if I'm missing this put somewhere else?

WE DO NOT currently manage user's expectations well when something is going to take a while. I appreciate how much work was done to make operations smooth and clean, but you have not tested these operations on bigger datasets.

@philipbaileynar

This comment has been minimized.

Copy link
Contributor

philipbaileynar commented Mar 7, 2018

@joewheaton agreed... we have some really good ideas. This can't happen before the April workshop.

@MattReimer MattReimer removed their assignment Mar 19, 2018

@philipbaileynar philipbaileynar moved this from Temp to Big in Post Workshop Breakdown May 16, 2018

@MattReimer

This comment has been minimized.

Copy link
Member

MattReimer commented May 17, 2018

Discussed on May 17 with @JamesSLC and @joewheaton

We decided that the most important thing is to simply give the user some indication that something is still processing.

@joewheaton

This comment has been minimized.

Copy link
Contributor

joewheaton commented May 29, 2018

This is @jb10016 top 4 priority (2 of 4).

@MattReimer

This comment has been minimized.

Copy link
Member

MattReimer commented Aug 20, 2018

FYI here is a sample of what the events look like when they come in:

3 variables: State(enum), Message(string), Progress(int)

These get initialized separately so yo need to account for that. Either wait for all 3 to come in before showing them or progressively populate the statusbar.

Event1:: 'Initialized', '', -1
Event2:: 'Initialized', 'Running Test Event', -1
Event3:: 'Started', 'Running Test Event', -1
Event4:: 'Started', 'Running Test Event', 0
Event5:: 'Started', 'Running Test Event', 1
Event6:: 'Started', 'Running Test Event', 2
...
Event7:: 'Started', 'Running Test Event', 100
Event8:: 'Complete', 'Running Test Event', 100

MattReimer added a commit that referenced this issue Aug 21, 2018

MattReimer added a commit that referenced this issue Aug 21, 2018

MattReimer added a commit that referenced this issue Aug 21, 2018

MattReimer added a commit that referenced this issue Aug 21, 2018

MattReimer added a commit that referenced this issue Aug 21, 2018

philipbaileynar added a commit that referenced this issue Aug 22, 2018

philipbaileynar added a commit that referenced this issue Aug 22, 2018

@joewheaton

This comment has been minimized.

Copy link
Contributor

joewheaton commented Aug 22, 2018

Really great compromise in https://youtu.be/we2vun_V5IE for some great, useful functionality within budget. Looks great. Nice work gents!

@jb10016

This comment has been minimized.

Copy link
Collaborator

jb10016 commented Aug 23, 2018

@philipbaileynar @MattReimer @joewheaton I like it - works well, and good to plot the label identifying the task, which at least enables the user to get a sense of where things are at. Great work!

@MattReimer

This comment has been minimized.

Copy link
Member

MattReimer commented Aug 23, 2018

TEsted and the async issue has been solved. Closing

@MattReimer MattReimer closed this Aug 23, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment