SDT-nlsim         Contents     Functions              PDF Index

hbm_post

• ZTraj[,Get,GetBnl,Set,SetDef]
• AddPost
• Init
• XF.[GetData,X,Y,Xlab]
• XF.set
• XF.Stack

Purpose

Commands for result post-processing. This functions provides post-treatment commands and handles the HBM result object.

Description

ZTraj[,Get,GetBnl,Set,SetDef]

Trajectory generation as harmonic result structures Zcurve from synthesis of given shapes.

• Command ZTraj generates a harmonic response associated to a given trajectory.
  Z=hbm_post('ZTraj',model,def);

  model is a standard SDT-NL model, def is a def curve expressed on the model DOF, typically a modeshape. The output is a HBM output Z. The model is HBM-assembled and data are initialized based on model.Stack{info,HBMOpt} or using the default options output by hbm_solve Opt. If the def curve is real, the output will be initialized with the shape on the c1 harmonic, the pulsation is initialized by def.data(:,1). If complex, the c1 harmonic is set to the real part and s1 to the opposite of the imaginary part, the pulsation is initialized by def.data(:,1).

  The output of hbm_post ZTraj cannot directly be exploited by other ZTraj commands as an observation (see hbm_solve AddPost) must be declared prior to generating the the HBM results object allowing response synthesis. The following command options are supported

  • -res to output the result in .Res format.
  • -reAss to force reassembly of the model.
  • -TKT to perform model projection on def.TR.
  • -harm to specify harmonics to be used for the results format (by default the first harmonic is used).
  • -useq0 in conjunction with -TKT to use the static state model.Stack{curve,q0} in the trajectory, the static state will increase def.TR prior to projection.
  • -q0inTR to detect the zero harmonic in def.TR (as with def.data(:,1)<1), thus initializing different generalized harmonic DOF for the zero harmonic and the others. This option is handled internally if useq0 is used.
• Command ZTrajSet updates the HBM results object Z with different harmonics.
  XF=hbm_post('ZTrajSet',XF,RA);
  XF is the HBM results object, RA is a structure with field .harm defining the new set of harmonics.
• Command ZTrajSetDef only updates the HBM curve Z with a new trajectory based on the same harmonic DOF than the initial one.
  XF=hbm_post('ZTrajSetDef',XF,struct,opt,struct,d1);, with XF the HBM results object, opt the opt structure, d1 the new shape.
• Command ZTrajGet synthesizes and outputs a transient NL trajectory (in the standard fe_timeNL format) based on one of the state of the provided HBM results object.
  def=hbm_post('ZTrajGet',XF,RO);. The following command options are supported
  • nTSampval to set the number of time samples to val in the output.
  • NoT to generate a trajectory based on the model DOF.
  • iModeind to select the state index ind in the HBM results object.
  • coefval to apply an amplitude coefficient val to the state.
  • NeelUNLval to output the non-linearity observations. Set val to a two digit number [unl vnl] set to 1 if needed, 0 otherwise to obtain def.FNL.unl and/or def.FNL.vnl.
  • initnl to perform and keep initializations necessary to optimized trajectory update by linear state coefficient application with hbm_solve @defUpCoef.
  • NoStat to ignore unl0 and vnl0 in the observation and evaluation of non-linear forces.
• Command ZTrajGetBnl outputs the non-linear harmonic forces based on the provided HBM results object.
  bnl=hbm_post('ZTrajGetBnl',XF,RO);.
  XF is a HBM results object, RO is an option structure with optional field .nTSamp to specify the time sampling number used to evaluate the harmonic non-linear forces.

AddPost

Handles observations declarations for post-treatments from the HBM curve output to the HBM results object.
hbm_post('AddPost',job,data); is used to handle outputs stored in the application. job is the name on which the observation will be applied (entry in PA.Stack). data provides the observation, it can be of the following types

• A DOF list in numeric format
• An observation struct, with fields .cta an observation matrix and .DOF the associated DOF vector. struct('cta',1,'DOF',21.03,'name','tip'). Appends the SensDof entry in the model PA.Stack{job}.
• A model. If field .DOF is present, it is directly used, otherwise DOF are obtained from the .Node field.

For all cases, a Sens data structure is generated and a SensDof entry is added to the model PA.Stack{job}2. The GUI then adds the observation to the available observation list.

Manual handling outside the GUI requires the use of a results structure RE as a third argument. The same operations are performed, the observation list stored in RE.PostSensList being updated RE=hbm_post('AddPost',lab,data,RE);.

Init

Initializes the HBM result object.
XF=hbm_post('Init',UI,ci);.

UI is a variable pointing to the HBM solver output data. It can be left empty, in such case it is initialized by UI=hbmui('PARAMUI'), or it is a results structure with mandatory fields .Res (see hbm_post ZTraj-Res) and .PostSensList (see hbm_postAddPost). ci is a iiplot object that will host the results display. It can be left empty not to display results.

If results are stored in the application, the HBM result object associated to the current application state can be recovered using XF=hbm_post('init').

Manual initialization with no display can be performed from an assembled harmonic model mo1 and a HBM curve output structure Z using

RE=struct('Res',{{Z.name,{Z,mo1}}});
RE=hbm_post('addPost',Z.name,mo1.DOF,RE);
XF=hbm_post('init',RE,[]);

HBM results object

The HBM results object provides methods to synthesize transfers or transient trajectories based on a HBM result, it is based on the curvemodel object that is a SDT curve wrapper. The result object is initialized using hbm_post Init.

XF.[GetData,X,Y,Xlab]

Provides access to the resolved content of the HBM result object XF in its current state.
X=XF.X;
Warning: depending on the current object state, recovering the full output can be a very intensive task and may generate a very large volume of data !

The .GetData method returns the full curve structure synthesized for the current object state. The other methods only return the field corresponding to their name.

XF.set

HBM results object options handling.
XF.set('nTSamp',100);

For an app linked object, the options are available in the GUI Post tab. This programmatic way can be used in scripts interacting with the GUI, or with results objects not linked with the GUI.

XF.Stack

Provides access to HBM results context data. The object mode can be programmatically altered through this way.
XF.Stack'type'=val;

Accepted types for val are

• Freq To handle maximum amplitude frequency responses.
• Time To handle transient responses.
• Harm To handle Harmonic contribution responses.
• FFT-1 To handle FFT of the first harmonic transient response.