migrating to wfcommons

wfcommons · Mar 9, 2021 · 1500f25 · 1500f25
1 parent aa07651
commit 1500f25
Show file tree

Hide file tree

Showing 9 changed files with 21 additions and 21 deletions.
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
@@ -21,12 +21,12 @@ jobs:
  - name: Check validity of traces
  run: |
  find . -type f -name "*.json" > traces.txt && err=0
- git clone https://github.com/workflowhub/workflow-schema
+ git clone https://github.com/wfcommons/workflow-schema
  err_report() {
  echo "Error on trace file $1"
  }
  trap 'err_report ${trace_file}' ERR;
  for trace_file in `cat traces.txt`; do
- python3 ./workflow-schema/workflowhub-validator.py -d ${trace_file};
+ python3 ./workflow-schema/wfcommons-validator.py -d ${trace_file};
  echo "";
  done
diff --git a/1000genome/README.md b/1000genome/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for 1000Genome Workflow
@@ -45,7 +45,7 @@ performance metrics can be found in the following research publication:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema) for
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema) for
 describing workflow executions. Execution traces from different computing
 platforms are organized into sub-folders.
 

diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
-![Build](https://github.com/workflowhub/pegasus-traces/workflows/Build/badge.svg)
+![Build](https://github.com/wfcommons/pegasus-traces/workflows/Build/badge.svg)
 
-<a href="https://workflowhub.org" target="_blank"><img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" /></a>
+<a href="https://wfcommons.org" target="_blank"><img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" /></a>
 
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
@@ -9,7 +9,7 @@
 This repository contains workflow execution traces generated from
 [Pegasus](http://pegasus.isi.edu) workflow executions. The traces
 hosted in this repository use the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema)
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema)
 for describing workflow executions.
 
 #### Repository Structure
@@ -22,8 +22,8 @@ _computing platforms_.
 #### Workflow Simulator
 
 The execution traces provided in this repository are compatible to any
-[simulator framework](https://workflowhub.org/simulator.html) that implements
-the [WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema).
+[simulator framework](https://wfcommons.org/simulators) that implements
+the [WfCommons JSON format](https://github.com/wfcommons/workflow-schema).
 
 ## Summary of Workflow Execution Traces
 

diff --git a/cycles/README.md b/cycles/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for Cycles Workflow
@@ -43,7 +43,7 @@ performance metrics can be found in the following research publication:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema)
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema)
 for describing workflow executions. Execution traces from different
 computing platforms are organized into sub-folders.
 

diff --git a/epigenomics/README.md b/epigenomics/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for Epigenomics Workflow
@@ -41,7 +41,7 @@ performance metrics can be found in the following research publication:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema)
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema)
 for describing workflow executions. Execution traces from different
 computing platforms are organized into sub-folders.
 

diff --git a/montage/README.md b/montage/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for Montage Workflow
@@ -45,7 +45,7 @@ performance metrics can be found in the following research publication:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema) for
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema) for
 describing workflow executions. Execution traces from different computing
 platforms are organized into sub-folders.
 

diff --git a/seismology/README.md b/seismology/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for Seismic Cross Correlation Workflow
@@ -37,7 +37,7 @@ publication:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema)
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema)
 for describing workflow executions. Execution traces from different
 computing platforms are organized into sub-folders.
 

diff --git a/soykb/README.md b/soykb/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for Soybean Workflow (SoyKB)
@@ -48,7 +48,7 @@ performance metrics can be found in the following research publication:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema)
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema)
 for describing workflow executions. Execution traces from different
 computing platforms are organized into sub-folders.
 

diff --git a/srasearch/README.md b/srasearch/README.md
@@ -1,4 +1,4 @@
-<img src="https://workflowhub.org/assets/images/logo-horizontal.png" width="300" />
+<img src="https://wfcommons.org/images/wfcommons-horizontal.png" width="350" />
 <img src="https://pegasus.isi.edu/wordpress/wp-content/uploads/2015/12/logo-dark.png" width=200 style="float: right" />
 
 # Execution Traces for SRA Search Workflow
@@ -27,7 +27,7 @@ The figure below shows an overview of the SRA Search workflow structure:
 ## Execution Traces
 
 Execution traces are formatted according to the
-[WorkflowHub JSON format](https://github.com/workflowhub/workflow-schema) for
+[WfCommons JSON format](https://github.com/wfcommons/workflow-schema) for
 describing workflow executions. Execution traces from different computing
 platforms are organized into sub-folders.