Page 1 of 1

EuroNCAP VTC reference data

Posted: Tue Jan 30, 2024 10:47 am
by hummg
Dear colleagues,

I have some questions and comments on the reference data from “TU Graz” to be uploaded to the EuroNCAP VTC Server in the future.
There are potential deviations from ISO 1.x standard in the following areas (for example).

MME file: Descriptor rows to long, max of 28 characters followed by colon (@29), Tab stops, non-defined keys and/or their values, number of test objects, …

Channel files: internal time base information, test object definition, key values, notation of units, min/max values, UTF-8 (error due to upload) …

And maybe an additional topic: how to handle extended velocity attributes for (lat./lon) --> ref. to?
viewtopic.php?t=706

Kind regards
Guido

Re: EuroNCAP VTC reference data

Posted: Tue Sep 17, 2024 3:40 pm
by DiVe
Dear All,

we started the discussion with Corinna Klug and received valuable feedback.
Mrs Klug has provides alternative descriptor names and the topic will be discussed internal at EuroNCAP.

Please find here the state of work as EXCEL-tables:
MME-Files-VTC.xlsx
(13.92 KiB) Downloaded 15 times
ISO_MME_Channels_Frontal_Simulations.xlsx
(24.3 KiB) Downloaded 11 times
Comments and feedback are welcome.

Kind regards,
Dirk

Re: EuroNCAP VTC reference data

Posted: Tue Sep 17, 2024 3:44 pm
by DiVe
Based on the first document I checked the descriptor length in the proposal and send some comments:
2024_07_15_MME-Files-VTC_DiVe.xlsx
(16.22 KiB) Downloaded 12 times
And the comments from the E-Mail:
VTC_Snap1.png
VTC_Snap1.png (47.58 KiB) Viewed 183 times
VTC_Snap2.png
VTC_Snap2.png (84.56 KiB) Viewed 183 times
Kind regards,
Dirk