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.

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

Trajectory: Improvements for trajGetMatch function #23

Open
ybeyer opened this issue Jun 16, 2022 · 0 comments
Open

Trajectory: Improvements for trajGetMatch function #23

ybeyer opened this issue Jun 16, 2022 · 0 comments
Assignees

Comments

@ybeyer
Copy link
Contributor

ybeyer commented Jun 16, 2022

Matching should be designed more cleverly in the future. It was actually once thought that with the trajSetMatch the two fields active_section and current_time in the traj struct can be updated and that the next matching takes into account the state of these two fields (or alternatively in Simulink - depending on the structuring - via unit delay feedback of these two variables). In addition, one can of course implement many other improvements.

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

No branches or pull requests

2 participants