Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
L
loom
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Tom Vander Aa
loom
Commits
c9e74092
Commit
c9e74092
authored
8 years ago
by
Ada Böhm
Browse files
Options
Downloads
Patches
Plain Diff
DOC: Reporting updated
parent
a5112063
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/source/client-py.rst
+9
-29
9 additions, 29 deletions
doc/source/client-py.rst
doc/source/conf.py
+2
-2
2 additions, 2 deletions
doc/source/conf.py
with
11 additions
and
31 deletions
doc/source/client-py.rst
+
9
−
29
View file @
c9e74092
...
@@ -395,49 +395,29 @@ Reports
...
@@ -395,49 +395,29 @@ Reports
-------
-------
Reporting system serves for debugging and profiling the Loom programs.
Reporting system serves for debugging and profiling the Loom programs.
Report can be
creat
ed by ``s
ubmit
`` method
by the
follow
ing way
::
Report
s
can be
enabl
ed by ``s
et_trace
`` method
as
follow
s
::
task = ...
task = ...
client.submit(task, "myreport.report")
client.set_trace("/path/to/mytrace")
client.submit(task)
It creates report file `myreport.report`. This file can be explored by ``loom.rview``.
The path provided to ``set_trace`` has to be placed on a network filesystem that
is visible to server and all workers. It creates a directory
``/path/to/mytrace`` where server and workers writes its traces.
The
following command shows graph of the plan:
The
trace can be explored by ``loom.lore``.
::
::
$ python3 -m loom.rview myreport.report --show-graph
$ python3 -m loom.lore /path/to/mytrace
The following command shows tracelog of tasks (how long and where each tasks was
executed):
::
$ python3 -m loom.rview myreport.report --show-trace
The following command generates summary plan execution report in HTML:
::
$ python3 -m loom.rview myreport.report --html-report
It creates file *output.html* that contains the final report.
The full list of commands can be obtained by
The full list of commands can be obtained by
::
::
$ python3 -m loom.rview --help
$ python3 -m loom.rview --help
In the example above, we have created report by ``submit``. It is possible to
create a report without submitting a task by
:py:func:`loom.client.make_dry_report`. The report created by this way contains
a graph of tasks, but does not contain runtime information (since the task was
not executed)::
from loom.client import make_dry_report
task = ...
make_dry_report(task, "myreport.report")
Labels
Labels
------
------
...
...
This diff is collapsed.
Click to expand it.
doc/source/conf.py
+
2
−
2
View file @
c9e74092
...
@@ -64,9 +64,9 @@ author = u'Loom Team'
...
@@ -64,9 +64,9 @@ author = u'Loom Team'
# built documents.
# built documents.
#
#
# The short X.Y version.
# The short X.Y version.
version
=
u
'
0.
4
'
version
=
u
'
0.
6
'
# The full version, including alpha/beta/rc tags.
# The full version, including alpha/beta/rc tags.
release
=
u
'
0.
2
'
release
=
u
'
0.
6
'
# The language for content autogenerated by Sphinx. Refer to documentation
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
# for a list of supported languages.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment