Legacy-Data on Fortran 2026

WII

Mon, 01 Jan 0001 00:00:00 +0000

WII is a wave-maths code written in Fortran. It runs the numerical modelling that sits behind sea-state and oceanographic products — the kind of long-running scientific Fortran where every line has been tuned over years and “just rewrite it” is not an option.

Where we add value

Maintaining and extending the wave-maths core without breaking the numerical results that downstream systems depend on.
Capturing reference outputs as regression tests so any change to the maths is provably bounded — see Expertise → Testing.
Modernising the build and runtime: pinned compilers, dependency stacks, container packaging — see Expertise → Packaging.
Recovering and migrating historic WII runs and inputs from old storage — see Expertise → Legacy data.
64-bit upgrades of older WII deployments without losing fidelity.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

NCL

Mon, 01 Jan 0001 00:00:00 +0000

NCL — the NCAR Command Language — is the scripting language we use to drive image generation from scientific Fortran codes. It is the standard tool for turning numerical output (wave fields, atmospheric grids, sea-state results) into the charts and rendered images downstream consumers rely on. NCL is no longer actively developed by NCAR, which makes expert support for existing NCL pipelines especially valuable.

Where we add value

Writing and maintaining NCL scripts that turn Fortran numerical output — including WRF and WII — into production-quality visuals.
Keeping legacy NCL pipelines working now that NCL itself is end-of-life: pinning compatible versions, packaging dependencies, and documenting the build.
Integrating NCL into the build, run, and reporting pipeline so visuals are produced automatically rather than by hand.
Reproducible imaging — same input data, same script, same image, every time, including months later.
Recovering and re-running historic NCL scripts against archived data when somebody needs a regenerated chart from years ago — see Expertise → Legacy data.
Migrating NCL outputs to modern delivery surfaces (web, REST, dashboards) — see Examples → REST API.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

WRF

Mon, 01 Jan 0001 00:00:00 +0000

The Weather Research and Forecasting (WRF) model is a large, mature, Fortran-heavy scientific code that is famously fiddly to build and operate at production scale. We help teams running WRF treat it as a real production system rather than a research experiment.

Where we add value

Reproducible builds of WRF and its dependencies (HDF5, NetCDF, MPI, compiler stacks) — pinned, scripted, containerised.
Operational packaging so a forecast run can be reproduced months later from the same inputs and binaries — see Expertise → Packaging.
Pipeline integration: feeding WRF outputs into downstream systems, dashboards, and APIs.
Recovery of legacy WRF runs and inputs from old storage — see Expertise → Legacy data.
Performance and 64-bit upgrades for older WRF deployments.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

Backup and recovery

Mon, 01 Jan 0001 00:00:00 +0000

A Fortran ERP that loses a day’s data is not a software problem — it’s a business problem. We design backup and recovery for systems where the database, the data files, the binaries, and the build artefacts all matter, and all have to come back together.

Where we add value

Backup strategies that actually get tested, not just scheduled.
Restore drills — proving recovery works before you need it.
Point-in-time recovery across SQL databases plus the on-disk Fortran data files that live alongside them.
Disaster recovery plans that account for the build system and the source tree, not just the data.
Migration of old backups onto modern storage — tightly related to Legacy data.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

Legacy data

Mon, 01 Jan 0001 00:00:00 +0000

A lot of Fortran systems sit on top of decades of data: binary records in undocumented formats, files copied from machines that no longer exist, tapes nobody has read in years. We are comfortable in that territory — and we know how to bring that data back into a system you can use today.

Where we add value

Reading old binary formats — record-based, fixed-width, vendor-proprietary, or whatever the previous decade left you with.
Reverse-engineering schemas from the Fortran code that wrote the files, when documentation is long gone.
Pulling data off old media and old machines onto modern storage with integrity checks.
Migrating recovered data into modern stores (SQL, files, APIs) without losing fidelity — see Examples → SQL.
Long-term archiving plans so this is the last time anyone has to do it.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au