...
- Agenda discussion - anything that needs to be added?
- Prioritized Topics:
- Decision on old open PRs
- Open Pull Requests VSS
- Open Pull Requests VSS-Tools
- Issues VSS
- Issues VSS-Tools
- Discussions VSS
- Discussions VSS-tools
- Prioritized topics for next meeting
Meeting notes 2024-
...
08-
...
20
APIgear Intro will be NEXT meeting (27th)
VSS-Tools
- merged core rework: Let's see what the fallout is, if any VSS vs. VSS-tools compatibility
- Shall VSS-tools vX.y be required to support anything else than VSS X.Y?
https://github.com/COVESA/vss-tools/pull/382
VSS
- Do we still need the submodule:vehicle_signal_specification/issues/734https://github.com/COVESA/vehicle_signal_specification/discussionsissues/732Overlay and removeShall new keyword "state" be considered to be part of "std VSS syntax", i.e. described in VSS docAlternative is to consider it just as a VSS-tools-specific feature767
Meeting notes 2024-08-13
VSS-spec
- PR 755, approved by Sebastian and merged.
- PR 761, merged.
VSS-Tools
- PR 391,
- looks good, comments are being addressed
- waiting for SebastianS approval
- https://github.com/COVESA/vss-tools/pull/382
Slack link has to be updated every 3 months.
https://join.slack.com/t/covesacommunity/shared_invite/zt-2mqg9h79y-GCer3TsNgSddodjcM3qh9w
Notes: Next meeting topic "APIGear Introduction". 15-20min
Meeting notes 2024-08-06
- Availability of maintainers for meetings August
- Erik on vacation rest of August
- Is some other maintainer (Adnan Bekan , Sebastian Schildt ) possibly available, or do we need to cancel? (13,20,27)
- Sebastian: Could do 20th and 27th
- Adnan: I can cover 13th, can discuss the other two
- VSS/AMM Workshop
- Paul will work with proposed agenda
Meeting notes 2024-07-30
Meeting notes 2024-07-23
Meeting notes 2024-07-16
- Slack
- Paul: Proposals to AMM wanted, contact Paul if you have questions
- VSS PRs and issues
- VSS-tools PRs and issues
Meeting notes 2024-07-09
- VSS PRs and issues
- VSS-tools PRs and issues
- Stefan (Allianz), open topics, suggestions for VSS.
- Move to the next meeting. Time required 10-15min.
- Stefan will try to upload and share signal list for the discussion.
- Niki, Static UID topic.
- To be reviewed and checked if feature would be useful.
- Issue: 749,
- Daniel, create an example. How this should be documented in vspec.
- Issue: 753
- MoM: Daniel will create PR, let's give it a try with struct.
- PR vss-tools 373
- MoM: Let's have a look.. We need time to review this.
- PR vss-tools 375
- Sebastian will refactor for the next meeting.
Meeting notes 2024-07-02
- Paul: Want to get proposals for technical presentation by end of July, finished by end Mid August
- Erik on business trip next week (Adnan back?)
Meeting notes 2024-06-25
- API Standardization charter - > Listen in to the CVII meeting after the VSS meeting if you like
- VSS-tools PRs
- VSS PRS
- VSS Issue (Daniel Alvarez)
Meeting notes 2024-06-18
Agenda 2024-06-11
- Actuators - https://github.com/COVESA/vehicle_signal_specification/issues/744
- Daniel: Is anyone interested in following up the onthology work presentred by BMW/Ford
- I am gonna work on that anyway, so contact me if you have interest.
- Paul: Interested in following it.
- Daniel: Not yet ready for new project
Agenda 2024-06-04
- AMM Info
- Novi, Detroit-area, USA
- 25-26 Sept, on 24th opportunity to have technical F2F sessions, related to VSS or other
- Paul: Good to take the opportunity F2F
- Erik: We need to start thinking on possible topics, especially for the 24th, also for 25-26th
- VSS Release Status - VSS 4.2 released - https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.2
- OK to remove pre-release tag
- Presentation - Sending VSS data with Protobuf
- By Kaan Bulut, Student at Techn Univ Munich, Thesis done in collab with BMW
- Multiple options
- Generate messages for all leafs (flat)
- Generate all message as key (key-value pair)
- vpec2protobuf -hierarchy of messages
- Compaibility - backward/forward/full
Image Added
Image Added
Meeting notes 2024-05-28
- PRs VSS-Tools
- Events in VSS - https://github.com/COVESA/vehicle_signal_specification/issues/273#
- Reopened
- AP: Adnan to present possible solutions/work-arounds
Meeting notes 2024-05-21
- Future of VSSo (Paul)
- There has been proposals on modeling fron Ford and BMW
- Paul is happy to help if someone wants to drive it forward
- Gunnar: The proposal from Swen - adding info on source of data items, has been discussed, adding metadata or ontology
- Gunnar: Found some drafts on layers, we should put them somewhere
VSS Layers was discussed in Cloud & Connected Services project, end of 2019 and beginning of 2020.
The VSS Layers draft was attached to the page.
Direct link: https://wiki.covesa.global/download/attachments/12124613/VSS%20composable%20layers%20-%20draft%2020200114.pdf?api=v2
Minutes from CCS are here, but there is a lot…
https://wiki.covesa.global/pages/viewpage.action?pageId=12124613
- Protobuf Thesis worker? (Adnan)
- VSS 4.2
- Japanese OEM APIs
Meeting notes 2024-05-14
- VSS Release 4.2
- "GraphQL as VSS Language"-info
- Adnan: The presentation from Swen Schisler could be good as a COVESA blog post
- Paul: To check
- References
Image Added
Meeting notes 2024-05-07
- Sivashankar Yoganathan- 10min presentations, 10 min talk. cca 07.5.2024
- Michael O´Shea presented MOTER
Image Added- With access to more data we can build better risk models
- Example: G value during braking, Tailgating (distance to vehicle in front of ego vehicle)
Image Added
- VSS 4.2 Release Planning
- PP: OBD
- PP: Seats instances
- Paul: VSSo topics: Handle here or not?
- "GraphQL as VSS Language"
Image Added
Meeting notes 2024-04-30
- VSS Release Planning
- Pierre Pierre: Blackberry interested in picking up 4.1 - found some inconsistencies
- Wiki out of date
- Version Info outdated at
- Add info on where to find release
- Changelog- better to have latest version at top, not at bottom
- AP: Erik to check on wiki write access
- Release plan, wait with 5.0 until fall AMM, possibly 4.2 with backward compatible changes including node removal
- PP Ok to use 4.1 for now, but deletion feature is interest, if available in with next 3 weeks then fine.
- Any remaining open PRs to include (must have)?
- AP: Erik to start cherry-picking to 4.X-branch, follow up on results.
Meeting notes 2024-04-23
VSS-Tools PRs
- 343 to be merged
Python active support until 2026 - 344 has to be checked and reviewed
- 346 to review and merged
- 347 to be checked by Erik, how to automate version
VSS-Tools Issues
Close issue 194 it is merged now.
Vspec PRs
- 731 stays open
- PierPierB
- Comments are documenting summary of the discussion.
- euro ncap is quite interesting document and it would be great to use this as base for the alignment of this topic.
- Stefan will check as well with Allianz - 737
- Resolution might be limited(Stefan)
- What about orientation of screen?
- What is the main usage and do we have any usecases? Are we missing anything on top. - 659
- Ppb new comment reference to euro cap
Issue VSpec
- 735 related to issue spec to franca
We had new visitors.
Sivashankar Yoganathan
AB: Do you have myb some use cases or requirements to share?
SY: We could do exchange and understand requirements.
SY: what is missing is frequency of the signals, but we can discuss more details
SY: possible exchange in two weeks,
AB: slot in the meeting for 15-20 min. 10min presentations, 10 min talk. cca 07.5.2024
StefanS: Would be great to have this discussion
New people from MOTER that joined us
Mohair Yadav from Ford as well.
ViSS status.
Ulf and Peter
- Ulf: ViSS is stabilised in covesa repo and everyone can use it
- Peter: demo went well as well on the side of Volvo
Meeting notes 2024-04-18 (April 2024 AMM Working Session on Raw vs. Derived signals):
- The definition of derived signals is not as straightforward as the definition of raw signals
- Distraction levels of 0% and 100% are clear but what does 66% or 34.5% distracted really mean?
- Should distraction really be represented as a percentage? Or, perhaps an enum?
- Units are one way in which clarity can be achieved
- Requires introspection (ability to ask the model) support in the API or equivalent
- Even if enums are used to "bucketize" or categorize the values, interpretation of what each bucket means is still important or not necessarily clear
- For example, what is a crash and severity of crash can have different interpretations depending on culture, context, etc.
- Same for aggressiveness
- How could we make available information on how a signal is derived?
- Where it may be needed or useful
- How can this be expressed to the user?
- Does it need to be digital?
- Margins of error and calculations may vary in time
- Remaining distance based on fuel consumption varies over time
- Some signals from which a derived signal is generate may become unavailable or become available again
- The rate of incoming signals may affect the derivation
- How do we plan to repesent this?
- Even an OEM may not know how some signals are derived
- The Tier-1 may have their own way of doing the derivation and this is not available to the OEM
- What is a raw signal?
- Is there such a beast?
- Clearly there are some, but perhaps the great majority of signals are derived?
- Would adding all the information discussed above impact simplicity?
- One main goal of VSS is simplicity
- Perhaps less precise definitions of signal values is actually simpler
- Should we define the set of parameters to evaluate in order to decide if a derived signal should be added to the signal catalog?
- Is portability of applications (where they can rely on a "standard" definition of a signal) a concern?
- And therefore should the signal catalog only contain clearly defined signals as opposed to leaving definition to interpretation?
- Options to consider:
- Determine if the signal should be made part of the catalog or left for manufacturers to add using overlays
- Require that signal definitions refer to a standard
- Allow liberal interpretation, but mention in signal definition comments that interpretation is left to the implementation
Meeting notes 2024-04-09:
- Crash detection/events - car immobilized
- Stefan: Do we have anything?
- Adnan: PRs welcome
- Erik: Sometimes we create a temporary *.md file and add it to PR for discussion.. PPB to put down initial thoughts in *.md
- AMM
- No regular VSS meeting next week
- Erik has asked Paul to delete
- VSS Deep Dive being prepared by Sebastian Schildt
- Head& Eye
- VSS-tools
Meeting notes 2024-04-02:
- Head& Eye
- Node removal - status update
- https://github.com/nwesem/vss-tools/pull/2
- Adnan: Soon official PR will created. Name of tag changed
- Adnan: Could be presented at AMM
- Erik: Agenda is quite full
- Adnan: We can mention as part of coming releases
- Erik: Could be good mentioning, as well as upcoming VSS 5.0
- DDSIDL and structs
- Pre-commit hooks
- -ot naming conflict
- AMM
- Releases
- Paul: what is the release plan
- erik: Current plan is 5.0 after node removal merge, around AMM, possibly release 4.2 as well at that time
Meeting notes 2024-03-25:
- Head& Eye
- Franca support
- "Inactive" PRs
- Do we want to close them after a certain time of inactivity, if no-one seems to be interested in driving them forward?
- MoM
- PPB: Have no issue closing if there are no progress. Close things at least not touched in a year
- Stefan: discuss in session, archive or take up
- Ulf: A year
- PPB: But not automatic, check last two
- Adnan: Do it AMM, try to schedule time
- AMM
Meeting notes 2024-03-18:
- AOSP
- VSS vs. VSS-tools compatibility
- Overlay and remove
- Shall new keyword "state" be considered to be part of "std VSS syntax", i.e. described in VSS doc
- Alternative is to consider it just as a VSS-tools-specific feature
- https://github.com/nwesem/vss-tools/pulls
- Adnan: Does not really understand the use of active/inactive
- Daniel: Is it intended only for exporter, or also other function
- Adnan: Inactive/active fills a different purpose, not needed for vss-tools for purpose of removing signals of tree
- Terminology:
- AMM
Topics for discussion:
- Raw vs. derived signals; does VSS need to define or state how signals are derived?
- Is this useful to clients?
- For signals derived through ML; should confidence level, variance, precision, error, etc. be reported?
- Is this useful to clients?
- How should model-generated derived signals such as "driver attentiveness" be represented (in the absence of a standard)?
- Confidence percentage? Enum?
- To what level of specificity should VSS describe signals?
- Leave semantics to OEMs (flexibility for OEMs but affects portability) or define them precisely?
nwesem/vss-tools/pulls
Meeting notes 2024-03-12:
...