Peter Hill
Peter Hill
Thanks @bendudson! It looks like having the dockerfile in a submodule might be tricky, so a Github action might be the better way to go.
An example of a good README.md is `IMEX/drift-wave-constraint/README.md` It describes what it does, what equations it solves, what the expected output should look like, as well as some additional information...
There actually is already one there, it's just a bit out of date.
+1 for duplicate for now, we could always refactor later. Ideally, one might imagine we had something like a list of `input_software` metadata with `software_name`, `software_version`, etc., so that we...
The IO refactor in #2209 should be able to handle this, although I'm not sure it's a good idea, as it would increase the file size of every output file....
readthedocs is failing because we need #2308 first
A short docstring in `bout-build-dep.sh` with a `--help` flag would be lovely too.
An alternative to this is to use [spack](https://spack.io). There's some spack files already in the GPU branches, e.g. https://github.com/boutproject/BOUT-dev/blob/next-hypre-outerloop-cuda/scripts-config/lassen-examples/spack_env/bout/spack.yaml It looks like it might also not be very much effort...
> For the future, it might be easier to integrate downloading + compiling of dependencies within cmake ...? Yes, there's a few options for this: Conan, vcpkg, CPM. Or we...
Let's move this to the BOUT-config repo and remove the machine specific instructions entirely