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

Make MultiApp take command line arguments #2137

Closed
YaqiWang opened this issue Feb 14, 2014 · 7 comments
Closed

Make MultiApp take command line arguments #2137

YaqiWang opened this issue Feb 14, 2014 · 7 comments
Labels
C: Framework T: task An enhancement to the software.

Comments

@YaqiWang
Copy link
Contributor

A MOOSE application can take command line arguments to override parameters in the input file. However, when it is started with a MultiApp, we currently do not have a way to give the application command line arguments. A suggested solution could be: add one or two parameters in the MultiApp block to take the arguments.

@YaqiWang
Copy link
Contributor Author

Any comments on this?

@friedmud
Copy link
Contributor

It's a good idea - just no time to do it yet...

@permcody
Copy link
Member

Cross-referencing #4119

@YaqiWang
Copy link
Contributor Author

Can we raise the priority of this issue? Without this, yak tests contains lots of inputs for subapps which only have small diffs. I really want this to be cleaned. Thanks!

@permcody
Copy link
Member

Yes, but I'm likely the one who will do it and I'm booked for most of the month of June. Don't know if I'll get it done for awhile yet.

@permcody permcody added P: critical and removed P: normal A defect affecting operation with a low possibility of significantly affects. labels May 26, 2015
@YaqiWang
Copy link
Contributor Author

This could be a low-hanging fruit.

@permcody
Copy link
Member

Well technically it's not hard, in fact I added code to explicitly
"disallow" this until we figured out syntax so I know how to turn it back
on. The problem was that the Multiapps were picking up the same options
that you were handing to the master causing other bad effects like
over-writing the same output file, etc when supplying something like an
Outputs file_base. Once we decide on syntax which is a little tricky when
you consider how flexible the Multiapp syntax is, the rest is just simple
parsing and bookkeeping.

Cody

On Tue, May 26, 2015 at 5:03 PM Yaqi notifications@github.com wrote:

This could be a low-hanging fruit.


Reply to this email directly or view it on GitHub
#2137 (comment).

permcody added a commit to permcody/moose that referenced this issue May 28, 2015
permcody added a commit to permcody/moose that referenced this issue May 29, 2015
permcody added a commit to permcody/moose that referenced this issue Jul 23, 2015
permcody added a commit to permcody/moose that referenced this issue Jul 23, 2015
permcody added a commit to permcody/moose that referenced this issue Jul 27, 2015
permcody added a commit to permcody/moose that referenced this issue Jul 31, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Framework T: task An enhancement to the software.
Projects
None yet
Development

No branches or pull requests

3 participants