Bart Rogiers

Consistent S3 class names

2

From the current namespace file, it is obvious we are not really using a consistent approach for naming our S3 classes. We have at least these: `bas`, `bcf`, `bud`, `cbc`,...

Currently we rely on hydroGOF for the model performance evaluation. Weights are however not used there, but they are common enough in groundwater modelling to implement I think. Question is...

Consistency with ModelMuse

2

Let's create a place to also discuss this. My point of view at the moment is that RMODFLOW should follow ModelMuse conventions as closely as possible. Main argument for that...

Metadata

3

Currently we have some functionality for metadata in a separate *.prj projection file, possibly containing crs, origin coordinates, start time and grid rotation. Some of these parameters can be part...

The idea has surfaced several times: - RMODFLOW.examples in #6, could also serve as a showcase of real-life models - RMODFLOW.invert in #7 - Testing in #8 could potentially also...

Basic MODFLOW package/file object functions

5

The idea is to have for all packages/files from MODFLOW-2005 based codes the following functions: - `rmf_read_*` for reading, - `rmf_write_*` for writing, - `rmf_create_*` for creating the object from...

Install codes and example models

1

Currently `rmf_install()` (**seems to be broken**, and) puts the codes in `C:/WRDAPP`. I would like to revert back to installing in the `system.file(package = "RMODFLOW")` folder to avoid interfering with...

Since the renaming of the {scales} S3 class to "transform", it clashes with e.g. {raylibr}'s S3 class. The `print()` method is defined in both packages, and generates a warning, but...

This should fix #13 as far as I can see ...

Consider including package name in S3 class name(s)?

1

Since the renaming of the {scales} S3 class to "transform", it clashes with e.g. {raylibr}'s S3 class. The `print()` method is defined in both packages, and generates a warning, but...