Fortran routine status matrix¶
This page gives a concise routine-by-routine status summary for the legacy odt1 Fortran source set under external/odt1/source1/.
Status labels¶
Implemented: a Python equivalent exists
Validated: compared directly against actual Fortran execution
Tested: covered by Python tests or structural compatibility checks, but not a dedicated major harness
Caveated: validated with an important caveat (for example, only for the patched legacy path)
Remaining: not yet fully mirrored in exact procedural detail
Matrix¶
Fortran routine |
Python equivalent |
Status |
|---|---|---|
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated, caveated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated, caveated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
|
|
Implemented, validated |
top-level execution in |
|
Implemented, caveated, remaining |
Important caveats¶
BInitIter.f¶
The important numerical behavior is represented and validated, but the Python implementation is split across helper functions and solver setup rather than mirrored as a single one-to-one routine.
BSnap.f¶
the patched legacy intercomparison path is validated
the original unmodified xmgrace path is validated
the original unmodified intercomparison path is documented as compiler-fragile legacy behavior
See:
Bodt.f¶
The main numerical runtime structure is in place, but exact line-by-line procedural parity is still not complete.
What remains is mostly:
exact monolithic driver structure
exact open/write/close sequencing everywhere
exact historical procedural parity rather than missing turbulence-model content
Recommended interpretation¶
The most accurate summary is:
the repository now covers almost the full routine set in implementation terms
the numerically important majority is directly validated against Fortran
the remaining work is primarily about top-level procedural parity, not missing core ODT physics