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.

Sign up for GitHub

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

Jump to bottom

Restarting subapp and all subapps underneath but not the ultimate master #6297

Closed
snschune opened this issue Feb 10, 2016 · 1 comment
Closed

Restarting subapp and all subapps underneath but not the ultimate master #6297

snschune opened this issue Feb 10, 2016 · 1 comment
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.

Comments

@snschune
Copy link
Contributor

@friedmud @YaqiWang @permcody
We have a FullSolveMultiapp executed on initial and the master picks up from this result, but
depending on the scenario the setup of the master transient can vary. This is related to the SPRINT scenario.

We would like to restart the subapp (and all apps underneath it) while the ultimate master does not restart. This would make it possible to ensure consistent behavior via the transfers we already have in place. One problem is scaling of the solution and providing the eigenvalue to the transient solve - this is currently all implemented in the transfers.
@friedmud
Copy link
Contributor

Yeah. It is definitely possible. But it will be a lot of work to get all of the little things right. 90% of it will work immediately... but that last 10% will suck.

@permcody permcody added C: Framework T: task An enhancement to the software. P: normal A defect affecting operation with a low possibility of significantly affects. labels Feb 10, 2016
snschune pushed a commit to snschune/moose that referenced this issue Mar 2, 2016
An example of restarting the subapp but not the master (idaholab#6297)
d43798c
permcody pushed a commit to permcody/moose that referenced this issue Mar 8, 2016
@permcody
An example of restarting the subapp but not the master (idaholab#6297)
86be430
permcody added a commit to permcody/moose that referenced this issue Mar 8, 2016
@permcody
Adding sub-app only restart feature
91e2839 
closes idaholab#6297
permcody added a commit to permcody/moose that referenced this issue Mar 8, 2016
@permcody
Adding sub-app only restart feature
33011e8 
closes idaholab#6297
permcody added a commit to permcody/moose that referenced this issue Mar 8, 2016
@permcody
Adding sub-app only restart feature
575bd64 
closes idaholab#6297
permcody pushed a commit to permcody/moose that referenced this issue Mar 9, 2016
@permcody
An example of restarting the subapp but not the master (idaholab#6297)
230eea1
permcody added a commit to permcody/moose that referenced this issue Mar 9, 2016
@permcody
Adding sub-app only restart feature
f5d5f38 
closes idaholab#6297
permcody added a commit to permcody/moose that referenced this issue Mar 9, 2016
@permcody
Adding subapp only restart feature
b95bbc1 
closes idaholab#6297
SudiptaBiswas pushed a commit to SudiptaBiswas/moose that referenced this issue Mar 29, 2016
An example of restarting the subapp but not the master (idaholab#6297)
690e123
SudiptaBiswas pushed a commit to SudiptaBiswas/moose that referenced this issue Mar 29, 2016
@permcody
Adding subapp only restart feature
9947394 
closes idaholab#6297
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: Framework P: normal A defect affecting operation with a low possibility of significantly affects. T: task An enhancement to the software.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@friedmud @permcody @snschune