Subject: Weap and Modflow Linkage Posted: 1/9/2019 Viewed: 8669 times
I'm PH.D candidate of civil engineering in Iran, I wanna to link Weap and Visual Modflow Flex 2015.1, But unfortunately the output format of Modflow is .amd and the Modflow format which weap link, is .mfn, what is the problem there?
I'm grateful to help me. thank you.
Ms. Anne Hereford
Subject: Re: Weap and Modflow Linkage Posted: 1/30/2019 Viewed: 8536 times
I'm not familiar with linking Modflow to WEAP, but the following statement from the WEAP help may hold the answer:
"The versions of MODFLOW that can be linked to WEAP are MODFLOW 2000, MODFLOW 2005 and MODFLOW-NWT."
If "Visual Modflow Flex 2015.1" is not part of one of these versions, i imagine that's the problem.
Let us know if this answers your question.
Eng. Mahsa Ghasemzade Somarin
Subject: Re: Weap and Modflow Linkage Posted: 1/30/2019 Viewed: 8528 times
Thank you very much Anne
Actually I have read the user guide of Weap and Moadflow. As you mentioned Modflow 2000, 2005 and NWT versions can be linked to Weap, I use these engines in Visual Modflow flex too, but unfortunately the Visual Modflow flex output's can't be read by Weap and I can't find anywhere why this happen and I don't know what I do anymore.
If someone can help me know a solution or change to solve this problem I would be really thank you
Greetings to all
Mr. Jack Sieber
Subject: Re: Weap and Modflow Linkage Posted: 1/30/2019 Viewed: 8524 times
WEAP does not require that the MODFLOW Name filename end in .mfn. You can tell WEAP to use any filename for the Name file, but it must conform to MODFLOW conventions in its internal formatting. When browsing in WEAP for the Name file, at the bottom of the window, change "Files of type" from "MODFLOW Name Files (*.nam, *.mfn)" to "All files (*.*)" to show all files.