Skip to content
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

Jump to bottom

Write design documents of high-level software architecture including component interfaces for Bus ODD discussed on GitLab #10

Closed
kenji-miyake opened this issue Dec 21, 2021 · 2 comments
Closed

Write design documents of high-level software architecture including component interfaces for Bus ODD discussed on GitLab #10

kenji-miyake opened this issue Dec 21, 2021 · 2 comments
Labels
status:stale Inactive or outdated issues. (auto-assigned)

Comments

@kenji-miyake
Copy link
Contributor

kenji-miyake commented Dec 21, 2021 •
edited
Loading

It's discussed here.

I believe the discussion result should be organized like this.
(Autoware.Auto doesn't have such high-level documentation, but a bit similar one is this.)

Also regarding the messages, writing rationales like autoware_auto_msgs is nice.
But if possible, I feel a bit more detailed rationales are better.
@kenji-miyake kenji-miyake mentioned this issue Dec 21, 2021
Open
10 tasks
@kenji-miyake kenji-miyake changed the title Write design documents of high-level software architecture including component interfaces for Bus ODD discussed here Write design documents of high-level software architecture including component interfaces for Bus ODD discussed on GitLab Dec 21, 2021
@kenji-miyake kenji-miyake mentioned this issue Dec 21, 2021
Open
kenji-miyake pushed a commit to KeisukeShima/autoware-documentation that referenced this issue Mar 23, 2022
@TakaHoribe
Merge pull request autowarefoundation#10 from tier4/add-node-topic-ar…
f9c8f5e 
…chitecture

docs(node-diagram): add overall node diagram for autoware.universe
@stale
Copy link

stale bot commented Mar 24, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the status:stale Inactive or outdated issues. (auto-assigned) label Mar 24, 2022
@kenji-miyake
Copy link
Contributor Author

kenji-miyake commented Mar 24, 2022 •
edited
Loading

Same as #9 (comment).

I think we can merge this with #9 since a draft version of the documents was added.

TakaHoribe added a commit that referenced this issue Jul 27, 2022
@TakaHoribe
Merge pull request #10 from tier4/add-node-topic-architecture
14e686e 
docs(node-diagram): add overall node diagram for autoware.universe
mitsudome-r added a commit that referenced this issue Jul 27, 2022
@TakaHoribe @mitsudome-r
docs: add overall node diagram for autoware core/universe (#50)
1f222a8 
* Merge pull request #10 from tier4/add-node-topic-architecture

docs(node-diagram): add overall node diagram for autoware.universe

* fix

Signed-off-by: Takamasa Horibe <horibe.takamasa@gmail.com>

* Update docs/design/node-diagram/index.md

Co-authored-by: Ryohsuke Mitsudome <43976834+mitsudome-r@users.noreply.github.com>

* fix precommit

Signed-off-by: Takamasa Horibe <horibe.takamasa@gmail.com>

Co-authored-by: Ryohsuke Mitsudome <43976834+mitsudome-r@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status:stale Inactive or outdated issues. (auto-assigned)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kenji-miyake