Merge pull request #15 from maggyl/main

Adding publications

_data/authors.yml

@@ -21,14 +21,31 @@ Basu:
 Batkovic:
   firstname: ["Ivo", "I.", "I. B.", "Ivo Batkovic"]
   scholar: 7X_8eVEAAAAJ
+Bergenhem:
+  firstname: ["Carl", "C.", "C. B.", "Carl Bergenhem"]
+  org: Qamcom
+  scholar: JN3MbzYAAAAJ
 Bodin:
   firstname: ["Alexander", "A.", "A. B.", "Alexander Bodin"]
   org: Zenseact
   title: Intern
+Brannstrom:
+  firstname: ["Mattias", "M.", "M. B.", "Mattias Brännström"]
+  org: Zenseact AB
+  scholar: rM9mOFAAAAAJ
 Buening:
   firstname: ["Thomas", "T.", "T.B", "Thomas Buening"]
   org: Oslo University
   scholar: 1VT2sBgAAAAJ
+Campos:
+  firstname: ["Gabriel", "G.", "G. C.", "Gabriel Rodrigues de Campos"]
+  org: Zenseact AB
+  url: http://www.gabrieldecampos.com
+  scholar: wK-DQL0AAAAJ
+Chen:
+   firstname: ["DeJiu", "D.", "D. C.", "DeJiu Chen"]
+   org: KTH Royal Institute of Technology
+   scholar: SE9ruMUAAAAJ
 Dimitrakakis:
   firstname: ["Christos", "C.", "C. D.", "Christos Dimitrakakis"]
   scholar: 9Kw4t_kAAAAJ
@@ -48,6 +65,9 @@ Fatemi:
   org: Zenseact
   scholar: GpcBXmoAAAAJ
   title: Researcher
+Feilbinger:
+  firstname: ["Hermann", "H.", "H. F.", "Hermann Feilbinger"]
+  org: AVL List
 Felsberg:
   firstname: ["Michael", "M.", "M. F.", "Michael Felsberg"]
   org: Linköping University
@@ -63,12 +83,25 @@ Fu:
   scholar: z3lud1UAAAAJ
   title: Researcher
   url: https://junshengfu.github.io
+Gaspar:
+  firstname: ["José Manuel Gaspar", "JMG.", "JMG. S.", "José Manuel Gaspar Sanchez"]
+  org: KTH Royal Institute of Technology
+  scholar: EEGDis0AAAAJ
 Gronberg:
   firstname: ["Robin", "R.", "R. G.", "Robin Grönberg"]
 Grover:
   firstname: ["Divya", "D.", "D.G.", "Divya Grover"]
   org: Chalmers University
   scholar: gxlPOTcAAAAJ
+Gyllenhammar:
+  firstname: ["Magnus", "M.", "M. G.", "Magnus Gyllenhammar"]
+  org: [Zenseact, KTH Royal Institute of Technology]
+  github: maggyl
+  linkedin: maggyl
+  picture: /assets/images/profiles/maggyl.jpg
+  title: PhD Student
+  url: https://maggyl.github.io
+  scholar: 2NAVPBMAAAAJ
 Hagerman:
   firstname: ["David", "D.", "D. H.", "David Hagerman"]
   org: Chalmers University of Technology
@@ -88,6 +121,10 @@ Hess:
   scholar: ZvUoV2EAAAAJ
   title: PhD Student
   url: https://georghess.github.io/
+Heyn:
+   firstname: ["Hans-Martin", "H.", "H. H.", "Hans-Martin Heyn"]
+   org: Volvo Technology AB
+   scholar: Pd5pmvQAAAAJ
 Hoel:
   firstname: ["Carl-Johan", "C.", "C. H.", "Carl-Johan Hoel"]
   scholar: f7ewwIsAAAAJ
@@ -97,6 +134,14 @@ Jaxing:
   firstname: ["Johan", "J.", "J. X.", "Johan Jaxing"]
   org: Zenseact
   title: Intern
+Jianbotao:
+  firstname: ["Jianbo", "J.", "J. T.", "Jianbo Tao"]
+  org: AVL List
+  scholar: UKUtWucAAAAJ
+Johansson:
+  firstname: ["Rolf", "R.", "R. J.", "Rolf Johansson"]
+  org: Astus AB
+  scholar: qceJ6hwAAAAJ
 Johnander:
   firstname: ["Joakim", "J.", "J. J.", "Joakim Johnander"]
   mail: [email protected]
@@ -152,9 +197,16 @@ Meding:
 Mohajerani:
   firstname: ["Sahar", "S.", "S. M.", "Sahar Mohajerani"]
   org: Mathworks
+Mohan:
+  firstname: ["Naveen", "N.", "N. M.", "Naveen Mohan"]
+  org: KTH Royal Institute of Technology
+  scholar: bSJ8lQoAAAAJ
 Motorniuk:
   firstname: ["Daria", "D.", "D. M.", "Daria Motorniuk"]
   org: Zenseact
+Nica:
+  firstname: ["Mihai", "M.", "M. N.", "Mihai Nica"]
+  org: AVL List
 Petersson:
   firstname: ["Christoffer", "C.", "C. P.", "Christoffer Petersson"]
   mail: [email protected]
@@ -168,9 +220,25 @@ Rafidashti:
   mail: [email protected]
   org: [Zenseact, Chalmers University of Technology]
   title: PhD Student
+Rusyadi:
+  firstname: ["Muhammad Rusyadi", "MR.", "MR. R.", "Muhammad Rusyadi Ramli"]
+  org: KTH Royal Institute of Technology
+  scholar: 6toSX0YAAAAJ
+Sandblom:
+  firstname: ["Fredrik", "F.", "F. S.", "Fredrik Sandblom"]
+  org: Zenseact AB
+Sanfridson:
+  firstname: ["Martin", "M.", "M. S.", "Martin Sanfridson"]
+  org: Volvo Technology AB
+Sivencrona:
+  firstname: ["Håkan", "H.", "H. S.", "Håkan Sivencrona"]
+  org: Zenseact AB
 Sjoberg:
   firstname: ["Jonas", "J.", "J. S.", "Jonas Sjöberg"]
   scholar: s0Qakg77XTYC
+Skoglund:
+  firstname: ["Martin", "M.", "M. S.", "Martin Skoglund"]
+  org: RISE Research Institutes of Sweden
 Stenborg:
   firstname: ["Erik", "E.", "E. S.", "Erik Stenborg"]
   mail: [email protected]
@@ -182,6 +250,18 @@ Svensson:
   org: Chalmers University of Technology
   scholar: AMM9vE4AAAAJ
   title: Professor
+Soderberg:
+   firstname: ["Jan", "J.", "J. S.", "Jan Söderberg"]
+   org: Systemite AB
+   url: https://www.researchgate.net/profile/Jan-Soderberg
+Tan:
+  firstname: ["Kaige", "K.", "K. T.", "Jianbo Tan"]
+  org: KTH Royal Institute of Technology
+  scholar: qA2Xb_MAAAAJ
+Thorsen:
+  firstname: ["Anders", "A.", "A. T.", "Anders Thorsén"]
+  org: RISE Research Institutes of Sweden
+  url: https://www.ri.se/sv/person/anders-thorsen
 Tonderski:
   firstname: ["Adam", "A.", "A. T.", "Adam Tonderski"]
   github: atonderski
@@ -197,9 +277,38 @@ Tram:
   org: Zenseact
   scholar: m_O_xjIAAAAJ
   title: null
+Torngren:
+  firstname: ["Martin", "M.", "M. T.", "Martin Törngren"]
+  org: KTH Royal Institute of Technology
+  url: https://www.kth.se/profile/martint
+  scholar: -F-KArEAAAAJ
+Ursing:
+  firstname: ["Stig", "S.", "S. U.", "Stig Ursing"]
+  org: Semcon Sweden AB
+  url: https://www.researchgate.net/profile/Stig-Ursing
+Warg:
+  firstname: ["Fredrik", "F.", "F. W.", "Fredrik Warg"]
+  org: RISE Research Institutes of Sweden
+  url: https://warg.org
+  scholar: H4hiOCMAAAAJ
 Widahl:
   firstname: ["Jenny", "J.", "J.W.", "Jenny Widahl"]
   org: Zenseact
+Wotawa:
+  firstname: ["Franz", "F.", "F. W.", "Franz Wotawa"]
+  org: Graz University of Technology
+  scholar: Z27gH2wAAAAJ
+Xintao:
+  firstname: ["Xin", "X.", "X. T.", "Xin Tao"]
+  org: KTH Royal Institute of Technology
+  scholar: h405hiwAAAAJ
+Xinhai:
+  firstname: ["Xinhai", "X.", "X. Z.", "Xinhai Zhang"]
+  org: KTH Royal Institute of Technology
+  scholar: hANonS0AAAAJ
+Zanden:
+  firstname: ["Carl", "C.", "C. Z.", "Carl Zandén"]
+  org: Zenuity AB
 Carlsson:
   firstname: ["Oscar", "O.", "O.C.", "Oscar Carlsson"]
   org: Chalmers University of Technology

_data/venues.yml

@@ -44,3 +44,20 @@ ITSC18:
 UAI2022:
   name: The 38th Conference on Uncertainty in Artificial Intelligence (UAI), 2022
   url: https://www.auai.org/uai2022/
+IV22:
+  name: 33rd IEEE Intelligent Vehicles Symposium
+  url: https://iv2022.com
+CARS21:
+  name: CARS 2021 - 6th International Workshop on Critical Automotive Applications - Robustness and Safety
+  url: http://cars2021.astus.se
+ERTS20:
+  name: 10th European Congress on Embedded Real Time Systems, 2020
+  url: https://www.erts2020.org
+SAEWCX20:
+  name: SAE World Congress Experience 2020
+  url: https://www.sae.org/attend/wcx/2020
+TSE:
+  name: IEEE Transactions on Software Engineering
+  url: https://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=32
+DSNW20:
+  name: 50th Annual IEEE/IFIP International Conference on Dependable Systems and Networks Workshops (DSN-W)

_publications/ad-safety-assurance-survey/2021-09-13-sota.md

@@ -0,0 +1,27 @@
+---
+title: "ADS Safety Assurance – Future Directions"
+layout: publication
+permalink: /publications/ad-safety-assurance-survey/
+date: 2021-09-13
+venue: CARS21
+extras: oral presentation
+authors:
+  - Gyllenhammar
+  - Bergenhem
+  - Warg
+thumbnail-img: sota.jpg
+arxiv: https://www.diva-portal.org/smash/get/diva2:1625417/FULLTEXT01.pdf
+---
+
+# Abstract
+More effective, efficient and flexible ways to manage safety assurance are needed for the successful development and release of Automated Driving Systems (ADSs). In this paper we propose a set of desired assurance method criteria and present an initial overview of available safety assurance methods and how they contribute to the proposed criteria. We observe that there is a significant gap between the state-of-the-art research and the state-of-practise for safety assurance of ADSs and propose to investigate reasons for this as future work. A next step will be to investigate how to merge the elements from the different assurance methods to achieve a method addressing all criteria.
+
+# BibTeX
+```bibtex
+@inproceedings{gyllenhammar2021sota,
+  title        = {ADS Safety Assurance--Future Directions},
+  author       = {Gyllenhammar, Magnus and Bergenhem, Carl and Warg, Fredrik},
+  booktitle    = {Int. Workshop on Critical Automotive Applications: Robustness \& Safety (CARS)},
+  year         = {2021}
+}
+```

_publications/critical-scenario-identification/2022-04-26-csi.md

@@ -0,0 +1,39 @@
+---
+title: "Finding critical scenarios for automated driving systems-A systematic mapping study"
+layout: publication
+permalink: /publications/critical-scenario-identification/
+date: 2022-04-26
+venue: TSE
+authors:
+  - Xinhai
+  - Jianbotao
+  - Tan
+  - Torngren
+  - Gaspar
+  - Rusyadi
+  - Xintao
+  - Gyllenhammar
+  - Wotawa
+  - Mohan
+  - Nica
+  - Feilbinger
+thumbnail-img: csi.jpg
+arxiv: https://www.diva-portal.org/smash/get/diva2:1659895/FULLTEXT01.pdf
+---
+
+# Abstract
+Scenario-based approaches have been receiving a huge amount of attention in research and engineering of automated driving systems. Due to the complexity and uncertainty of the driving environment, and the complexity of the driving task itself, the number of possible driving scenarios that an Automated Driving System or Advanced Driving-Assistance System may encounter is virtually infinite. Therefore it is essential to be able to reason about the identification of scenarios and in particular critical ones that may impose unacceptable risk if not considered. Critical scenarios are particularly important to support design, verification and validation efforts, and as a basis for a safety case. In this paper, we present the results of a systematic mapping study in the context of autonomous driving. The main contributions are: (i) introducing a comprehensive taxonomy for critical scenario identification methods; (ii) giving an overview of the state-of-the-art research based on the taxonomy encompassing 86 papers between 2017 and 2020; and (iii) identifying open issues and directions for further research. The provided taxonomy comprises three main perspectives encompassing the problem definition (the why), the solution (the methods to derive scenarios), and the assessment of the established scenarios. In addition, we discuss open research issues considering the perspectives of coverage, practicability, and scenario space explosion.
+
+# BibTeX
+```bibtex
+@ARTICLE{zhang2022csireview,
+  author  = {Zhang, Xinhai and Tao, Jianbo and Tan, Kaige and Törngren, Martin and Sánchez, José Manuel Gaspar and Ramli, Muhammad Rusyadi and Tao, Xin and Gyllenhammar, Magnus and Wotawa, Franz and Mohan, Naveen and Nica, Mihai and Felbinger, Hermann},
+  journal = {IEEE Transactions on Software Engineering},
+  title   = {Finding Critical Scenarios for Automated Driving Systems: A Systematic Mapping Study},
+  year    = {2023},
+  volume  = {49},
+  number  = {3},
+  pages   = {991-1026},
+  doi     = {10.1109/TSE.2022.3170122}
+  }
+```

_publications/fundamental-actions-for-ad/2020-04-14-actions.md

@@ -0,0 +1,27 @@
+---
+title: "Defining Fundamental Vehicle Actions for the Development of Automated Driving Systems"
+layout: publication
+permalink: /publications/fundamental-actions-for-ad/
+date: 2020-04-14
+venue: SAEWCX20
+authors:
+  - Gyllenhammar
+  - Zanden
+  - Torngren
+thumbnail-img: actions.jpg
+arxiv: https://www.diva-portal.org/smash/get/diva2:1454057/FULLTEXT01.pdf
+---
+
+# Abstract
+Automated Driving Systems (ADSs) show great potential to improve our transport systems. Safety validation, before market launch, is challenging due to the large number of miles required to gather enough evidence for a proven in use argumentation. Hence there is ongoing research to find more effective ways of verifying and validating the safety of ADSs. It is crucial both for the design as well as the validation to have a good understanding of the environment of the ADS. A natural way of characterizing the external conditions is by modelling and analysing data from real traffic. Towards this end, we present a framework with the primary ultimate objective to completely model and quantify the statistically relevant actions that other vehicles conduct on motorways. Two categories of fundamental actions are identified by recognising that a vehicle can only move longitudinally and laterally. The fundamental actions are defined in detail to create a set that is collectively exhaustive and mutually exclusive. All physically possible combinatorial actions that can be constructed from the fundamental actions are presented. To increase the granularity of the modelling the combinatorial actions are proposed to be analysed as sequences. Further, multi-vehicle interactions, which capture correlations between actions from multiple vehicles, are discussed. The resulting modularity of the framework allows for performing statistical analysis at an arbitrary granularity to support the design of a performant ADS as well as creating applicable validation scenarios. The use of the framework is demonstrated by automatically identifying fundamental actions in field data. Identified trajectories of two types of actions are visualised and the distributions for one parameter characterising each action type are estimated.
+
+# BibTeX
+```bibtex
+@inproceedings{gyllenhammar2020defining,
+  title        = {Defining Fundamental Vehicle Actions for the Development of Automated Driving Systems},
+  author       = {Gyllenhammar, Magnus and Zand{\'e}n, Carl and T{\"o}rngren, Martin},
+  booktitle    = {World Congress (WCX)},
+  year         = {2020},
+  organization = {SAE}
+}
+```

_publications/minimal-risk-condition/2021-09-13-mrc.md

@@ -0,0 +1,30 @@
+---
+title: "Minimal risk condition for safety assurance of automated driving systems"
+layout: publication
+permalink: /publications/minimal-risk-condition/
+date: 2021-09-13
+venue: CARS21
+extras: oral presentation
+authors:
+  - Gyllenhammar
+  - Brannstrom
+  - Johansson
+  - Sandblom
+  - Ursing
+  - Warg
+thumbnail-img: mrc.jpg
+arxiv: https://www.diva-portal.org/smash/get/diva2:1593404/FULLTEXT01.pdf
+---
+
+# Abstract
+We have yet to see wide deployment of automated driving systems (ADSs) on public roads. One of the reasons is the challenge of ensuring the systems’ safety. The operational design domain (ODD) can be used to confine the scope of the ADS and subsequently also its safety case. For this to be valid the ADS needs to have strategies to remain in the ODD throughout its operations. In this paper we discuss the role of the minimal risk condition (MRC) as a means to ensure this. Further, we elaborate on the need for hierarchies of MRCs to cope with diverse system degradations during operations.
+
+# BibTeX
+```bibtex
+@inproceedings{ gyllenhammar2021mrc,
+  title         = {Minimal Risk Condition for Safety Assurance of Automated Driving Systems},
+  author        = {Gyllenhammar, Magnus and Br{\"a}nnstr{\"o}m, Mattias and Johansson, Rolf and Sandblom, Fredrik and Ursing, Stig and Warg, Fredrik},
+  booktitle     = {Int. Workshop on Critical Automotive Applications: Robustness \& Safety (CARS)},
+  year          = {2021}
+}
+```

_publications/operational-design-domain/2020-01-20-odd.md

@@ -0,0 +1,32 @@
+---
+title: "Towards an Operational Design Domain That Supports the Safety Argumentation of an Automated Driving System"
+layout: publication
+permalink: /publications/operational-design-domain/
+date: 2020-01-20
+venue: ERTS20
+authors:
+  - Gyllenhammar
+  - Johansson
+  - Warg
+  - Chen
+  - Heyn
+  - Sanfridson
+  - Soderberg
+  - Thorsen
+  - Ursing  
+thumbnail-img: odd.jpg
+arxiv: https://www.diva-portal.org/smash/get/diva2:1390550/FULLTEXT01.pdf
+---
+
+# Abstract
+One of the biggest challenges for self-driving road vehicles is how to argue that their safety cases are complete. The operational design domain (ODD) of the automated driving system (ADS) can be used to restrict where the ADS is valid and thus confine the scope of the safety case as well as the verification. To complete the safety case there is a need to ensure that the ADS will not exit its ODD. We present four generic strategies to ensure this. Use cases (UCs) provide a convenient way providing such a strategy for a collection of operating conditions (OCs) and further ensures that the ODD allows for operation within the real world. A framework to categorise the OCs of a UC is presented and it is suggested that the ODD is written with this structure in mind to facilitate mapping towards potential UCs. The ODD defines the functional boundary of the system and modelling it with this structure makes it modular and generalisable across different potential UCs. Further, using the ODD to connect the ADS to the UC enables the continuous delivery of the ADS feature. Two examples of dimensions of the ODD are given and a strategy to avoid an ODD exit is proposed in the respective case.
+
+# BibTeX
+```bibtex
+@inproceedings{gyllenhammar2020towards,
+  title     = {Towards an operational design domain that supports the safety argumentation of an automated driving system},
+  author    = {Gyllenhammar, Magnus and Johansson, Rolf and Warg, Fredrik and Chen, DeJiu and Heyn, Hans-Martin and Sanfridson, Martin and S{\"o}derberg, Jan and Thors{\'e}n, Anders and Ursing, Stig},
+  booktitle = {European Congress on Embedded Real Time Systems},
+  year      = {2020}
+}
+```