You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pipeline must be running on a graph service exposed on the network. For example, first, run the GraphService on an open port:
40
56
41
-
## Getting Started
57
+
`ezmsg --address 127.0.0.1:25978 start`
42
58
43
-
This package includes some entrypoints with useful tools.
59
+
Then run your usual pipeline but make sure it attaches to the graph address by passing `graph_address=("127.0.0.1", 25978)` as a kwarg to `ez.run`.
60
+
61
+
While the pipeline is running, you can run the signal-monitor tool with (`uv run`) `ezmsg-signal-monitor --graph-addr 127.0.0.1:25978`.
62
+
63
+
This launches a window with graph visualized on the left. Click on a node's output box to get a live visualization on the right side of the screen plotting the data as it leaves that node. Use `a` to toggle auto-scaling. With auto-scaling off, use `-`, and `=` to zoom out and in, respectively. See the [phosphor docs](https://www.ezmsg.org/phosphor/) for the full list of keyboard shortcuts.
64
+
65
+
> Currently only 2-D outputs are supported!
66
+
67
+
Don't forget to shutdown your graph service when you are done, e.g.: `ezmsg --address 127.0.0.1:25978 shutdown`
44
68
45
69
### ezmsg-performance-monitor
46
70
71
+
**DEPRECATED**
72
+
73
+
> ezmsg will soon includes a built-in performance monitor that can be used instead of this tool.
74
+
47
75
This tool operates on logfiles created by ezmsg. Logfiles will automatically be created when running a pipeline containing nodes decorated with `ezmsg.sigproc.util.profile.profile_subpub`,
48
76
and if the `EZMSG_LOGLEVEL` environment variable is set to DEBUG. The logfiles will be created in `~/.ezmsg/profile/ezprofiler.log` by default but this can be changed with the `EZMSG_PROFILE` environment variable.
49
77
@@ -52,25 +80,11 @@ You can decorate other nodes with `ezmsg.sigproc.util.profile.profile_subpub` to
52
80
53
81
During a run with profiling enabled, the logfiles will be created in the specified location. You may wish to additionally create a graph file: (`uv run`) `EZMSG_LOGLEVEL=WARN ezmsg mermaid > ~/.ezmsg/profile/ezprofiler.mermaid`
54
82
55
-
During or after a pipeline run with profiling enabled, you can run (`uv run `) `performance-monitor` to visualize the performance of the nodes in the pipeline.
83
+
During or after a pipeline run with profiling enabled, you can run (`uv run `) `ezmsg-performance-monitor` to visualize the performance of the nodes in the pipeline.
56
84
57
85
> Unlike `signal-monitor`, this tool does not require the pipeline to attach to an existing graph service because it relies exclusively on the logfile.
58
86
59
-
### ezmsg-signal-monitor
60
-
61
-
The pipeline must be running on a graph service exposed on the network. For example, first, run the GraphService on an open port:
62
-
63
-
`ezmsg --address 127.0.0.1:25978 start`
64
-
65
-
Then run your usual pipeline but make sure it attaches to the graph address by passing `graph_address=("127.0.0.1", 25978)` as a kwarg to `ez.run`.
66
-
67
-
While the pipeline is running, you can run the signal-monitor tool with (`uv run`) `signal-monitor --graph-addr 127.0.0.1:25978`.
68
-
69
-
This launches a window with graph visualized on the left. Click on a node's output box to get a live visualization on the right side of the screen plotting the data as it leaves that node. Use `a` to toggle auto-scaling. With auto-scaling off, use `-`, and `=` to zoom out and in, respectively.
70
-
71
-
> Currently only 2-D outputs are supported!
72
-
73
-
Don't forget to shutdown your graph service when you are done, e.g.: `ezmsg --address 127.0.0.1:25978 shutdown`
87
+
> This performance monitor is soon to be deprecated in favor of monitoring tools built-in to ezmsg.
74
88
75
89
## Developers
76
90
@@ -80,9 +94,9 @@ We use [`uv`](https://docs.astral.sh/uv/getting-started/installation/) for devel
80
94
2. Fork ezmsg-tools and clone your fork to your local computer.
81
95
3. Open a terminal and `cd` to the cloned folder.
82
96
4. Make sure `pygraphviz`[pre-requisites](#pre-requisites) are installed.
0 commit comments