ModelMuse only produces errors
JHaas
is better suited for my work than PMWIN.
I am working through the modelmuse documentation ( http://pubs.usgs.gov/tm/tm6A29/
) and i can't get the example to run.
I go through it step by step, and when i get to the "Executing the
model" step, it starts to run, but simply ends with the ModelMonitor,
and a "The program terminated with an error" popup.
In ModelMonitor Results and Listing are empty, and after closing the
monitor, i get the .lst file in notepad, Which just says:
"LIST FILE: ExampleModel.lst
UNIT 11"
If i understand it correctly, this file should list all stuff that has
been done, and all the results of the simulation. Shouldn't this .lst
file be the same one, that is called output.dat in PMWIN?
Is there any way to get the error message to be more verbose, or where
should i start looking on what could have gone wrong? I tried to set
up a model of my own, and there it actually told me what was wrong
first (eg. starting heads under model bottom, and a list of the
affected cells), but when i had fixed those problems, i got to the
same message and behavior as described above.
J Haas
JHaas
It now behaves a bit differently, but it still does not work (On the
computer i first tried it on).
The list file still is the same, but the ModelMonitor does not even
start now.
However if i look into the output in the "terminal window" (or however
that is called in Windows) I get the following:
>C:\Programme\USGS\ModelMuse2_8\examples\MODFLOW>C:\WRDAPP\MF2005.1_8\Bin\mf2005.
>exe ExampleModel.nam /wait
>
> MODFLOW-2005
> U.S. GEOLOGICAL SURVEY MODULAR FINITE-DIFFERENCE GROUND-WATER FLOW MODEL
> Version 1.8.00 12/18/2009
>
> Using NAME file: ExampleModel.nam
> Run start date and time (yyyy/mm/dd hh:mm:ss): 2010/12/17 10:04:46
>
>forrtl: severe (168): Program Exception - illegal instruction
>Image PC Routine Line Source
>mf2005.exe 0040ED37 Unknown Unknown Unknown
>mf2005.exe 0040B2A1 Unknown Unknown Unknown
>mf2005.exe 0068D1D7 Unknown Unknown Unknown
>mf2005.exe 0074B693 Unknown Unknown Unknown
>mf2005.exe 00737065 Unknown Unknown Unknown
>kernel32.dll 7C817077 Unknown Unknown Unknown
>
>C:\Programme\USGS\ModelMuse2_8\examples\MODFLOW>Start Notepad.exe C:\Programme\U
>SGS\ModelMuse2_8\examples\MODFLOW\ExampleModel.lst
>
>C:\Programme\USGS\ModelMuse2_8\examples\MODFLOW>pause
>Drücken Sie eine beliebige Taste . . .
I guess the key line could be
"forrtl: severe (168): Program Exception - illegal instruction"
According to a quick google search, this could simply mean that the
program (The underlying Modflow 2005 in this case, I assume) tries to
do stuff not supported by the hardware. Given the fact that i try to
run the model on an old Pentium III box, this is maybe not that
surprising.
To test my suspicion, i installed Modflow and ModelMuse on my other,
more modern computer. The first run didn't work, whereas the second
try did produce exactly the output shown in the documentation, even
though i run both, Modlflow and ModelMuse with wine (A windows
compatibility layer for Linux).
So can anyone confirm my suspicion that a Pentium III is simply to
old, and does anyone else successfully run Modflow and ModelMuse under
Linux?
Regards,
J Haas
Richard B. Winston
working. There are several possibilities why MODFLOW isn't working.
1. The input is incorrect.
2. The compiled version of the program is incompatible with your hardware.
3. MODFLOW may not be running under WINE even though ModelMuse is
running under WINE.
The first thing to do in figuring out what is wrong would be to try to
run MODFLOW with input that is known to be correct. The MODFLOW
executable for Windows comes with input files for several models. I
believe the UNIX source code also comes with those same example models.
You didn't say whether you compiled MODFLOW yourself or are using the
Windows executable under WINE. Whichever you are using, I suggest
trying it out with input files from both the Windows and the UNIX
distribution. I think it is likely that the examples with the UNIX
distribution will work with a version you compiled yourself but that it
won't work with the input files from the Windows distribution. The
input files from the UNIX distribution probably won't work with the
Windows executable run under WINE but should work with the examples from
the Windows distribution. The difference between the two sets of
example input files has to do with how line endings are defined in
Windows and UNIX. The two operating systems use different conventions
and won't necessarily recognizing line endings if they are in the wrong
format. If you can get MODFLOW to run with at least one of the example
input data sets, that will prove that the compiled version of MODFLOW is
compatible with your hardware. If it doesn't run with any of the
examples, than the compiled version is probably incompatible with your
hardware.
If you can get MODFLOW to run, the next step would be to determine why
it isn't running with the input generated by ModelMuse. If you are
using a version of MODFLOW that you compiled yourself on Linux, the
line-ending issue may be the culprit. If you are using the windows
version of MODFLOW and you can get it to run under WINE, then the
problem may be that when ModelMuse tries to start MODFLOW it doesn't try
to start it under WINE but instead tries to start it as a native Linux
executable. If that is the case, you may be able to get MODFLOW to run
if you start it yourself under WINE.
Because ModelMuse is a Windows application, there is no guarantee that
you will be able to get it to work the way you want under WINE.
>> Dr�cken Sie eine beliebige Taste . . .
Richard B. Winston
running Windows Server 2003). The same thing happened to him as happened
to you; MODFLOW crashed with the following error message.
forrtl: severe (168): Program Exception - illegal instruction
I think this means that when MODFLOW was compiled, the compiler options
were set so that MODFLOW would take advantage of features in more recent
computer chips. Consequently, it won't run on some older chips. You
could probably recompile MODFLOW with different compiler options and get
it to run on a Pentium III.
If you have never compiled MODFLOW before, it is not a trivial task.
There are some suggestions on how to do it with a variety of different
compilers at the following URL.
http://water.usgs.gov/nrp/gwsoftware/modflow2000/MFDOC/index.html?suggestions_on_compiling.htm
However, none of the suggestions address your problem exactly.
>> Dr�cken Sie eine beliebige Taste . . .