Legacy Fortran to Python mapping¶
Upstream Fortran source¶
Primary upstream reference:
external/odt1/source1/
Current mapping¶
Fortran |
Python |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
location sampling in |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
top-level legacy case execution in |
|
|
|
|
|
simple realization scheduling in |
|
|
|
repeated realization / series aggregation path in |
|
Notes¶
This mapping now covers most of the numerically important Bodt.f execution path: initialization, eddy sampling, acceptance, triplet application, adaptive dt, deterministic advancement, repeated realizations, time statistics, change statistics, and major postprocessing/output helpers.
The main remaining gaps or caveats are:
top-level legacy file-opening / file-closing orchestration in
Bodt.fis not mirrored as a single monolithic Python drivertop-level legacy file-opening / file-closing orchestration in
Bodt.fis not mirrored line-for-line, thoughpyodt1.legacy.run_legacy_case()now provides a legacy-style end-to-end case runner that reads a case directory, writes the expected legacy file set, and emitsfort.11the external legacy sources in this repository now include a minimal robustness patch for the intercomparison
BSnap/BRecordpath; the patched path is validated, while the original unmodified negative-Nvariant is documented separately viascripts/investigate_bsnap_intercomparison.pyas compiler-fragile legacy behavior