Hi Elana, you misunderstood my point. What I meant is the following: If shutting off is not safe for a system as it apparently is the case in your example, you simply can not design it with a single c

Hi Elana, not sure what you refer to, but in any case, I think Lukas is right, I also don’t see how the example supports your position. If availlability is safety critical, a system without redundancy

Hi everyone, just a quality of life service for those interested, the recording of the talk can be found here: https://youtu.be/iaK_wcL1ekY?t=12393 Jochen

Hi Everyone, - The last two weeks we worked on - Workshop preparation - Slides - Demo - Brainstorming regarding goal setting next quarter - Code improvements to the cluster demo - Feedback from the Ar

Hi everyone, in preparation of todays workgroup update centered TSC meeting, here a quick overview of our activities since the last update: - Finished meta-elisa repo restructuring - Cluster Demo use

Hi Milan, sorry to answer this late, pre christmas crunch :/ git rev-list --ancestry-path turned out to be not the right tool for the job, since it collects all commits on all potential paths between

Better late than never: For the Automotive WG, our activities last month were: - Implemented telltale demo application, an extension of AGL cluster demo - We have a proper AGL layer now for the demo a

Hi everyone, Kate and I did a bit of brainstorming how to deal with the our repo problem Problem at hand to recapitulate: Currently we have elisa-tech as central hub for ELISA repos, but since github

Hi Lukas, everyone, this looks fun indeed, so I gave it a try yesterday night. Nice challenge, it is shaping up to be a good excample for why stuff is not that simple and streightforward to trace, eve

Hi everyone, in the Automotive workgroup we discussed with Yocto/AGL experts how to add our extensions to the AGL cluster demo. It turns out, the correct Yocto way involves several repositories (at le

Hi Roberto, looks good. Only content issue I have is the Part 11 reference, you probably saw that coming 😉 Some editorial comments inline. Jochen [JK: should be "guaranteeing"] [JK: I think Part 11 sh

Hi Walt, they should end up in the google drive folder: https://drive.google.com/drive/folders/149GogyKS1dZVn4HsiNWVj7tAgoxVWSWr Currently it is still empty though, recordings always take a while to b

Hi Everyone, WITZ made an updated version of the ISO26262 visualization material to include all the verification related things that were not considered the first time around. The updated materials ca

Hi all, below you find the abstract for the Automotive Working Group session in next weeks Workshop Best regards, Jochen -------------- Topic idea: Summary of Automotive Working Group Activities What

Hi all, just a reminder/slight update of the agenda for todays WG call: 1. Tell Tale Safety document review (Jochen) https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%

Hi Oscar, good catch, I’ll look into that, clearly missing at the moment. Jochen Von: devel@... <devel@...> Im Auftrag von Oscar Slotosch Gesendet: Mittwoch, 19. August 2020

Hi Everyone, Our collegues at WITZ created a visualization of the development process according to ISO26262 to help us and especially those without an automotive safety background and access to the st

Hi Lukas, that looks very good to me, I'd definitely take part in that exercise. Not a C programmer, but 10 years of Matlab and familiar with git. Best regards Jochen -----Ursprüngliche Nachricht-----

Hi Everyone, The white papers finally have their own repository! Check it out! ^^ https://github.com/elisa-tech/ELISA-White-Papers.git Sorry this took so long, lots of obstacles. So far there is a tem

Thanks Kate, for the clarification. Should have realized the difference between voting for the date and registration… not fully awake yet it seems ^^ Best regards Jochen Von: Kate Stewart <kstewart@li