Skip to content

Understanding the Internals of MotoROS2 Trajectory Validation #332

Answered by lkaising
lkaising asked this question in Q&A
Discussion options

You must be logged in to vote

Yes, I managed to resolve the issue by implementing additional validation checks in my task execution pipeline. While I didn't identify the exact source of the problem (whether MTC or my implementation), adding pre-execution validation has effectively prevented the single-point trajectory issues.

Here's the solution I implemented:

  1. The task execution flow has two phases - planning and execution:
TaskExecutionStatus TaskManager::performTask(Task& task, 
                                             const string& command,
                                             TimerResults& timer_results) const {
    {
        ScopedTimer timer("Initialize and Plan Task Timer", timer_results);
        a…

Replies: 1 comment 12 replies

Comment options

You must be logged in to vote
12 replies
@lkaising
Comment options

@gavanderhoorn
Comment options

@gavanderhoorn
Comment options

@lkaising
Comment options

Answer selected by lkaising
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants