Forrtl: severe (59): list-directed I/O syntax error in ModelMonitor

[Chang Liao]

Simulating error using the ModelMonitor.exe

forrtl: severe (59): list-directed I/O syntax error, unit 29, file simulation.sfr

Image              PC        Routine            Line        Source             

mf2005.exe         008F1CA0  Unknown               Unknown  Unknown

mf2005.exe         008B3866  Unknown               Unknown  Unknown

mf2005.exe         0089F342  Unknown               Unknown  Unknown

mf2005.exe         0089E684  Unknown               Unknown  Unknown

mf2005.exe         008842D1  Unknown               Unknown  Unknown

mf2005.exe         0076D4E0  Unknown               Unknown  Unknown

mf2005.exe         0075E1E6  Unknown               Unknown  Unknown

mf2005.exe         00807AF8  Unknown               Unknown  Unknown

mf2005.exe         008F2C53  Unknown               Unknown  Unknown

mf2005.exe         008DADE9  Unknown               Unknown  Unknown

kernel32.dll       7699338A  Unknown               Unknown  Unknown

ntdll.dll          77C19F72  Unknown               Unknown  Unknown

ntdll.dll          77C19F45  Unknown               Unknown  Unknown

Don't have a clue where I should look into, any suggestion?

[Richard B. Winston]

Check that you are using the most recent version of MODFLOW: version
1.11.00.

> --
> 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
> <mailto:modflow+u...@googlegroups.com>.
> To post to this group, send email to mod...@googlegroups.com
> <mailto:mod...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/modflow.
> For more options, visit https://groups.google.com/d/optout.

[Chang Liao]

Yes, sure. I am using the latest version from the USGS site.

As far I tested, most of time it is because that the data format doesn't meet the requirement.

But there is no clue which line goes wrong.

I might try debug mode under Linux environment.

[Richard B. Winston]

The extension SFR indicates that the problem is in the SFR package.
ModelMuse uses free format for the SFR input but that was first
supported in MODFLOW: version 1.10. You should check the listing file
that was generated. At the top, it should say which version of MODFLOW
you were running. You should check that to make sure you were running
the right version. You can also look at where MODFLOW stopped writing
output to identify where the error is. However, if you are really using
the latest version of MODFLOW, that won't solve your problem because the
problem is in ModelMuse. If you send me your ModelMuse file at my work
email (rbw...@usgs.gov), I should be able to find and fix the problem.

> > an email to modflow+u...@googlegroups.com <javascript:>
> > <mailto:modflow+u...@googlegroups.com <javascript:>>.

> > To post to this group, send email to mod...@googlegroups.com

> <javascript:>
> > <mailto:mod...@googlegroups.com <javascript:>>.

> > Visit this group at http://groups.google.com/group/modflow

> <http://groups.google.com/group/modflow>.

> > For more options, visit https://groups.google.com/d/optout

> <https://groups.google.com/d/optout>.

[Chang Liao]

Thank you for that help.

I fixed it again.

I was using ModelMuse and MODFLOW at the same time.

My tircky is that I only use the ModelMuse as an example run, which mean I don't put all my data into the ModelMuse.

Meanwhile, I wrote code to prepare the complete input files and borrow the ModelMonitor from the ModelMuse to run the MODFLOW.

I wished I could use ModelMuse directly. But importing datasets into the ModelMuse for river reaches, streams, etc. are somewhat inefficient by far. For example, I have over 600 hundred river reaches, and I need to prepared the table outside and then select each of the reach and paste into the table, which is quite time consuming for me.

[Richard B. Winston]

You could try using File|Import|Points to import all the river reaches
at once.

> email (rbw...@usgs.gov <javascript:>), I should be able to find