SEAWAT ERROR: .hds file not found! Run ModFlow first!

[eugenio pescimoro]

Hi all,

I am stuck on a basic ModFlow model beacuse of the following error message that I get when I try to look at the Output:

" #filename.hds file not found! Run ModFlow first! "

I am using the Visual Modflow Classic interface to write the Input files of a model that should simulate an acquifer with saltwater intrusion.

Few months ago, when I simulated some similar simple cases (always using SEAWAT engine), I got preatty good outputs nevertheless the same error message now comes out when I try to re-run the same models.

Do anyone know any feature that could have changed?

Thank you in advance,

Eugenio.

[An Ho Antonio Taylor]

Maybe your model is transient and the initial head archive , from other run or previous run is missing or the root was changed, modflow 2000 has the option for making steady or transient period stress(0 or 1), it very helpful if you don't have the configuration of the initial head.

--
You received this message because you are subscribed to the Google Groups "MODFLOW Users Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modflow+u...@googlegroups.com.
To post to this group, send email to mod...@googlegroups.com.
Visit this group at https://groups.google.com/group/modflow.
For more options, visit https://groups.google.com/d/optout.

[eugenio pescimoro]

Thank you An Ho Antonio Taylor, I double checked the stress period and it was correctly set as transient.

I think the problem is something related to the settings of SEAWAT packages but I can't recall the right configuration.

I've tried to run it selecting different Solvers with different Layer Property Packages but it didn't work.

Hope someone already step into it and could troubleshoot-it.

Best,

Eugenio.

[Chris Russoniello]

Eugenio,

I'm a bit confused, because you said you're just writing the the input files (not running Modflow/Seawat), so I wouldn't expect that modflow or the GUI should be trying to find the hds file. The only reason I can think of that you might need the hds file during the write is if it uses it as an initial condition as An Ho suggested. Make sure that if you are using a previous run as initial conditions that the hds file you would be accessing is where you expect it to be and you have read access to the directory it lives in.

If you're also running Modflow/Seawat, the issue could also be read/write access to the directory?

If you're seeing the issue after the model run, the issue could be that the run didn't go because you have an issue in the model. In that case your model run crashed prior to the hds file being written and thus you can't access the nonexistent hds file for reading. In this case, look at the .lst file and see what it looks like at the end.

Hope that helps.

-Chris

[Ashutosh]

Hi!

Try selecting the initial head file again from the menu. Most probably you have deleted the initial heads file and Visual modflow is trying to find it, since you are rerunning the model.

Hpc

Sent from my iPhone

--

[An Ho Antonio Taylor]

i think you should comment the vdf file in the part of mt3d part and extract the initial heads from modflow run, then you should looking in the list file from seawat original run and provide the initial heads to the input dataset and rerun, and isolate the files in a folder and run the seawat making a .bat executable rather than .exe via straighforward 

best regards

To unsubscribe from this group and stop receiving emails from it, send an email to modflow+unsubscribe@googlegroups.com.

To post to this group, send email to mod...@googlegroups.com.
Visit this group at https://groups.google.com/group/modflow.
For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "MODFLOW Users Group" group.

To unsubscribe from this group and stop receiving emails from it, send an email to modflow+unsubscribe@googlegroups.com.