Skip to content

fix: update GitHub links from tier4 to autowarefoundation #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
atsushi421 merged 1 commit into from
Feb 23, 2026
Merged

fix: update GitHub links from tier4 to autowarefoundation #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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.
Expand Down
4 changes: 2 additions & 2 deletions cie_thread_configurator/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Expand Down Expand Up @@ -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:
Expand Down