Directory Layout
The
following model directory layout is recommended:
Vehicle(s)
|
|-Event
| |-Data
| | |-Test
| | | |-Film
| | | | |-Raw
| | | |-Instr
| | | |-Raw
| | |-VeCor
| | |-Model
| |-Model
| |-Ext.Wt
| |-Ext
| |-Sim
| |-SimEvent
|
|-MulEvent
|-Model
|-Ext.Wt
| |-Event
|-Ext
| |-Event
|-Sim
| |-Event
|-SimEvent
|
Vehicle(s) descriptor
Event descriptor
Film motion data
Raw film motion data
Instrument signals
Raw instrument signals
VeCor preprocessing
Modeling input data (preprocessed and averaged/summed)
Test/event model
Weight extraction
Model extraction
Resimulation of extraction event
Simulation of some other Event
Multiple-event model directory
Model identifier or simply "Model"
Weight extraction
For each event
Model extraction
For each event
Resimulation of extraction events
For each event
Simulation of some other Event |
SISAME Input
File Naming
SISAME
Input Files
Vehicle.ext
Vehicle.mdl
Vehicle.sim |
Extraction
Extracted model
Simulation |
SISAMEM
Input Files
Vehicle.mev
Vehicle.mev |
Weight extraction
Model extraction |
SISAME Input
File Usage
Path
Names
For
cross-platform input files use relative path names: the applications
can translate relative paths to the host platform format automatically.
Standard
Model ID Codes and File Extensions
MassID
Code |
File
Extension |
Description |
OccComp
Engine
EngineTop
EngineBot
Wheels
WheelL
WheelR
WheelsF
WheelFL
WheelFR
WheelsR
WheelRL
WheelRR
FrontXMem
Interface
InterfaceL
InterfaceR |
Occ
Eng
EnT
EnB
Whe
WhL
WhR
WhF
WFL
WFR
WhR
WRL
WRR
FXM
Int
InL
InR |
Occupant
Compartment
Engine
Engine - Top
Engine - Bottom
Front Wheels/Suspension
Left Front Wheel/Suspension
Right Front Wheel/Suspension
Front Wheels/Suspension
Front Left Wheel/Suspension
Front Right Wheel/Suspension
Rear Wheels/Suspension
Rear Left Wheel/Suspension
Rear Right Wheel/Suspension
Front Frame X-Member
Interface
Interface - Left
Interface - Right |
SprID
Code |
File
Extension |
Description |
Occ-Bar
Radiator
Wheels-Bar
FrontFrame
Firewall
Occ-Wheels
RearFrame
EngineMt
Suspension |
OcB
Rad
WhB
FrF
Fir
OcW
ReF
EnM
Sus |
OccComp to
Barrier
Engine to Barrier
Front Wheels/Suspension to Barrier
Front X-Member to Barrier
OccComp to Engine
OccComp to Front Wheels/Suspension
OccComp to Front X-Member
Front X-Member to Engine
Front X-Member to Front Wheels |
FrcID
Code |
File
Extension |
Description |
InertiaFrc |
InF |
Total inertia
of all masses for weight extraction |
Model Documentation
Create
and maintain documentation files for each vehicle and each event as
per those in the SISAME Model Library.
Vehicle
Instrument Signal Preparation
The
NHTSA Tools applications such as UDSMod, UDSTool, and Scale can be used
to prepare UDS vehicle signal files for SISAME modeling use. For example:
-
Set
file name extensions based on standard component ID codes
-
Clear
nonblank SENLOC and OCCTYP fields
-
Change
AXIS from XL to XG
-
Check/fix
forces mis-scaled by 103 or 106 or -1 (barrier
contact forces should be positive)
The
instrument signals should be visually examined:
-
Instrument
failures: eliminate signals with large nonsystematic errors
-
Acceleration/force
signal tail bias
-
Acceleration
signal first and second integrals
Film Data Collection/Preparation
If
test film analysis is available, collect displacements for the full
instrument signal time span for the:
Convert
the film displacements to UDS files using Film2UDS or another procedure
using UDSMod. An instrument signal UDS file can be used to set the baseline
specifications and then modified as follows:
-
Set
DEL to the film time step value
-
Set
SENATT to the film target location
-
Set
INIVEL and CLSSPD
-
Set
AXIS=XG
-
Check
for film time step and displacement scaling errors (look at velocity
before t=0)
Name
the film displacement UDS files using the form v1234daV.Ext
where 1234 stands for the test number, V is the vehicle
model letter code, and Ext is the standard file extension for
the target component.
Collect
film displacement target values for use in VeCor at 100, 200, and 300
ms (but at least 10 ms before final tail to allow for time shifting). A
30 Hz zero-phase-shift filter is recommended prior to sampling film
data.
Modeling
General
Weight
Extraction
-
Run
weight extraction if VTB test with barrier force or VTV test
-
Specify
known vehicle weight(s)
-
First
run with no weight estimates/bounds to assess inertial completeness of the signal set
-
Then
run using weight estimate/bound information: if fit degrades significantly
try looser estimates/bounds
Model
Extraction
-
First
run with all possible load-paths present to get best-case fit
-
Start
with StaType=SI for deforming load-paths with unknown behavior and
change those with simple extracted behavior to simpler types
-
Use
Symmetric=True load-paths when the primary deflection direction
may vary between matching/referenced structures in single or multiple
events
-
Enforce
known structural symmetries using references
Dynamic
extraction
Static
and dynamic contributions may not be clearly distinguishable from the
instrument data alone, particularly in single-event extractions, so
dynamic parameter estimate/bound specifiers are recommended. The dynamic
parameter specifiers shown below provide a good starting point.
Single
Event Extractions
Metric
DynType=LM
MSlp=?( ~0[2.5] )
DynType=AM
MSlp=?( ~0[5] ) MMax=?( ~1[100] )
English
DynType=LM
MSlp=?( ~0[4] )
DynType=AM
MSlp=?( ~0[8] ) MMax=?( ~1[100] )
Multiple
Event Extractions
Metric
DynType=LM
MSlp=?( ~0[5] )
DynType=AM
MSlp=?( ~0[10] ) MMax=?( ~1[200] )
English
DynType=LM
MSlp=?( ~0[8] )
DynType=AM
MSlp=?( ~0[16] ) MMax=?( ~1[200] )
Refining
Dynamic Specifiers
-
LM
magnifiers provide a simpler and more efficient extraction process
-
AM magnifiers
can represent a broader range of behavior but at some cost in efficiency
-
Adjust
AM specifiers to avoid both MSlp and MMax having
sufficiently large values to give unrealistic magnification
-
AM magnifiers with
sufficiently large (MMax-1)/MSlp ratios can be replaced by more efficient LM
magnifiers
|