Plotting control parameters

@PLOTTING_CONTROL_PARAMETERS {
@PLOTTING_CONTROL_PARAMETERS_NAME {PltCtrlName} {
@GRAPH_PLOT_FORMAT {CrpPF1, CrpPF2, CrpPF3}
@GRAPH_PLOT_SIZE {CrpPS1, CrpPS2, CrpPS3}
@MAP_PLOT_FORMAT {MapPF1, MapPF2, MapPF3}
@MAP_PLOT_SIZE {MapPS1, MapPS2, MapPS3}
@OBJECT_PLOT_FORMAT {ObjPF1, ObjPF2, ObjPF3}
@OBJECT_PLOT_SIZE {ObjPS1, ObjPS2, ObjPS3}
@SENSOR_PLOT_FORMAT {SenPF1, SenPF2, SenPF3}
@SENSOR_PLOT_SIZE {SenPS1, SenPS2, SenPS3}
@SIGNAL_PLOT_FORMAT {SigPF1, SigPF2, SigPF3}
@SIGNAL_PLOT_SIZE {SigPS1, SigPS2, SigPS3}
@SURVEY_PLOT_FORMAT {SvyPF1, SvyPF2, SvyPF3}
@SURVEY_PLOT_SIZE {SvyPS1, SvyPS2, SvyPS3}
@TIME_LABEL {timeLabel}
@INITIAL_TIME {t0}
@TIME_NORMALIZATION {T}
@NORMALIZED_TIME_RANGE {τi, τf}
@SENSOR_MEMORY_SIZE {SensorMemSize}
@MAP_MEMORY_SIZE {MapMemSize}
@COMMENTS {CommentText}
}
}

Notes

  1. This section defines the parameters that control the plotting of the model objects and simulation predictions as requested by sensors, maps, surveys, or cross-plots. The plotting package used to generate the plots is GNUPLOT version 4.4.
  2. The following model objects will generate plots.
    • Airfoil tables: the lift, drag and moment coefficients are plotted as a function of angle of attack for each Mach number.
    • Beam properties: the bending, shearing and mass properties of the beam are plotted along its span.
    • Cable properties: the stiffness mass properties of the cable are plotted along its span.
    • Curves: the geometry of the curve is plotted in three different views from the three inertial axes. If a triad table is defined, the orientation of the triad is also plotted along the curve.
    • Dampers: the force (or moment) in the damper is plotted as a function of damper velocity (or angular velocity).
    • Springs: the force (or moment) in the spring is plotted as a function of stretch (or relative rotation).
    • Time functions: the time function is plotted as a function of time.
  3. The following items also generate plots.
    • Cross-plots: the output quantities of the graph are plotted as a function of time or space.
    • Maps: the output quantities of the map are plotted as a function of time and space, or over a spatial domain.
    • Sensors: the output quantities of the sensor are plotted as a function of time.
    • Signals: the output quantities of the signal are plotted as a function of time.
    • Surveys: the output quantities of the survey are plotted as a function of space.
  4. Up to three different formats, CrpPF1, CrpPF2, CrpPF3 for cross-plots, MapPF1, MapPF2, MapPF3 for maps, ObjPF1, ObjPF2, ObjPF3 for model objects, SenPF1, SenPF2, SenPF3 for sensors, SigPF1, SigPF2, SigPF3 for signals, or SvyPF1, SvyPF2, SvyPF3 for surveys, can be requested. The following formats are available.
    • EPS: Plots will be generated in the Encapsulated Postscript format; individual plots can be readily incorporated in electronic documents.
    • PNG: Plots will be generated in the Portable Network Graphics format; individual plots are included in the html file documenting the simulation. It is recommended that this format be requested.
    • TRM: Plots will be generated in Terminal format; all plots will appear on the screen.
  5. The size of the plots, CrpPS1, CrpPS2, CrpPS3 for cross-plots, MapPS1, MapPS2, MapPS3 for maps, ObjPS1, ObjPS2, ObjPS3 for model objects, SenPS1, SenPS2, SenPS3 for sensors, SigPS1, SigPS2, SigPS3 for signals, or SvyPS1, SvyPS2, SvyPS3 for surveys, can be controlled for each of the requested formats. The following sizes are available.
    • SMALL: For the PNG format, this corresponds to 640 by 480 pixels. For the other formats, the actual size of the plot depends of the media use to display it.
    • MEDIUM: For the PNG format, this corresponds to 800 by 600 pixels. For the other formats, the actual size of the plot depends of the media use to display it.
    • LARGE: For the PNG format, this corresponds to 1000 by 750 pixels. For the other formats, the actual size of the plot depends of the media use to display it.
  6. Sensor output files are generated during the finite element phase of the analysis, see section~\ref{ProCtrl: Analysis Phases}, as explained in section~\ref{ProCtrl: Processing Signals}. To avoid opening and closing sensor files at each time step of the analysis, a certain amount of memory is allocated for each sensor; this memory is sufficient to store SensorMemSize steps of sensor output. Once this memory is full, the data is written to the sensor file. Increasing SensorMemSize will slightly speed up the simulation since less time will be spent opening and closing sensor files; of course, this is achieved at the expense or requiring additional memory during the simulation. On the other hand, as soon as sensor data is written to the sensor files, it becomes available for plotting. Increasing SensorMemSize will decrease the rate at which sensor data becomes available.
  7. The parameter MapMemSize controls the size of the memory associated with maps. It function for maps is identical to that of the parameter SensorMemSize for sensors.
  8. It is possible to attach comments to the definition of the object; these comments have no effect on its definition.

Examples

Example 1.

For both model objects and simulation results, three plot formats are requested, PNG, EPS, PS; PNG plot will be 1000 by 750 pixels. For maps, TRM format is requested as this will allows interactive rotation of the map on the terminal screen.

PLOTTING_CONTROL_PARAMETERS {
@PLOTTING_CONTROL_PARAMETERS_NAME {PlottingControlParameters} {
@MAP_PLOT_FORMAT {PNG,EPS,TRM}
@MAP_PLOT_SIZE {LARGE,MEDIUM,MEDIUM}
@OBJECT_PLOT_FORMAT {PNG,EPS,PS}
@OBJECT_PLOT_SIZE {LARGE,MEDIUM,MEDIUM}
@SENSOR_PLOT_FORMAT {PNG,EPS,PS}
@SENSOR_PLOT_SIZE {LARGE,MEDIUM,MEDIUM}
}
}