ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Safety Critical WG meeting #20190822

I see in my calendar an entry for the next safety critical working group, but I don’t see an announcement here about it. I’m going to assume that we decided the next time in the previous meeting but I forgot to make a topic announcing it. So here is that topic!

The next Safety Critical WG meeting will be held at Thursday, August 22, 2019 2:00 PM.


Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/573563349

You can also dial in using your phone.
United States: +1 (646) 749-3117

Access Code: 573-563-349

More phone numbers
Australia: +61 2 9091 7603
Austria: +43 7 2081 5337
Belgium: +32 28 93 7002
Canada: +1 (647) 497-9373
Denmark: +45 32 72 03 69
Finland: +358 923 17 0556
France: +33 170 950 590
Germany: +49 692 5736 7300
Ireland: +353 15 360 756
Italy: +39 0 230 57 81 80
Netherlands: +31 207 941 375
New Zealand: +64 9 913 2226
Norway: +47 21 93 37 37
Spain: +34 932 75 1230
Sweden: +46 853 527 818
Switzerland: +41 225 4599 60
United Kingdom: +44 20 3713 5011

New to GoToMeeting? Get the app now and be ready when your first meeting starts:
https://global.gotomeeting.com/install/573563349

Attendees

  • Geoffrey Biggs (Tier IV)
  • Denis Stogl
  • Erik Boasson
  • Shawn (Northstar Robotics)
  • Joe Speed
  • Sohin Shah
  • Rajesh Kumar

Minutes Geoffrey Biggs

Previous meeting Safety Critical WG meeting #4

Discussion

  • Proposal: We can produce packages that provide node constructs (patterns) for common patterns used in safety-critical systems such as a 2oo3 architecture.
  • Can we do anything with ISO 13849 for control systems of machinery?
    • It does discuss some software aspects at the system level.
    • The patterns idea could work for this standard as well
  • How can we move forward with the patterns idea?
    • What would our output be?
      • Documents
      • Code
    • Need to collect patterns first
      • Good source: ISO 13849 and IEC 61508
    • Start a Google Doc or something where we can start collecting patterns and describing how to do them in ROS
    • List the resources we have available (useful parts of standards, etc.)
  • Proposal: Produce a library to provide useful functionality for increasing reliability or availability, such as Virtual Synchrony.
  • An interesting alternative angle: How do you integrate ROS (as a non-safety-critical part of a system) with a safety-critical part and provide guarantees of non-interference, etc.?

Action items

  • Start a Google Doc for documenting patterns and available resources
  • Take a poll on the regular meeting time

Here’s the Google Doc for describing patterns:

We decided to have a regular meeting every four weeks. We can make it more frequent if we decide we need more discussion time when activities start building up.

The current proposed time is four weeks from today, so the 26th of September. To give people the chance to find a better time, here’s a doodle poll:

The time chosen by that poll will become the regular meeting time, so don’t choose based solely on the September time slot.