-
Notifications
You must be signed in to change notification settings - Fork 59
In Situ Python Analysis
In situ analysis is to analyze ongoing simulation data without outputting data to disk before conducting analysis. It enables us to explore these ongoing simulation data through accessing memory directly using Python.
- Install libyt and yt_libyt: the in situ analysis library and its yt frontend.
- Install yt: the core analysis tool.
libyt has the following compilation options in Makefile
:
-
SUPPORT_LIBYT (or
--libyt
when usingconfigure.py
) -
LIBYT_USE_PATCH_GROUP (or
--libyt_patchgroup
when usingconfigure.py
) -
LIBYT_INTERACTIVE (or
--libyt_interactive
when usingconfigure.py
)
Must set LIBYT_PATH
in either Makefile
or the machine configuration file
to the path containing the folders include
and lib
of libyt.
libyt has the following runtime parameters:
-
YT_SCRIPT
: The Python script name to be loaded. Do not include the file extension.py
. -
YT_VERBOSE
: Log level of libyt (0=off, 1=info, 2=warning, 3=debug). -
YT_FIG_BASENAME
: Figure basename of the outputs from yt.
For example, Input__Parameter
with the following lines will read the Python script inline_script.py
,
set log level to information only, and set the figure basename to MHD
.
YT_SCRIPT inline_script
YT_VERBOSE 1
YT_FIG_BASENAME MHD
If you encounter the following OpenMPI error messages related to MPI remote memory access operation,
ompi_osc_ucx_win_attach: Assertion ......
try adding OMPI_MCA_osc=sm,pt2pt
before mpirun
:
OMPI_MCA_osc=sm,pt2pt mpirun ...
This is something libyt will fix in the near future.
Getting Started
User Guide
- Installation
- Running the Code
- Adding New Simulations
- Runtime Parameters
- MPI and OpenMP
- GPU
- Physics Modules
- Outputs
- Simulation Logs
- Data Analysis
- In Situ Python Analysis
- Test Problems
- Troubleshooting
Advanced Topics
Developer Guide