# FullSolveMultiApp

Performs a complete simulation during each execution.

## Overview

The FullSolveMultiApp object is designed to perform a complete simulation every time it executes, thus it can be used for creating simulations that have portions that are on drastically different time scales.

## Example Input File Syntax

The following code snippet demonstrates how to create a FullSolveMultiApp object.

[MultiApps]
[full_solve]
type = FullSolveMultiApp
# not setting app_type to use the same app type of master, i.e. MooseTestApp
execute_on = initial
positions = '0 0 0'
input_files = sub.i
[]
[]

(test/tests/multiapps/full_solve_multiapp/master.i)

## Input Parameters

• input_filesThe input file for each App. If this parameter only contains one input file it will be used for all of the Apps. When using 'positions_from_file' it is also admissable to provide one input_file per file.

C++ Type:std::vector

Options:

Description:The input file for each App. If this parameter only contains one input file it will be used for all of the Apps. When using 'positions_from_file' it is also admissable to provide one input_file per file.

### Required Parameters

• app_typeThe type of application to build (applications not registered can be loaded with dynamic libraries. Master application type will be used if not provided.

C++ Type:MooseEnum

Options:CombinedApp CombinedTestApp

Description:The type of application to build (applications not registered can be loaded with dynamic libraries. Master application type will be used if not provided.

• bounding_box_inflation0.01Relative amount to 'inflate' the bounding box of this MultiApp.

Default:0.01

C++ Type:double

Options:

Description:Relative amount to 'inflate' the bounding box of this MultiApp.

Default:0 0 0

C++ Type:libMesh::Point

Options:

• cli_argsAdditional command line arguments to pass to the sub apps. If one set is provided the arguments are applied to all, otherwise there must be a set for each sub app.

C++ Type:std::vector

Options:

Description:Additional command line arguments to pass to the sub apps. If one set is provided the arguments are applied to all, otherwise there must be a set for each sub app.

• clone_master_meshFalseTrue to clone master mesh and use it for this MultiApp.

Default:False

C++ Type:bool

Options:

Description:True to clone master mesh and use it for this MultiApp.

• execute_onTIMESTEP_BEGINThe list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, FINAL, CUSTOM.

Default:TIMESTEP_BEGIN

C++ Type:ExecFlagEnum

Options:NONE INITIAL LINEAR NONLINEAR TIMESTEP_END TIMESTEP_BEGIN FINAL CUSTOM

Description:The list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, FINAL, CUSTOM.

• global_time_offset0The time offset relative to the master application for the purpose of starting a subapp at different time from the master application. The global time will be ahead by the offset specified here.

Default:0

C++ Type:double

Options:

Description:The time offset relative to the master application for the purpose of starting a subapp at different time from the master application. The global time will be ahead by the offset specified here.

• keep_full_output_historyFalseWhether or not to keep the full output history when this multiapp has multiple entries

Default:False

C++ Type:bool

Options:

Description:Whether or not to keep the full output history when this multiapp has multiple entries

• keep_solution_during_restoreFalseThis is useful when doing Picard. It takes the final solution from the previous Picard iterationand re-uses it as the initial guess for the next picard iteration

Default:False

C++ Type:bool

Options:

Description:This is useful when doing Picard. It takes the final solution from the previous Picard iterationand re-uses it as the initial guess for the next picard iteration

• library_nameThe file name of the library (*.la file) that will be dynamically loaded.

C++ Type:std::string

Options:

Description:The file name of the library (*.la file) that will be dynamically loaded.

• library_pathPath to search for dynamic libraries (please avoid committing absolute paths in addition to MOOSE_LIBRARY_PATH)

C++ Type:std::string

Options:

Description:Path to search for dynamic libraries (please avoid committing absolute paths in addition to MOOSE_LIBRARY_PATH)

• max_procs_per_app4294967295Maximum number of processors to give to each App in this MultiApp. Useful for restricting small solves to just a few procs so they don't get spread out

Default:4294967295

C++ Type:unsigned int

Options:

Description:Maximum number of processors to give to each App in this MultiApp. Useful for restricting small solves to just a few procs so they don't get spread out

• move_appsApps, designated by their 'numbers' starting with 0 corresponding to the order of the App positions, to be moved at move_time to move_positions

C++ Type:std::vector

Options:

Description:Apps, designated by their 'numbers' starting with 0 corresponding to the order of the App positions, to be moved at move_time to move_positions

• move_positionsThe positions corresponding to each move_app.

C++ Type:std::vector

Options:

Description:The positions corresponding to each move_app.

• move_time1.79769e+308The time at which Apps designated by move_apps are moved to move_positions.

Default:1.79769e+308

C++ Type:double

Options:

Description:The time at which Apps designated by move_apps are moved to move_positions.

• no_backup_and_restoreFalseTrue to turn off backup/restore for this multiapp. This is useful when doing steady-state Picard iterations where we want to use the solution of previous Picard iteration as the initial guess of the current Picard iteration

Default:False

C++ Type:bool

Options:

Description:True to turn off backup/restore for this multiapp. This is useful when doing steady-state Picard iterations where we want to use the solution of previous Picard iteration as the initial guess of the current Picard iteration

• output_in_positionFalseIf true this will cause the output from the MultiApp to be 'moved' by its position vector

Default:False

C++ Type:bool

Options:

Description:If true this will cause the output from the MultiApp to be 'moved' by its position vector

• positionsThe positions of the App locations. Each set of 3 values will represent a Point. This and 'positions_file' cannot be both supplied. If this and 'positions_file' are not supplied, a single position (0,0,0) will be used

C++ Type:std::vector

Options:

Description:The positions of the App locations. Each set of 3 values will represent a Point. This and 'positions_file' cannot be both supplied. If this and 'positions_file' are not supplied, a single position (0,0,0) will be used

• positions_fileA filename that should be looked in for positions. Each set of 3 values in that file will represent a Point. This and 'positions' cannot be both supplied

C++ Type:std::vector

Options:

Description:A filename that should be looked in for positions. Each set of 3 values in that file will represent a Point. This and 'positions' cannot be both supplied

• relaxation_factor1Fraction of newly computed value to keep.Set between 0 and 2.

Default:1

C++ Type:double

Options:

Description:Fraction of newly computed value to keep.Set between 0 and 2.

• relaxed_variablesList of variables to relax during Picard Iteration

C++ Type:std::vector

Options:

Description:List of variables to relax during Picard Iteration

• reset_appsThe Apps that will be reset when 'reset_time' is hit. These are the App 'numbers' starting with 0 corresponding to the order of the App positions. Resetting an App means that it is destroyed and recreated, possibly modeling the insertion of 'new' material for that app.

C++ Type:std::vector

Options:

Description:The Apps that will be reset when 'reset_time' is hit. These are the App 'numbers' starting with 0 corresponding to the order of the App positions. Resetting an App means that it is destroyed and recreated, possibly modeling the insertion of 'new' material for that app.

• reset_time1.79769e+308The time at which to reset Apps given by the 'reset_apps' parameter. Resetting an App means that it is destroyed and recreated, possibly modeling the insertion of 'new' material for that app.

Default:1.79769e+308

C++ Type:double

Options:

Description:The time at which to reset Apps given by the 'reset_apps' parameter. Resetting an App means that it is destroyed and recreated, possibly modeling the insertion of 'new' material for that app.

### Optional Parameters

• control_tagsAdds user-defined labels for accessing object parameters via control logic.

C++ Type:std::vector

Options:

Description:Adds user-defined labels for accessing object parameters via control logic.

• enableTrueSet the enabled status of the MooseObject.

Default:True

C++ Type:bool

Options:

Description:Set the enabled status of the MooseObject.

• use_displaced_meshFalseWhether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.

Default:False

C++ Type:bool

Options:

Description:Whether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.