-
Notifications
You must be signed in to change notification settings - Fork 78
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
Provide Job Name in submitterDID submitting a Job to sciserver compute?? #1830
Comments
This is a good idea but will require a little thought about what sort of additional metadata will be useful for job creation. (It would be good to update the compute client interface for Maybe "name" is the only thing we care about but it's possible that other info could be of interest in the future. If there is additional info in the future, it might be good to simply create a Anyway, the short answer is that this is a good idea but requires modification of the compute adapter interface. Although it is only a minor change, it would be nice to think about it carefully before adding it to prevent an annoying or confusing interface in the future. |
It might be nice to revamp the JobOriginsAPI in favor of a richer compute API as the JobOriginsAPI is tied to the GME executor framework. One tricky thing is that interactive compute will not have an associated job, pipeline, etc. Maybe we should have them as optional? Something like the following for interactive compute sessions:
or
The WebGME Executor Framework compute client would need to record the latter metadata info in the database for use with the compute dashboard (or it could simply be changed to show a name like SciServer compute's dashboard). |
It might be nice to submit a Job in
sciserver-compute
with its name, it will be easier to debug in dashboard when executing apipeline
with multiple jobs. However, there's no clear advantage other than that.The text was updated successfully, but these errors were encountered: