mjreno
mjreno
@langevin-usgs This hasn't been tested yet but should be close if not already done. I'll find or generate a suitable input and test and then will update this issue.
@langevin-usgs apologies for losing track of this one, will verify and close.
@langevin-usgs just thinking about this a bit- the struct array input reader already can read similar binary inputs. The current use case is for stress period data, however, so currently...
Closing as this has been addressed with #1784 and #1783.
@langevin-usgs I do have some thoughts about how to remove the EXCHANGEDATA reference. It might be straightforward and can look at it before or after a merge. I agree that...
Agree @langevin-usgs. This type of checking is already being supported for FILEIN tags as certain tags can be read more than once (TS6) but not most. FILEOUT tags are treated...
A few comments... I agree that compile time errors would be preferable to see in general. I also agree that the language is ambiguous in this way- it isn't necessarily...
Hi @RyanConway91 I just ran a test in version 6.4.4 and didn't see this issue. Is it possible to run your model in the most recent version of MODFLOW 6...
replaced with #2490
@rbwinst-usgs thanks for looking at the ```NetCDF``` documentation. The ```NetCDF``` keyword is analogous to the ```LAYERED``` keyword and there is a brief explanation in the section ```Array Input (READARRAY)```, where...