@@ -8,14 +8,14 @@ workflow executions, and to build distributions of workflow execution behaviors,
88which are used to evaluate methods and techniques in simulation or in real
99conditions.
1010
11- The first axis of the WorkflowHub project targets the analysis of actual workflow
11+ The first axis of the WfCommons project targets the analysis of actual workflow
1212execution traces (i.e., the workflow execution profile data and characterizations)
1313in order to build **recipes ** of workflow applications. These recipes contain
1414the necessary information for generating synthetic, yet realistic, workflow
1515traces that resemble the structure and distribution of the original workflow
1616executions.
1717
18- A `list of workflow execution traces <https://workflowhub .org/traces.html >`_
18+ A `list of workflow execution traces <https://wfcommons .org/traces.html >`_
1919that are compatible with :ref: `json-format-label ` is kept constantly updated
2020in our project website.
2121
@@ -24,45 +24,45 @@ Workflow Execution Traces
2424
2525A workflow execution trace represents an actual execution of a scientific
2626workflow on a distributed platform (e.g., clouds, grids, HPC, etc.). In the
27- WorkflowHub project, a trace is represented in a JSON file following the
27+ WfCommons project, a trace is represented in a JSON file following the
2828schema described in :ref: `json-format-label ` section. This Python package
2929provides a *trace loader * tool for importing workflow execution traces
3030for analysis. For instance, the code snippet below shows how a trace can
31- be loaded using the :class: `~workflowhub .trace.trace.Trace ` class: ::
31+ be loaded using the :class: `~wfcommons .trace.trace.Trace ` class: ::
3232
33- from workflowhub import Trace
33+ from wfcommons import Trace
3434 trace = Trace(input_trace='/path/to/trace/file.json')
3535
36- The :class: `~workflowhub .trace.trace.Trace ` class provides a number of
36+ The :class: `~wfcommons .trace.trace.Trace ` class provides a number of
3737methods for interacting with the workflow trace, including:
3838
39- - :meth: `~workflowhub .trace.trace.Trace.draw `: produces an image or a pdf file representing the trace.
40- - :meth: `~workflowhub .trace.trace.Trace.leaves `: gets the leaves of the workflow (i.e., the tasks without any successors).
41- - :meth: `~workflowhub .trace.trace.Trace.roots `: gets the roots of the workflow (i.e., the tasks without any predecessors).
42- - :meth: `~workflowhub .trace.trace.Trace.write_dot `: writes a dot file of the trace.
39+ - :meth: `~wfcommons .trace.trace.Trace.draw `: produces an image or a pdf file representing the trace.
40+ - :meth: `~wfcommons .trace.trace.Trace.leaves `: gets the leaves of the workflow (i.e., the tasks without any successors).
41+ - :meth: `~wfcommons .trace.trace.Trace.roots `: gets the roots of the workflow (i.e., the tasks without any predecessors).
42+ - :meth: `~wfcommons .trace.trace.Trace.write_dot `: writes a dot file of the trace.
4343
4444The Trace Analyzer
4545------------------
4646
47- The :class: `~workflowhub .trace.trace_analyzer.TraceAnalyzer ` class provides
47+ The :class: `~wfcommons .trace.trace_analyzer.TraceAnalyzer ` class provides
4848a number of tools for analyzing collection of workflow execution traces. The
49- goal of the :class: `~workflowhub .trace.trace_analyzer.TraceAnalyzer ` is to
49+ goal of the :class: `~wfcommons .trace.trace_analyzer.TraceAnalyzer ` is to
5050perform analyzes of one or multiple workflow execution traces, and build
5151summaries of the analyzes per workflow' task type prefix.
5252
5353.. note ::
5454
5555 Although any workflow execution trace represented as a
56- :class: `~workflowhub .trace.trace.Trace ` object (i.e., compatible with
56+ :class: `~wfcommons .trace.trace.Trace ` object (i.e., compatible with
5757 :ref: `json-format-label `) can be appended to the
58- :class: `~workflowhub .trace.trace_analyzer.TraceAnalyzer `, we strongly
58+ :class: `~wfcommons .trace.trace_analyzer.TraceAnalyzer `, we strongly
5959 recommend that only traces of a single workflow application type be
6060 appended to an analyzer object. You may though create several analyzer
6161 objects per workflow application.
6262
63- The :meth: `~workflowhub .trace.trace_analyzer.TraceAnalyzer.append_trace ` method
63+ The :meth: `~wfcommons .trace.trace_analyzer.TraceAnalyzer.append_trace ` method
6464allows you to include traces for analysis. The
65- :meth: `~workflowhub .trace.trace_analyzer.TraceAnalyzer.build_summary ` method
65+ :meth: `~wfcommons .trace.trace_analyzer.TraceAnalyzer.build_summary ` method
6666processes all appended traces. The method applies probability distributions fitting
6767to a series of data to find the *best * (i.e., minimizes the mean square error)
6868probability distribution that represents the analyzed data. The method returns
@@ -94,8 +94,8 @@ in which themselves are used to :ref:`generate realistic synthetic workflow trac
9494<generating-workflows-label>`.
9595
9696Probability distribution fits can also be plotted by using the
97- :meth: `~workflowhub .trace.trace_analyzer.TraceAnalyzer.generate_fit_plots ` or
98- :meth: `~workflowhub .trace.trace_analyzer.TraceAnalyzer.generate_all_fit_plots `
97+ :meth: `~wfcommons .trace.trace_analyzer.TraceAnalyzer.generate_fit_plots ` or
98+ :meth: `~wfcommons .trace.trace_analyzer.TraceAnalyzer.generate_all_fit_plots `
9999methods -- plots will be saved as :code: `png ` files.
100100
101101Examples
@@ -108,7 +108,7 @@ distribution fitting for task *prefixes* of the Seismology workflow
108108plots (runtime, and input and output files) into the :code: `fits ` folder using
109109:code: `seismology ` as a prefix for each generated plot: ::
110110
111- from workflowhub import Trace, TraceAnalyzer
111+ from wfcommons import Trace, TraceAnalyzer
112112 from os import listdir
113113 from os.path import isfile, join
114114
0 commit comments