ccs@lists.genivi.org

Mailing list for the Cloud & Connected Services project (https://at.projects.genivi.org/wiki/x/PIAVAg)

View all threads

CCS W3C client LiveSim

SL
Stephen Lawrence
Mon, Oct 18, 2021 5:00 PM

Hi,

Following on from the discussion in today's CCS call, why does the W3C client LiveSim write directly into the WAII (VISS) server state storage as shown in the new readme diagram[1]?

I could see it doing that if there was a requirement for the LiveSim to provide data for the VISS server as two stand alone components (just LiveSim and VISS in light weight use), but both the W3C client and LiveSim Readmes[2] say LiveSim reads data from the OVDS component. I wonder why in that case you would create a unique processing path rather than have LiveSim seed the correct simulation data into OVDS and have WAII read it through the normal processing path? What feature dictates the unique LiveSim to WAITT state storage path?

[1] https://github.com/GENIVI/ccs-w3c-client/blob/master/README.md
[2] https://github.com/GENIVI/ccs-w3c-client#live-simulator

Regards

Steve

Hi, Following on from the discussion in today's CCS call, why does the W3C client LiveSim write directly into the WAII (VISS) server state storage as shown in the new readme diagram[1]? I could see it doing that if there was a requirement for the LiveSim to provide data for the VISS server as two stand alone components (just LiveSim and VISS in light weight use), but both the W3C client and LiveSim Readmes[2] say LiveSim reads data from the OVDS component. I wonder why in that case you would create a unique processing path rather than have LiveSim seed the correct simulation data into OVDS and have WAII read it through the normal processing path? What feature dictates the unique LiveSim to WAITT state storage path? [1] https://github.com/GENIVI/ccs-w3c-client/blob/master/README.md [2] https://github.com/GENIVI/ccs-w3c-client#live-simulator Regards Steve
SL
Stephen Lawrence
Mon, Oct 18, 2021 7:32 PM

Ulf/Gunnar,

OK reading the readme further I can see I was working on incorrect assumptions with the overloaded OVDS instances in the diagram.

Regards

Steve

-----Original Message-----
From: Stephen Lawrence
Sent: 18 October 2021 18:01
To: ccs@lists.genivi.org
Subject: CCS W3C client LiveSim

Hi,

Following on from the discussion in today's CCS call, why does the W3C client LiveSim
write directly into the WAII (VISS) server state storage as shown in the new readme
diagram[1]?

I could see it doing that if there was a requirement for the LiveSim to provide data
for the VISS server as two stand alone components (just LiveSim and VISS in light
weight use), but both the W3C client and LiveSim Readmes[2] say LiveSim reads data
from the OVDS component. I wonder why in that case you would create a unique
processing path rather than have LiveSim seed the correct simulation data into OVDS
and have WAII read it through the normal processing path? What feature dictates the
unique LiveSim to WAITT state storage path?

[1] https://github.com/GENIVI/ccs-w3c-client/blob/master/README.md
[2] https://github.com/GENIVI/ccs-w3c-client#live-simulator

Regards

Steve

Ulf/Gunnar, OK reading the readme further I can see I was working on incorrect assumptions with the overloaded OVDS instances in the diagram. Regards Steve > -----Original Message----- > From: Stephen Lawrence > Sent: 18 October 2021 18:01 > To: ccs@lists.genivi.org > Subject: CCS W3C client LiveSim > > Hi, > > Following on from the discussion in today's CCS call, why does the W3C client LiveSim > write directly into the WAII (VISS) server state storage as shown in the new readme > diagram[1]? > > I could see it doing that if there was a requirement for the LiveSim to provide data > for the VISS server as two stand alone components (just LiveSim and VISS in light > weight use), but both the W3C client and LiveSim Readmes[2] say LiveSim reads data > from the OVDS component. I wonder why in that case you would create a unique > processing path rather than have LiveSim seed the correct simulation data into OVDS > and have WAII read it through the normal processing path? What feature dictates the > unique LiveSim to WAITT state storage path? > > [1] https://github.com/GENIVI/ccs-w3c-client/blob/master/README.md > [2] https://github.com/GENIVI/ccs-w3c-client#live-simulator > > Regards > > Steve