From a1fa44a10d8d33257e92a7a933279cc8467a20c9 Mon Sep 17 00:00:00 2001 From: atsushi421 Date: Tue, 24 Feb 2026 06:58:00 +0900 Subject: [PATCH] fix: update GitHub links from tier4 to autowarefoundation --- README.md | 6 +++--- cie_thread_configurator/README.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 6a8b699..a7b0a78 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ This reflects the current status, and support is expected to expand in the futur ## Build and Install ``` -$ git clone https://github.com/tier4/callback_isolated_executor.git +$ git clone https://github.com/autowarefoundation/callback_isolated_executor.git $ cd callback_isolated_executor $ source /opt/ros/humble/setup.bash $ colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release @@ -90,7 +90,7 @@ $ sudo reboot ### Step1: Rewrite your app When running a node within `ComponentContainerCallbackIsolated`, you don't need to modify the node's implementation. However, if starting the node directly from the main function without using ComponentContainer, you need to modify the node's implementation as shown below and rebuild it. -Refer to the source code in the [cie_sample_application](https://github.com/tier4/callback_isolated_executor/tree/main/cie_sample_application) package to understand how to modify your app. +Refer to the source code in the [cie_sample_application](https://github.com/autowarefoundation/callback_isolated_executor/tree/main/cie_sample_application) package to understand how to modify your app. #### Option1: Launch without ComponentContainer If you are launching a node directly from the main function without using a ComponentContainer, change the name of the Executor. @@ -214,7 +214,7 @@ $ vim your_config.yaml ``` For callback groups that do not require configuration, you can either delete the entry entirely or leave it as is because the default values in `template.yaml` are set with default nice values and no affinity settings on the CFS scheduler. -For the detailed specifications of the configuration file, please refer to https://github.com/tier4/callback_isolated_executor/tree/main/cie_thread_configurator#yaml-configuration-file-format. +For the detailed specifications of the configuration file, please refer to https://github.com/autowarefoundation/callback_isolated_executor/tree/main/cie_thread_configurator#yaml-configuration-file-format. ### Step5: Launch your app with scheduler configuration To launch the target ROS 2 application with the scheduler settings applied from the your_config.yaml you created, first start the configurator node with the following command. diff --git a/cie_thread_configurator/README.md b/cie_thread_configurator/README.md index acbbbec..31a499f 100644 --- a/cie_thread_configurator/README.md +++ b/cie_thread_configurator/README.md @@ -1,7 +1,7 @@ # cie_thread_configurator A library that allows you to configure thread scheduling for all callback groups of ROS 2 nodes launched by the `callback_isolated_executor` package using just one YAML file. -For instructions on how to use this tool, please refer to https://github.com/tier4/callback_isolated_executor/tree/main?tab=readme-ov-file#usage. +For instructions on how to use this tool, please refer to https://github.com/autowarefoundation/callback_isolated_executor/tree/main?tab=readme-ov-file#usage. ## YAML Configuration File Format For each ROS 2 application, prepare a single YAML configuration file. @@ -100,7 +100,7 @@ For threads operating on the EDF scheduler, you can specify the parameters named ## CallbackGroup ID format In the YAML template generated by `cie_thread_configurator`, CallbackGroup IDs are automatically generated. -As explained in the [usage instructions](https://github.com/tier4/callback_isolated_executor/tree/main?tab=readme-ov-file#step3-generate-yaml-template-file), the YAML template file looks like this: +As explained in the [usage instructions](https://github.com/autowarefoundation/callback_isolated_executor/tree/main?tab=readme-ov-file#step3-generate-yaml-template-file), the YAML template file looks like this: ```yaml callback_groups: