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

Add execution status tracking #564

Closed
adelavega opened this issue May 13, 2019 · 2 comments
Closed

Add execution status tracking #564

adelavega opened this issue May 13, 2019 · 2 comments

Comments

@adelavega
Copy link
Collaborator

adelavega commented May 13, 2019

Add a link to neurovault collection for results.

GET /api/analyses/{id}/uploads and take the collection id of the latest upload. Or alternatively, show a list of uploads.

Might want to show status as well (or at least show "pending" if only existing one is "pending").

@adelavega
Copy link
Collaborator Author

@rwblair and I just discussed this.

The idea will be for the upload attempts ("Execution status") to be displayed in a stack below the compilation status in the Status tab.

This section willl look for results in get_uploads. It will display all of the successful attempts, as well as the most non-successful status. They will be displayed as colored cards of status boxes.

While the frontend changes won't depend on this, in the future I will also add more status updating to the cli and celery, so that the following is logged:

  • When an analysis is started
  • When fitlins is completed (and if its failed, succeeded) (maybe could be merged with the following status update)
  • When images are uploaded to NS (also, if it fails, CLI should ask if the user wants to try again).
  • When images are uploaded to NV. At this point, if successful the status will have a collection_id which can be displayed at linked.

So essentially, this is going to be become a "execution status" which may or may not have a NV collection_id associated with it (only upon success).

@adelavega adelavega added this to To Do (Frontend) in 0.9 via automation May 14, 2019
@rwblair rwblair moved this from To Do (Frontend) to In Progress in 0.9 Jun 4, 2019
@adelavega adelavega changed the title Link to NeuroVault results from frontend Add execution status tracking Jun 6, 2019
@adelavega adelavega moved this from In Progress to To Do (Frontend) in 0.9 Jun 21, 2019
@adelavega adelavega moved this from To Do (Frontend) to To Do (Backend) in 0.9 Jun 26, 2019
@adelavega adelavega removed this from To Do (Backend) in 0.9 Jun 26, 2019
@adelavega
Copy link
Collaborator Author

I'm closing this as not needed. I think its fine for it to only update when the final results are available.

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

No branches or pull requests

1 participant