SDT-base         Contents     Functions              PDF Index

3.5  SDT numerical experiments (DOE)

A systematic process has been defined to standardize computations and associated parametric studies. An experiment is described by a list of strings stored as nmap('CurExp') entry. For example

RT=d_doe('nmap.Hbm.Gart');RT.nmap('CurExp')
%    {'MeshCfg{d_fetime(Gart),VtGart}',';'
%      'SimuCfg{ModalNewmark{$dt$,10,fc,chandle1}}',';'
%   'RunCfg{Reduce}' }

Each string corresponds to a step (called level fe_range Loop since steps can be organized in a tree). Standard steps are described below

• MeshCfg, 10 Mesh configuration : defines the FEM, sensor and loading locations. To stop at the default implementation set a break point using sdtweb _bp sdtsys stepMesh. 'MeshCfg{d_fetime(Gart):VtGart:None}' is split into 3 sub steps
  • Mesh (level 10.1), generating the mesh where the callback function is d_fetime, called with command MeshGart.
  • Case (level 10.2), adding case (boundary conditions, ...) using call d_fetime('CaseVtGart').
  • NL (level 10.3), adding non linearity information using d_fetime('CaseNLNone')
• SimuCfg, 20
• RunCfg, 30 list of run steps given as a comma separated list. If you need to debug usage, use sdtweb('_bp','sdtsys','steprun'). Standardized steps are
  • xxxGV Step{curStep%s,out%s} Time calls fe_time.
  • eig calls fe_eig.
  • Time calls fe_time.
  • Strings that correspond to nmap keys are replaced by the corresponding value. For example in above the Reduce key has value 'nl_solve(ReducFree 2 NM 1e3 -Float2 -SetDiag -SE)' where the NM is replaced by the current value of nmap('NM').

Looping on a range of experiments, needs to be documented. URN with key replacement.