Builder (alpha)

This is an Alamo input file builder for the Integrator::Flame method. Enter values for the Alamo parameters, and an input file is generated at the bottom of this page. Required parameters are indicated with red inputs. Default values are indicated with placeholder values, and will not be included in the input unless you put it in specifically.

Warning

This is a new and very experimental Alamo feature. This form is entirely auto-generated based on the Alamo code base using the code scrapers. It is not currently complete (there are some known params that are not included) and it is also not yet thoroughly tested.

Please use with caution.

Dynamic Form with Nested Sections

Integrator::Flame inputs

plot_field
pf.eps
pf.kappa
pf.lambda
pf.w1
pf.w12
pf.w0

pf.eta.bc.type

This is the most commonly used standard boundary condition implementation. The name "Constant" refers to the invariance of the BC value or character along each face of the simulation domain; however, you may cause a change in the value with time by using a :ref:`Numeric::Interpolator::Linear` string. The BC on each face is specified with a :code:`type` string that specifies the nature of the BC, and a :code:`val` that specifies the value. By default, all types are Dirichlet and all values are 0.0. The complete list of BC types are below: `Dirichlet `_ boundary condition types can be specified with :code:`Dirichlet`, :code:`dirichlet`, :code:`EXT_DIR`. `Neumann `_ boundary condition types are specified with :code:`Neumann`, :code:`neumann`. `Periodic `_ boundary conditions can be specified with :code:`Periodic`, :code:`periodic`, :code:`INT_DIR`. **Important**: Ensure that your geometry is specified to be periodic using :code:`geometry.is_periodic`. For instance, if periodic in x, set to :code:`1 0 0` The BC values can be specified either as a number (e.g. :code:`1.0`) or using a linear interpolator string (e.g. :code:`(0,1:2.3,-0.1)`). The number of values and types must be either 0 (for defaults), 1 (to set the same for all field components) or N (where N=number of field components).

pf.eta.bc.constant.type.xlo
pf.eta.bc.constant.type.xhi
pf.eta.bc.constant.type.ylo
pf.eta.bc.constant.type.yhi
pf.eta.bc.constant.type.zlo
pf.eta.bc.constant.type.zhi
pf.eta.bc.constant.val.xlo
pf.eta.bc.constant.val.xhi
pf.eta.bc.constant.val.ylo
pf.eta.bc.constant.val.yhi
pf.eta.bc.constant.val.zlo
pf.eta.bc.constant.val.zhi

Create a single laminate with specified orientation, thickness, and offset.

pf.eta.ic.laminate.number_of_inclusions
pf.eta.ic.laminate.orientation
pf.eta.ic.laminate.eps
pf.eta.ic.laminate.mollifier
pf.eta.ic.laminate.singlefab
pf.eta.ic.laminate.invert

Basic IC that just sets the entire field to a constant value. Works with a single or multiple-component field.

pf.eta.ic.constant.value

Initialize a field using a mathematical expression. Expressions are imported as strings and are compiled real-time using the `AMReX Parser `_. Works for single or multiple-component fields. Use the :code:`regionN` (N=0,1,2, etc. up to number of components) to pass expression. For example: .. code-block:: bash ic.region0 = "sin(x*y*z)" ic.region1 = "3.0*(x > 0.5 and y > 0.5)" for a two-component field. It is up to you to make sure your expressions are parsed correctly; otherwise you will get undefined behavior. :bdg-primary-line:`Constants` You can add constants to your expressions using the :code:`constant` directive. For instance, in the following code .. code-block:: bash psi.ic.type=expression psi.ic.expression.constant.eps = 0.05 psi.ic.expression.constant.R = 0.25 psi.ic.expression.region0 = "0.5 + 0.5*tanh((x^2 + y^2 - R)/eps)" the constants :code:`eps` and :code:`R` are defined by the user and then used in the subsequent expression. The variables can have any name made up of characters that is not reserved. However, if multiple ICs are used, they must be defined each time for each IC.

pf.eta.ic.expression.coord
pf.eta.ic.expression.region

Initialize a field using a bitmap image. (2D only) Note that in GIMP, you must select "do not write color space information" and "24 bit R8 G8 B8" when exporting the BMP file.

pf.eta.ic.bmp.filename
pf.eta.ic.bmp.fit
pf.eta.ic.bmp.coord.lo
pf.eta.ic.bmp.coord.hi
pf.eta.ic.bmp.channel
pf.eta.ic.bmp.min
pf.eta.ic.bmp.max

Initialize a field using a PNG image. (2D only)

pf.eta.ic.png.channel
pf.eta.ic.png.filename
pf.eta.ic.png.fit
pf.eta.ic.png.coord.lo
pf.eta.ic.png.coord.hi
pf.eta.ic.png.min
pf.eta.ic.png.max

propellant.type

This SCP model implements the method described in the following paper .. bibliography:: :list: none :filter: False kanagarajan2022diffuse This method imitates inheritance :code:`Propellant::Propellant` using static polymorphism

propellant.powerlaw.gamma
propellant.powerlaw.r_ap
propellant.powerlaw.r_htpb
propellant.powerlaw.r_comb
propellant.powerlaw.n_ap
propellant.powerlaw.n_htpb
propellant.powerlaw.n_comb
propellant.powerlaw.deltaw

This SCP model implements the method described in the following paper .. bibliography:: :list: none :filter: False meier2024diffuse This method imitates inheritance :code:`Propellant::Propellant` using static polymorphism

propellant.fullfeedback.phi.zeta
propellant.fullfeedback.phi.zeta_0
propellant.fullfeedback.a1
propellant.fullfeedback.a2
propellant.fullfeedback.a3
propellant.fullfeedback.b1
propellant.fullfeedback.b2
propellant.fullfeedback.b3
propellant.fullfeedback.c1
propellant.fullfeedback.pressure.dependency
propellant.fullfeedback.mlocal_ap
propellant.fullfeedback.mlocal_comb
propellant.fullfeedback.rho_ap
propellant.fullfeedback.rho_htpb
propellant.fullfeedback.k_ap
propellant.fullfeedback.k_htpb
propellant.fullfeedback.cp_ap
propellant.fullfeedback.cp_htpb
propellant.fullfeedback.m_ap
propellant.fullfeedback.m_htpb
propellant.fullfeedback.E_ap
propellant.fullfeedback.E_htpb
propellant.fullfeedback.mob_ap
propellant.fullfeedback.bound

propellant.homogenize.dispersion1
propellant.homogenize.dispersion2
propellant.homogenize.dispersion3
propellant.homogenize.rho_ap
propellant.homogenize.rho_htpb
propellant.homogenize.k_ap
propellant.homogenize.k_htpb
propellant.homogenize.cp_ap
propellant.homogenize.cp_htpb
propellant.homogenize.h1
propellant.homogenize.h2
propellant.homogenize.massfraction
propellant.homogenize.mlocal_ap
propellant.homogenize.m_ap
propellant.homogenize.m_htpb
propellant.homogenize.E_ap
propellant.homogenize.E_htpb
propellant.homogenize.mob_ap
propellant.homogenize.bound
thermal.on
thermal.Tref
thermal.hc
thermal.Tfluid
thermal.temp.bc
laser.ic
temp.ic
chamber.pressure
variable_pressure
amr.refinement_criterion
amr.refinement_criterion_temp
amr.refinament_restriction
amr.phi_refinement_criterion
small
phi.ic
elastic.on
elastic.traction
elastic.phirefinement

elastic

elastic.type
elastic.time_evolving
elastic.plot_disp
elastic.plot_rhs
elastic.plot_psi
elastic.plot_stress
elastic.plot_strain

elastic.solver

elastic.viscous.mu_dashpot
elastic.viscous.mu_newton
elastic.velocity.ic.type

elastic.bc.type

This BC defines boundary conditions that are constant with respect to space. However they may change in time using the :ref:`Numeric::Interpolator::Linear` method. In 2D, BCs are prescribed for each edge (4) and corner (4) on the boundary, for a total of 8 possible regions. In 3D, BCs are prescribed for each face (6), each edge (12), and each corner (8), for a total of 26 possible regions. Care must be taken to define BCs for edges/corners consistently with the faces/edges, or you will get poor convergence and inaccurate behavior. (See :ref:`BC::Operator::Elastic::TensionTest` for a reduced BC with streamlined load options.) To define a boundary condition, you must define both a "type" and a "value" in each direction. The type can be "displacement", "disp", "neumann", "traction", "trac". The value is the corresponding value. All BCs are, by default, dirichlet (displacement) with a value of zero.

bc.constant.type.xloylozlo
bc.constant.type.xloylozhi
bc.constant.type.xloyhizlo
bc.constant.type.xloyhizhi
bc.constant.type.xhiylozlo
bc.constant.type.xhiylozhi
bc.constant.type.xhiyhizlo
bc.constant.type.xhiyhizhi
bc.constant.type.ylozlo
bc.constant.type.ylozhi
bc.constant.type.yhizlo
bc.constant.type.yhizhi
bc.constant.type.zloxlo
bc.constant.type.zloxhi
bc.constant.type.zhixlo
bc.constant.type.zhixhi
bc.constant.type.xloylo
bc.constant.type.xloyhi
bc.constant.type.xhiylo
bc.constant.type.xhiyhi
bc.constant.type.xlo
bc.constant.type.xhi
bc.constant.type.ylo
bc.constant.type.yhi
bc.constant.type.zlo
bc.constant.type.zhi
bc.constant.val.xloylozlo
bc.constant.val.xloylozhi
bc.constant.val.xloyhizlo
bc.constant.val.xloyhizhi
bc.constant.val.xhiylozlo
bc.constant.val.xhiylozhi
bc.constant.val.xhiyhizlo
bc.constant.val.xhiyhizhi
bc.constant.val.ylozlo
bc.constant.val.ylozhi
bc.constant.val.yhizlo
bc.constant.val.yhizhi
bc.constant.val.zloxlo
bc.constant.val.zloxhi
bc.constant.val.zhixlo
bc.constant.val.zhixhi
bc.constant.val.xloylo
bc.constant.val.xloyhi
bc.constant.val.xhiylo
bc.constant.val.xhiyhi
bc.constant.val.xlo
bc.constant.val.xhi
bc.constant.val.ylo
bc.constant.val.yhi
bc.constant.val.zlo
bc.constant.val.zhi

A boundary condition for mechanics operators that simplifies frequently-used conditions for uniaxial loading. Types include: - :code:`uniaxial_stress_clamp`: fixes both ends and allows for stress concentrations at the corners. - :code:`uniaxial_kolsky` - :code:`uniaxial_stress`: 1D stress problem - :code:`uniaxial_strain`: 1D strain problem

bc.tensiontest.type
bc.tensiontest.disp
bc.tensiontest.trac

Use expressions to define space and time varying boundary conditions for elastic problems.

elastic.print_model

elastic.rhs.type

Basic IC that just sets the entire field to a constant value. Works with a single or multiple-component field.

rhs.constant.value

Initialize a field using a mathematical expression. Expressions are imported as strings and are compiled real-time using the `AMReX Parser `_. Works for single or multiple-component fields. Use the :code:`regionN` (N=0,1,2, etc. up to number of components) to pass expression. For example: .. code-block:: bash ic.region0 = "sin(x*y*z)" ic.region1 = "3.0*(x > 0.5 and y > 0.5)" for a two-component field. It is up to you to make sure your expressions are parsed correctly; otherwise you will get undefined behavior. :bdg-primary-line:`Constants` You can add constants to your expressions using the :code:`constant` directive. For instance, in the following code .. code-block:: bash psi.ic.type=expression psi.ic.expression.constant.eps = 0.05 psi.ic.expression.constant.R = 0.25 psi.ic.expression.region0 = "0.5 + 0.5*tanh((x^2 + y^2 - R)/eps)" the constants :code:`eps` and :code:`R` are defined by the user and then used in the subsequent expression. The variables can have any name made up of characters that is not reserved. However, if multiple ICs are used, they must be defined each time for each IC.

rhs.expression.coord
rhs.expression.region

This is an old-fashioned IC. It is kept because it is still used with the Trig regression test, but it is recommended to use IC::Expression instead.

rhs.trig.nr
rhs.trig.ni
rhs.trig.dim
rhs.trig.alpha
elastic.interval
elastic.max_coarsening_level
elastic.print_residual
elastic.elastic_ref_threshold
elastic.zero_out_displacement
elastic.tstart
Telastic

model_ap

model_ap.F0
model_ap.eps0

model_htpb

model_htpb.F0
model_htpb.eps0
allow_unused

Alamo input file