Configuration Reference: Monitor YAML

Table of Contents

• 1. io
• 2. logging
• 3. profiling
• 4. solver_monitoring

For the full commented template, see:

monitor.yml controls observability and run I/O behavior.

1. io

io:
  data_output_frequency: 100
  particle_log_interval: 10
  directories:
    output: "results"
    restart: "results"
    log: "logs"
    eulerian_subdir: "eulerian"
    particle_subdir: "particles"

Mappings:

• data_output_frequency -> -tio
• particle_log_interval -> -logfreq
• directories.output -> -output_dir
• directories.restart -> -restart_dir
• directories.log -> -log_dir
• directories.eulerian_subdir -> -euler_subdir
• directories.particle_subdir -> -particle_subdir

2. logging

logging:
  verbosity: "INFO"
  enabled_functions:
    - AdvanceSimulation

• verbosity maps to environment variable LOG_LEVEL via pic.flow launcher.
• enabled_functions is serialized into whitelist.run and loaded by C logging filters.

Supported verbosity strings:

• ERROR
• WARNING
• PROFILE
• INFO
• DEBUG
• TRACE
• VERBOSE

3. profiling

profiling:
  critical_functions:
    - Flow_Solver
    - AdvanceSimulation

This list is serialized into profile.run for critical-path profiling summaries.

4. solver_monitoring

Raw flag passthrough for PETSc monitors/debug options:

solver_monitoring:
  -ps_ksp_pic_monitor_true_residual: true
  -ps_ksp_converged_reason: true

Rules:

• Keys must be full flags (with leading -).
• true emits switch-only flag.
• false omits flag.
• Non-boolean values emit flag value.

9. Next Steps

Proceed to Configuration Reference: Postprocessor YAML.

Also see:

• Configuration Contract (YAML -> Generated Artifacts -> Runtime)
• Developer Ingestion Map