Comments (4)
This should probably be "How long did this workflow take to run?" It only seems useful if accompanied by information on the computing infrastructure used for the run.
from workflow-run-crate.
This should probably be "How long did this workflow take to run?"
The "does" vs "did" here is similar to the discussion on resource usage in #10: "does" implies a prior knowledge from some statistics while "did" is simply a statement of fact regarding the represented run. The answer to the latter is simply to subtract the startTime
from the endTime
, so I guess the description for this issue also needs to be clarified.
from workflow-run-crate.
the description for this issue also needs to be clarified
Done
from workflow-run-crate.
It only seems useful if accompanied by information on the computing infrastructure used for the run.
Yes, and that's why including a meaningful estimated running time is probably too complicated. That would have to refer to an average system, but what exactly is an average system? Even assuming such a system could be identified, its details would have to be included, but it would need to be clear that they refer to a hypotetical system where the workflow is supposed to run in the specified amount of time, and not to the actual system where the run described in the crate took place. The actual running time given by endTime
- startTime
is sufficient to get an idea of the order of magnitude. I am therefore closing this as the information is already represented in the profiles.
from workflow-run-crate.
Related Issues (20)
- CQ2 - Resource usage HOT 25
- CQ3 - Configuration files HOT 5
- CQ4 - environment/container file HOT 16
- CQ5 - Step running time HOT 2
- CQ7 - Outcome HOT 5
- CQ8 - Workflow inputs and outputs HOT 2
- CQ9 - Software version
- CQ10 - Tool wrappers HOT 6
- cwlprov_to_crate: support for nested workflows HOT 1
- cwlprov_to_crate: test converting cwlprovs created for each CWL conformance tests HOT 6
- CQ11 - Parameter connections HOT 4
- Resource requirements HOT 3
- Representing conditional execution HOT 7
- Representing secondary files HOT 2
- Representing environment variables HOT 5
- Content negotiation is not enabled for the profiles HOT 11
- How to represent which compute provider was used? HOT 6
- Remove individual roterms from profile crates
- Citing the profiles HOT 2
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-run-crate.