Dear colleagues,
I would like you to clarify the proper use of data status as the use of them could be open to interpretation. The Data Status are shown in the table 2.5
Our interpretation is the explained below:
“channel failed” vs “no data”
- Channel failed: Can only be used if all samples are set to NOVALUE. This status will be set after processing the data. Once the data is analyzed and decided that something went wrong all samples are set to NOVALUE.
- No data: I guess no data is more or less the same than “channel failed” but channel data is empty for “no data” meanwhile for “channel failed” is NOVALUE for every time step
At this point I would like to ask, why would somebody needs a status as “no data”? I can not imagine a situation where we would need this status if we already have “Channel failed” status. Is there any other difference between them that I have not considered? If so, please, would you be so kind to explain it?
“meaningless data” vs “questionable data”
- Meaningless data: This status must be used when some samples (could be all samples as well) in the data channel are meaningless but those wrong samples are not set to NOVALUE. This status will be useful to deliver raw data coming straight from the data acquisition system and informing in the remarks where the data is meaningless. For instance: 10VEHC000000ACXP: meaningless data from 50.0 ms to 350.0 ms
- Questionable data: Must be used the same way than “meaningless data” but the questionable data must be always set to NOVALUE. In this status, the “wrong” data can´t remain in the data channel. This status must be used when data has been processed.
Are the explanations detailed before correct?
To conclude, we would like to know why is the status “system failed” intended for? Looks similar to “no data” but is not clear the situation where this status should be used.
Best regards
Miguel Ángel
Proper use of Data Status codes
Help in understanding TS 13499
-
- Posts: 7
- Joined: Mon Apr 20, 2020 8:24 am
- Company: Applus IDIADA Group
Jump to
- TS 13499 - the current release
- ↳ General (1.6.x)
- ↳ RED A (1.6.x)
- ↳ RED B (1.6.x / 2.x)
- ↳ RED C (1.6.x / 2.x)
- ↳ RED D (1.6.x / 2.x)
- ↳ RED E (1.6.x / 2.x)
- ↳ RED F (1.6.x / 2.x)
- ↳ Database (1.6.x / 2.x)
- ↳ Test Data (1.6.x)
- ↳ General (2.x)
- ↳ RED A (2.x)
- TS 13499 - Suggestions
- ↳ Corrections to existing codes
- ↳ Additional codes
- ↳ Clarification
- ↳ Last TaskForce meeting
- ↳ Next TaskForce meeting
- ↳ MME 2.0 discussion
- ↳ IR-TRACC discussion
- ↳ Movie Codes
- ↳ Naming Rules
- ↳ Vehicle Figures
- ↳ Vehicle surface and structure
- ↳ Restraint systems and seats
- ↳ Impactors
- ↳ Other Figures
- ↳ Dummy Figures
- ↳ Overview
- ↳ Chest Deflection Measurement
- ↳ Euro SID (E1, E2, ER)
- ↳ Hybrid III (H3, HF, HM)
- ↳ SID IIs (S2)
- ↳ Child Dummy Y-series (Y2, Y6, Y7, YA)
- ↳ Child Dummy Q-series (Q0, Q1, Q2, Q3, Q4, Q6, QA)
- ↳ WorldSID (WS)
- ↳ BioRID (BR)
- ↳ THOR (TH, TF, T3)
- ↳ Codes for THOR dummy
- ↳ Codes for WorldSID
- ↳ Codes for ES-2re
- ↳ Codes for Advanced Lower Leg for Hybrid 3 dummies
- ↳ Dummy certification
- ↳ Testtypes, Subtypes and Regulations
- ↳ Active Safety Codes
- ↳ Dummy Positioning
- TS 13499 - Archive
- ↳ Release 1.5
- ↳ General (1.5)
- ↳ RED A (1.5)
- ↳ RED B (1.5)
- ↳ RED C (1.5)
- ↳ RED D (1.5)
- ↳ RED E (1.5)
- ↳ Test Data (1.5)
- ↳ Database (1.5)
- ↳ Release 1.4
- ↳ General (1.4)
- ↳ RED A (1.4)
- ↳ RED B (1.4)
- ↳ RED C (1.4)
- ↳ RED D (1.4)
- ↳ RED E (1.4)
- ↳ Test Data (1.4)
- ↳ Release 1.6
- ↳ General (1.6)
- ↳ RED A (1.6)
- ↳ RED B (1.6)
- ↳ RED C (1.6)
- ↳ RED D (1.6)
- ↳ RED E (1.6)
- ↳ Test Data (1.6)
- ↳ Database (1.6)
- TS 22240 - the current release
- ↳ Vehicle Safety Information Model - VSIM
- ↳ RED A
- ↳ RED B
- ↳ RED C
- ↳ Testdata
- TS 23520 - EQX - EQuipment eXchange
- ↳ Documents and RED (XSD, demo data)