Conversation
elichad
left a comment
elichad
left a comment
There was a problem hiding this comment.
skimming through first, I tested the links for the COMPSs docs but I got 404 errors (and if I visit https://compss-doc.readthedocs.io/en/stable/ I don't see an Ecosystem section)
| url: https://pypi.org/project/pycompss-cli/ | ||
| subitems: | ||
| - name: Documentation | ||
| url: https://compss-doc.readthedocs.io/en/stable/Sections/04_Ecosystem/09_CLI/02_Usage.html#inspect-workflow-provenance |
There was a problem hiding this comment.
I get a 404 error at this link
| COMPSs provides a programming interface for the development of applications in Python/Java/C/C++/R, a runtime system that exploits the inherent parallelism of applications at execution time, and a rich ecosystem for the operation, monitoring, performance evaluation and integration with Jupyter/Jupyterlab. | ||
|
|
||
| The COMPSs runtime includes the capacity of automatically recording details of the application’s execution as metadata, also known as [Workflow Provenance](https://compss-doc.readthedocs.io/en/stable/Sections/05_Tools/04_Workflow_Provenance.html). The metadata is recorded in RO-Crate format, following [Workflow RO-Crate](https://w3id.org/workflowhub/workflow-ro-crate/1.0) and [Workflow Run Crate](https://www.researchobject.org/workflow-run-crate/) profiles. With workflow provenance, you are able to share not only your workflow application (i.e. the source code) but also your workflow run (i.e. the datasets used as inputs, and the outputs generated as results). | ||
| The COMPSs runtime includes the capacity of automatically recording details of the application’s execution as metadata, also known as [Workflow Provenance](https://compss-doc.readthedocs.io/en/stable/Sections/04_Ecosystem/05_Workflow_Provenance.html). The metadata is recorded in RO-Crate format, following [Workflow RO-Crate](https://w3id.org/workflowhub/workflow-ro-crate/1.0) and [Workflow Run RO-Crate](https://www.researchobject.org/workflow-run-crate/) profile collection. With workflow provenance, you are able to share not only your workflow application (i.e. the source code) but also your workflow run (i.e. the datasets used as inputs, the outputs generated as results, and rich information about every single task executed). |
There was a problem hiding this comment.
| Plenty of examples of COMPSs Workflows with enabled provenance recording can be found at [WorkflowHub](https://workflowhub.eu/workflows?filter%5Bworkflow_type%5D=pycompss) (filtering the browsing by 'COMPSs' workflow type). | ||
|
|
||
| In addition, the COMPSs User Manual has a dedicated section on [how to generate Workflow Provenance with COMPSs](https://compss-doc.readthedocs.io/en/stable/Sections/05_Tools/04_Workflow_Provenance.html). | ||
| In addition, the COMPSs User Manual has a dedicated section on [how to generate Workflow Provenance with COMPSs](https://compss-doc.readthedocs.io/en/stable/Sections/04_Ecosystem/05_Workflow_Provenance.html). |
There was a problem hiding this comment.
Hi Eli, thanks for checking all the links! I was a bit ahead of myself. Our documentation branch ready for the next release and currently online is 'major-update', but on thursday it will be moved to 'stable'. That's why I prepared all the links so when the stable version is updated, they will work. An example of current 'major-update':
https://compss-doc.readthedocs.io/en/major-update/Sections/04_Ecosystem/05_Workflow_Provenance.html
If you want, we can hold this for 2 days and check on thursday that every link works.
There was a problem hiding this comment.
Ahh, okay - then yes, let's hold until the links work, please let me know when your docs update is done
There was a problem hiding this comment.
Hey Eli!!! We advanced the release of the documentation. Links should be working now.
Let me know any issue.
2 participants
I have updated the COMPSs use case, with a description that matches the new features of the upcoming COMPSs 3.4 release. Resources and publications have also been updated.