I think ultimately this implementation could be a bit more lightweight. I would for example not provide any functionality to run the actual modflow model, but only export the required input files. A user can then go ahead and install flopy/MODFLOW themselves and fiddle around in a notebook, it's then their responsibility and we don't have to have any dependency on MODFLOW to test our code. Our job is really just to provide a way for them to get a MODFLOW/flopy compatible representation of our mibitrans model. I think we can in the end turn this into some methods of the mibitrans.model class which is mostly based on the _parameters method, but let's do this in another PR some day 😄 .
Originally posted by @JaroCamphuijsen in #170 (review)
I think ultimately this implementation could be a bit more lightweight. I would for example not provide any functionality to run the actual modflow model, but only export the required input files. A user can then go ahead and install flopy/MODFLOW themselves and fiddle around in a notebook, it's then their responsibility and we don't have to have any dependency on MODFLOW to test our code. Our job is really just to provide a way for them to get a MODFLOW/flopy compatible representation of our mibitrans model. I think we can in the end turn this into some methods of the
mibitrans.modelclass which is mostly based on the_parametersmethod, but let's do this in another PR some day 😄 .Originally posted by @JaroCamphuijsen in #170 (review)