Codes in THOR/WS deflection with FL2 = 03

Help in understanding TS 13499
Locked
DiVe
Posts: 411
Joined: Tue Apr 24, 2007 9:14 am
Company: IAT mbh
Location: IAT Berlin - Germany
Contact:

Codes in THOR/WS deflection with FL2 = 03

Post by DiVe »

Dear colleagues,

we have seen in the wild some channels for the chest/abdomen deflection that have been coded in a special way.
So there are channels for the angle measurements, that occur twice with different naming:
WS_Angle-ANZ.png
WS_Angle-ANZ.png (27.51 KiB) Viewed 2966 times

(the column "Langname" will show the code with the rib number associated)

For the WorldSID thoracic ribs this will end in three channels with the same coding
for the thorax ribs:
Thorax_WS_triple_Angle.png
Thorax_WS_triple_Angle.png (11.27 KiB) Viewed 2966 times

For the abdomen there will be two rib angles with the same name:
Abdomen_WS_double_Angle.png
Abdomen_WS_double_Angle.png (9.06 KiB) Viewed 2966 times

Based on the THOR/T3 channels provided from Crash Designer the intention for the naming seems to be:



original code -> linear
like : 11CHSTLEUPT3ANZP
-> .Transfer function used : Linear regression

03 -> Linear with offset:
like: 11CHSTLE03T3ANZP
-> .Transfer function used : Linear regression with offset

Also here you will get double named channels for the 4 thorax channels!

I guess this is not what is intended by the coding given for the THOR:
The coding for the angle is intended for the linear with offset channel or better to say for the
"absolute angle". There has been no 03 variant (cubic polynom) defined.

It would be helpful if we can disuss this together with Kistler, to avoid the confusion
for the users and implement a change in the generation of these channels.
May this is only a configuration problem at the users?

Kind regards,
Dirk

(@Paul: Am I limited to 3 attachments per message?)
DiVe
Posts: 411
Joined: Tue Apr 24, 2007 9:14 am
Company: IAT mbh
Location: IAT Berlin - Germany
Contact:

Re: Codes in THOR/WS deflection with FL2 = 03

Post by DiVe »

Updated information:

In a recent feedback from Kistler we could clarify that this behavior is already corrected in CrashDesigner since a while:
Since CrashDesigner Version 2.10.0 (December 2019) the following conditions will be used for the generation of a secondary (nonlinear) channel:
• The base Location Code must have „00“ on FL2.
• The skaling of the secondary channel musst use a cubic polynomial calculation. "Linear with offset" is no longer valid for the 03 coding.

Moreover there is an option to define for each physical dimension if a secondary channel is allowed to be generated.

So this topic can be closed.
Locked

Return to “Clarification”