Peter Hill
Peter Hill
That best practices is only for Fedora, and is for standalone Python packages, so it's not super relevant here. > It would also be beneficial for applying those scripts to...
Bah, I made a start on moving these all over to boututils, including keeping all the git history, but one of them requires boutdata, so they'll have to be there...
Replaced by https://github.com/boutproject/boutdata/pull/111
Have you tried building BOUT++ with: ``` cmake . -B build -DBOUT_DOWNLOAD_NETCDF_CXX4=ON ``` This will build the netcdf C++ library as part of the BOUT++ build. It also looks like...
Ah, we probably want to restore the option in master/5.1.1, mark it as deprecated (not sure we actually have a way of doing this for input options), and then add...
I think maybe deprecate `mxorder` and keep `cvode_max_order`? To be honest, looking through the rest of the options, we don't have terribly consistent naming scheme -- another one for the...
Hmm, I thought we fixed this. Which BOUT++ version/commit are you using here?
We've sort of run into similar issues with the coordinate variables `x, y, z` in the input files being in some fixed coordinate system, and not necessarily the normalised coordinates...
No, but I think it's a bit of a chicken-and-egg situation -- nobody's likely to start using it until there's good support. Getting support into fpm will be good motivation...
Wouldn't they just come under `includes`? Or are you thinking of something else?