Skip to content

Support namespacing controller launches - #5

Merged
eholum-nasa merged 2 commits into
jazzy-develfrom
support-namespaces
Apr 21, 2026
Merged

Support namespacing controller launches#5
eholum-nasa merged 2 commits into
jazzy-develfrom
support-namespaces

Conversation

@eholum-nasa

@eholum-nasa eholum-nasa commented Apr 16, 2026

Copy link
Copy Markdown
Member

Might as well support this here since it isn't a huge change.

@ndunkelb-nasa ndunkelb-nasa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, this looks fairly straightforward. I am wondering - should we monorepo this into CLR? I don't really see a good reason for us to maintain this separately. I don't think we will integrate a vention rail in this exact config elsewhere.

constraints:
stopped_velocity_tolerance: 0.2
goal_time: 0.0
vention_rail_base_to_carriage: { trajectory: 0.1, goal: 0.1 }

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
vention_rail_base_to_carriage: { trajectory: 0.1, goal: 0.1 }
$(var tf_prefix)vention_rail_base_to_carriage: { trajectory: 0.1, goal: 0.1 }

Comment thread vention_rail_deploy/config/rail_controllers.yaml

@eholum-nasa eholum-nasa left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am wondering - should we monorepo this into CLR?

The only reason that I hesitate is I think this can be used with not CLR. There are other vention rails in the wild and maybe having this be standalone is more generally helpful?

Comment thread vention_rail_deploy/config/rail_controllers.yaml
@eholum-nasa
eholum-nasa merged commit 9bc7391 into jazzy-devel Apr 21, 2026
1 check passed
@eholum-nasa
eholum-nasa deleted the support-namespaces branch April 21, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants