Comments (12)
Cool, did some reading on the links to catch up -- and thanks to Jeff Gentry for explaining CWLProv a little more deeply. My own thoughts are that these are really good best practices from the perspective of leveraging features of the http spec. If I put myself in the mindset of someone who runs workflows a lot, I'd absolutely need logs of my workflow run and a link to that log (whether it looks like a provenance object or not) and I'd expect a link to those logs directly in the API response (not just header, which I may never even know to check as comp bio rather than software engineer). So I see the logs as a necessity in the spec and the provenance_uri a bonus/competitive feature for providing structured details for debugging/tracking.
So it sounds like think this is something to add to WES documentation as a recommendation rather than a spec change. let me know if I misunderstood!
from workflow-execution-service-schemas.
This is a clever usage of the feature that helps with the last leg of a workflow execution. I think it will require modification directly of the OpenAPI description.
from workflow-execution-service-schemas.
I'm pro-provenance in general, but would need some more details on what this might look like in the spec. Tagging as a v2.0 candidate for now.
from workflow-execution-service-schemas.
To be more specific, the returned value would be the IRI/URI to a v0.6.0 or newer CWLProv ResearchObject https://w3id.org/cwl/prov/0.6.0
from workflow-execution-service-schemas.
@mr-c to clarify for my sake -- your suggestion enables something like:
- I'm doing a status check on a workflow
- I see the status is a failure
- Linked to the status through "provenance-uri" is the actual http link to the raw workflow definition associated to the failure -- which I can go to investigate?
- ....
from workflow-execution-service-schemas.
@ruchim Almost, for step 3 the URI points to a CWLProv document that would give detailed information, not the workflow definition (which one assumes the caller of the API already has a copy of)
from workflow-execution-service-schemas.
ahhh! is the provenance-uri the same as stdout/stderr logs -- or something else? also, thanks so much for the quick response, really appreciate it.
from workflow-execution-service-schemas.
The provinance-uri would point to a CWLProv format document which would contain structured data including raw logs, server information, etc.. 🙂👍
from workflow-execution-service-schemas.
I think from https://www.w3.org/TR/prov-aq/#resource-accessed-by-http in PROV we kind of allowed any kind of provenance document, although one containing PROV in one of the several formats would be preferable.
I would not require all in CWLProv - that is kind of the inside of the workflow and could be exposed as well if present as a Research Object BagIt archive (as it would be multiple files) or as a directory of files exposed through the WES - there is no single "CWLProv document" as such, we have both primary.cwlprov.*
in multiple serializations, or metadata/manifest.json that types and links to all the other files.
Perhaps WES would have its own "outer" provenance that just says when the workflow job started/stopped and ideally links to its outputs?
from workflow-execution-service-schemas.
just poking @stain @mr-c @david4096 for any opinions to my comment above!
from workflow-execution-service-schemas.
@ruchim Yep, it can go in the header and in the body of the response, agreed!
from workflow-execution-service-schemas.
excellent, I'll mark this as a documentation change.
from workflow-execution-service-schemas.
Related Issues (20)
- Add API call for workflow and inputs validation HOT 2
- Support passing TRS URIs to workflow_url HOT 4
- Input and Output Format Specification HOT 22
- Migrate build docs over to github actions
- Semantics of error states ambiguous HOT 2
- CWL: support for uploading (private) containers HOT 12
- Add Workflow engine and version to RunWorkflow parameters HOT 11
- WES API clients HOT 1
- Separate default engine parameters for different engines in the service info HOT 2
- Proposal: New WES State for Preemption HOT 1
- Optional ServiceInfo on supported workflows HOT 10
- No tag/release for version 1.0.1 HOT 24
- Versioned documentation
- Default branch & release model HOT 4
- Integrate OpenAPI validator into CI
- Field for run/task error messages (beyond stderr) HOT 8
- Workflow file authorization HOT 6
- Rerun workflows HOT 3
- Add unique identifier and additional information to tasks HOT 12
- In which field of the wes interface should the logs of the Cromwell engine and the tes server be reflected? HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from workflow-execution-service-schemas.