Logging

runtime.log

This is the primary log for the solver -> here, you can see success / failure of the solver in its tasks. This is the go-to log to check when something does not work.

<...>
[2026-09-16 11:44:22.756] [rl] [info] Initializing Headless Texture.....
[2026-09-16 11:44:22.756] [rl] [info] Success
[2026-09-16 11:44:22.756] [rl] [info] Running headless context 
[2026-09-16 11:44:22.756] [rl] [info] Dispatching Solver2D (FP32)
[2026-09-16 11:44:22.756] [rl] [info] Checking Available CUDA CUBIN PTX / SASS versions
[2026-09-16 11:44:22.790] [rl] [info] CUBIN versions: PTX 120 | binary 120
[2026-09-16 11:44:22.790] [rl] [info] Transferring Constants to Device
<...>

Note: Sometimes, before the solver launches, you may experience a rather large delay. This is most often the case when CUBIN versions of PTX / binary differ. See more in troubleshooting.

casefile.log

This log shows the Physical parameters (reference state loaded / computed). Typically, this looks something like:

                    Physical Parameters                     
------------------------------------------------------------
 Temperature                                300.00000  K     
 Gas Constant                               287.05800  J/(kg·K) 
 Gamma                                        1.40000  -     
 μ                                            0.00049  Pa·s  
 Pressure                                100000.00000  Pa    
 Speed of Sound                             347.22379  m/s   
 Probe Offset                                 0.10000  m     
 Precision                                             -     
------------------------------------------------------------

                    Computed Parameters                     
------------------------------------------------------------
 β                                            0.96167        
 c                                            1.18322        
 Δx                                      1.000000e-04        
 Δt                                      2.846872e-07        
------------------------------------------------------------

And allows you to directly inspect what parameters the solver used.

Events.log

The sole purpose of this log is to track capture_events, i.e. the second branch of events that are triggered after a density spike passes a certain position (for boundaries, this amounts to the location (NoseX, NoseY), which you define in the configuration file. This will then track the time since the event, and any subsequent events that are triggered:

[2026-09-16 11:44:32.172] [eventLog] [info] Time since impact:  199.2810
[2026-09-16 11:44:32.200] [eventLog] [info] Event Triggered: store_1 at  200.4198 us
[2026-09-16 11:44:32.201] [eventLog] [info] Exporting Fields as HDF5
<...>
[2026-09-16 11:44:43.004] [eventLog] [info] Event Triggered: EXT at  300.0603 us
[2026-09-16 11:44:43.004] [eventLog] [warning] Simulation finished

memory.log

This log shows the VRAM allocations for the lattice distributions, fields, and buffers. At the end, you can track the total VRAM memory the solver used:

+------------------------------+--------+----------+----------------+
| Buffer Name                  | Type   | Device   | Size (Mb)      |
+------------------------------+--------+----------+----------------+
 Device                             2         0           976.6 

NVML.log

This log records device parameters via NVML: Power, Temperature, and Utilization.

[2026-09-16 11:44:22.810] [nvmlLOG] [info] Monitoring device 0: NVIDIA GeForce RTX 5070
[2026-09-16 11:44:22.817] [nvmlLOG] [info] Power: 33.9 W  Temp: 34 °C  Util: 4 %
[2026-09-16 11:44:23.017] [nvmlLOG] [info] Power: 33.9 W  Temp: 34 °C  Util: 4 %
[2026-09-16 11:44:23.217] [nvmlLOG] [info] Power: 47.3 W  Temp: 38 °C  Util: 55 %