ROS & simulators 7 ROS driver node ROS based visualization tool ROS based data processing publishes: /sensor topic reads: raw sensor's data subscribes: /sensor topic subscribes: /sensor What is missing? 16 Simulation run 1: Camera image: [ Image 1] Detected pedestrians: [Pedestrian A, Pedestrian B] Simulation run 2: Camera image: [Image 1] Detected pedestrians: [Pedestrian A, Pedestrian Pedestrian B] Simulation run 3: Camera image: [Image 1] Detected pedestrians: [Pedestrian A, Pedestrian B] This determinism can allow repeatability and reproducibility of different AV scenarios in testing

Medical Group12 Aurora Innovation What could go wrong? Incorrect interpolation and misrepresenting image positions could result in inaccurate measurements, causing patient harm. Courtesy of Canon Medical v1 Bazel v6.3.2 touca.io/docs/sdk/installing43 Aurora Innovation Data Capturing API touca::workflow("students", [](const std::string& username) { const auto& student = find_student(username); Deeper Dive pejman.dev/talks/cppcon2150 Aurora Innovation Data Submission Low-Level API touca::workflow("students", [](const std::string& username) { const auto& student = find_student(username);

sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()

sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()

sources, that compilation is also done by the client application. The different applications in the image above are: • The Conan client: this is a console/terminal command line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["MyOtherLib"].full_package()

the client application. 3 Conan Documentation, Release 1.29.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.30.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.31.4 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.24.1 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()

the client application. 3 Conan Documentation, Release 1.25.2 The different applications in the image above are: • The Conan client: this is a console/terminal command-line application, containing the previous section, we fetched the sources of our library from an external repository. It is a typical workflow for packaging third party libraries. There are two different ways to fetch the sources from an be built. If we know that changes in the channel never imply a source code change, as set in our workflow/lifecycle, we could write: def package_id(self): self.info.requires["my_other_lib"].full_package()