.testing: Use Fortran to generate tc inputs #250
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch removes the
build_{grid,data}.py
scripts from .testing's tc4, along with the setup of the Python infrastructure used in the .testing Makefile and GitHub Actions CI.The Python scripts have been replaced with equivalent Fortran programs which generate identical netCDF output.
A new rule (
preproc
) has been added to the .testing top Makefile for generating the model input files.The netCDF compiler dependenices are configured with autoconf, currently duplicating the macros in
ac/configure.ac
. (NOTE: It may be possible to share these with a common macro in ac/m4.The configure script and Makefile are currently generated from
configure.ac
andautoreconf
. In the future, we could simply pre-generateconfigure
and add it to the repository.This patch was motivated by the inability to install recent netCDF-Python packages on systems with older gcc compilers, including our main production machine. We could have possibly resolved this by adding compiler configuration to pip, or perhaps reported the issue to the netCDF-python project for them to resolve. But the costs of relying on all this Python infrastructure is starting to exceed the benefits, and I would recommend we excise it from our test suite.