Capability to read domain netCDF #361
Comments
dschlaep
added a commit
that referenced
this issue
Jan 4, 2024
Read and create domain netCDF file - close #361, close #362 * SOILWAT2 can now be compiled in one of two modes (#361, #362; @N1ckP3rsl3y, @dschlaep): * `"netCDF"`-based input (currently limited to the `"domain"`); this mode is compiled if the new preprocessor definition `"SWNETCDF"` and the `"netCDF"` library are available, e.g., `CPPFLAGS=-DSWNETCDF make all` * text-based input and output (as previously) * For `"netCDF"`-based SOILWAT2, information about the `"domain"` (i.e., simulation units and their geographic locations) is obtained from `"domain.nc"` (#361; @N1ckP3rsl3y, @dschlaep). * `"netCDF"`-based SOILWAT2 is compiled if the new preprocessor definition `"SWNETCDF"` is made available, e.g., `CPPFLAGS=-DSWNETCDF make all` * User-specified paths to `"netCDF"` header and library can be provided as well, e.g., `CPPFLAGS=-DSWNETCDF NC_CFLAGS="-I/path/to/include" NC_LIBS="-L/path/to/lib" make all` * New input directory `"Input_nc/"` that describes `"netCDF"`-based inputs (paths provided by new entries in `"files.in"`). * New text input file `"files_nc.in"` that lists for each input purpose (currently, only `"domain"` is implemented) the path to the `"netCDF"` input file and associated variable name. * New text input file `"attribues_nc.in"` to provide global attributes and a geographic (and optionally a projected) `"CRS"` (coordinate reference system) that describe the `"domain.nc"`. * A user provided `"domain.nc"` that describes the simulation `"domain"`. Specifications must be consistent with `"domain.in"`. If absent, a template is automatically generated based on `"domain.in"`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: