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
Added logging, subprocess output handling with BusySpinner and test improvements
1. Added and documented a logging system.
2. Implemented animation for long-running processes in Score-P mode (both for data transfer to the subprocess and for displaying progress animation within the subprocess itself).
3. Added an example of execution of the long running task – Large array processing with Score-P in `examples/ExampleBasic.ipynb`.
4. Changed the way subprocess output streams are read — moved this logic into a separate function `read_scorep_process_pipe()`.
5. Brought tests into a working state:
- Created a new function to clean up garbage from standard output.
- Added a context manager `with self.subTest()` to better identify which cell failed during execution.
- Temporarily updated expected test outputs to account for a new line introduced for proper animation handling (`clear_line` string in `read_scorep_process_pipe()`).
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -152,6 +152,7 @@ MODE=[disk,memory]
152
152
```
153
153
154
154
When using persistence in `disk` mode, user can also define directory to which serializer output will be saved with `SCOREP_KERNEL_PERSISTENCE_DIR` environment variable.
155
+
To see the detailed report for marshalling steps - `MARSHALLING_DETAILED_REPORT=1` environment variable can be set.
155
156
156
157
`%%execute_with_scorep`
157
158
@@ -235,6 +236,11 @@ Similar yields for cloudpickle. Use the `%%marshalling_settings` magic command t
235
236
236
237
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.
237
238
239
+
## Logging Configuration
240
+
To adjust logging and obtain more detailed output about the behavior of the JUmPER kernel, refer to the `src/logging_config.py` file.
241
+
242
+
This file contains configuration options for controlling the verbosity, format, and destination of log messages. You can customize it to suit your debugging or monitoring needs.
243
+
238
244
# Future Work
239
245
240
246
The kernel is still under development. The following is on the agenda:
Copy file name to clipboardExpand all lines: examples/ExampleBasic.ipynb
+51-1Lines changed: 51 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -466,7 +466,57 @@
466
466
{
467
467
"cell_type": "markdown",
468
468
"metadata": {},
469
-
"source": []
469
+
"source": [
470
+
"### Large array processing with Score-P\n",
471
+
"This example illustrates the steps involved in the marshalling process when a cell instrumented with Score-P is executed with a large data payload as input.\n"
0 commit comments