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.

Sign up for GitHub

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

Jump to bottom

Add TaskProvenance node with relationship to both a ProtocolDAGResultRef and its associated Task upon error or complete #106

Open
dotsdl opened this issue Mar 28, 2023 · 1 comment · May be fixed by #114
Open

Add TaskProvenance node with relationship to both a ProtocolDAGResultRef and its associated Task upon error or complete #106

dotsdl opened this issue Mar 28, 2023 · 1 comment · May be fixed by #114
Milestone
Release 0.7.0 - "...

Comments

@dotsdl
Copy link
Member

dotsdl commented Mar 28, 2023

We would like to hold on to metadata on when a ProtocolDAGResultRef was created, in particular information on the compute service identity that executed it, when execution started, when it completed, etc. This should be a separate TaskProvenance node with direct relationships to both the ProtocolDAGResultResultRef it corresponds to and the associated Task.
@dotsdl dotsdl added this to the Release 0.3.0 milestone Mar 28, 2023
@dotsdl dotsdl linked a pull request Apr 4, 2023 that will close this issue
Open
@dotsdl
Copy link
Member Author

dotsdl commented Apr 15, 2024

We also want to grab host information if possible; I believe QCEngine does this, allowing QCFractal to hold on to this information. We can reference their approach for our own implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Release 0.7.0 - "living networks" and...
Development

Successfully merging a pull request may close this issue.

[WIP] Adding TaskProvenance usage to compute execution and results OpenFreeEnergy/alchemiscale
1 participant
@dotsdl