Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mpath7.log filename as an input option in .MPSIM/.MPNAM #20

Open
mjigmond opened this issue May 14, 2019 · 2 comments
Open

Add mpath7.log filename as an input option in .MPSIM/.MPNAM #20

mjigmond opened this issue May 14, 2019 · 2 comments

Comments

@mjigmond
Copy link

In the current implementation it's impossible to run multiple tracking simulations in the same directory because the mpath7.log file is hard-coded in MPath7.f90.

@mjigmond mjigmond changed the title Add mpath7.log filename as an input option in .MPSIM Add mpath7.log filename as an input option in .MPSIM/.MPNAM May 14, 2019
@aprovost-usgs
Copy link
Collaborator

As noted by @mjigmond, hardwiring of the log file name to "mpath7.log" precluded running more than one simulation in the same directory at the same time, since all the simulations would try to write to the same log file. The log file name can now be optionally specified on the command line, after the simulation file name. If not specified, it defaults to "mpath7.log". (If only one file name is given on the command line, it is interpreted as the simulation file name, since that file is required. If no file names are given, the user is prompted to enter only the simulation file name, since that file is required.) Tested to confirm the ability to run more than one simulation simultaneously in the same directory (provided none of the output files have been given conflicting names). The updated source code has been posted (commit fdb3924), and we're working on a USGS release that includes this update.

@aprovost-usgs
Copy link
Collaborator

See relevant updates in commit 20ae10c in response to issue #19.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants