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
-[Configuring Score-P in Jupyter](#configuring-score-p-in-jupyter)
32
+
-[Vampir Launch Control](#vampir-launch-control)
32
33
-[Multi-Cell Mode](#multi-cell-mode)
33
34
-[Write Mode](#write-mode)
35
+
-[Logging Configuration](#logging-configuration)
34
36
-[Presentation of Performance Data](#presentation-of-performance-data)
35
37
-[Limitations](#limitations)
36
38
-[Serialization Type Support](#serialization-type-support)
37
39
-[Overhead](#overhead)
38
-
-[Logging Configuration](#logging-configuration)
39
40
-[Future Work](#future-work)
40
41
-[Citing](#citing)
41
42
-[Contact](#contact)
@@ -131,7 +132,22 @@ Executes a cell with Score-P, i.e. it calls `python -m scorep <cell code>`
131
132
132
133

133
134
135
+
### Vampir Launch Control
136
+
137
+
To automatically launch **Vampir** after a cell with Score-P instrumentation, use:
138
+
139
+
```
140
+
%%enable_vampir_launch_on_scorep_instrumented
141
+
```
134
142
143
+
This will cause the kernel to open `traces.otf2` in Vampir (if found) after the next instrumented cell.
144
+
To disable this behavior again:
145
+
146
+
```
147
+
%%disable_vampir_launch
148
+
```
149
+
150
+
By default, Vampir launching is disabled. You must enable it explicitly when needed.
135
151
136
152
## Multi-Cell Mode
137
153
You can also treat multiple cells as one single cell by using the multi cell mode. Therefore you can mark the cells in the order you wish to execute them.
@@ -186,6 +202,23 @@ Stops the marking process and writes the marked cells in a Python script. Additi
186
202
187
203

188
204
205
+
## Logging Configuration
206
+
To adjust logging and obtain more detailed output about the behavior of the scorep_jupyter kernel, refer to the `src/logging_config.py` file.
207
+
This file contains configuration options for controlling the verbosity, format, and destination of log messages. You can customize it to suit your debugging needs.
208
+
209
+
Log files are stored in the following directory:
210
+
```
211
+
scorep_jupyter_kernel_python/
212
+
├── logs_scorep_jupyter/
213
+
│ ├── debug.log
214
+
│ ├── info.log
215
+
└── └── error.log
216
+
```
217
+
In some cases, you may want to suppress tqdm messages that are saved to error.log (since tqdm outputs to stderr). This can be done using the following environment variable:
218
+
```
219
+
%env TQDM_DISABLE=1
220
+
```
221
+
189
222
190
223
# Presentation of Performance Data
191
224
@@ -205,23 +238,6 @@ Similar yields for cloudpickle. Use the `%%marshalling_settings` magic command t
205
238
206
239
When dealing with big data structures, there might be a big runtime overhead at the beginning and the end of a Score-P cell. This is due to additional data saving and loading processes for persistency in the background. However this does not affect the actual user code and the Score-P measurements.
207
240
208
-
## Logging Configuration
209
-
To adjust logging and obtain more detailed output about the behavior of the scorep_jupyter kernel, refer to the `src/logging_config.py` file.
210
-
This file contains configuration options for controlling the verbosity, format, and destination of log messages. You can customize it to suit your debugging needs.
211
-
212
-
Log files are stored in the following directory:
213
-
```
214
-
scorep_jupyter_kernel_python/
215
-
├── logs_scorep_jupyter/
216
-
│ ├── debug.log
217
-
│ ├── info.log
218
-
└── └── error.log
219
-
```
220
-
In some cases, you may want to suppress tqdm messages that are saved to error.log (since tqdm outputs to stderr). This can be done using the following environment variable:
0 commit comments