Skip to content

Conversation

@yammineramy
Copy link

Background

[Describe the background for this PR here.
Edit this description and all other fields in square brackets. Check the box when the item is fully resolved, check and add "N/A" if not applicable.]

What's new

  • [New feature description]

Related work

  • [link] needs this PR

TODOs / Nice-To-Haves

  • [Add system tests for new feature.]

Comment on lines +37 to +44
// start and goal system confs for problem to solve and insert into db
SystemConf start_sysconf = 6;
SystemConf goal_sysconf = 7;
}
}

// Response which contains the result of attempting to start computation of a
// solution for the corresponding StartBuildRequest.
/** Response which contains the result of attempting to start computation of a
* solution for the corresponding StartBuildFromConfsRequest. */
Copy link
Contributor

@davebambrick davebambrick Jul 15, 2024

Choose a reason for hiding this comment

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

I commented this on the planning_service PR, but I think we'd probably want to break out the "update roadmap" call into its own RPC. An example could be something like:

message UpdateRoadmapRequest {
  // Definitions of motion plans to be solved.
  repeated ProblemDef pdef = 1;
  // Options passed to the solver.
  UpdateRoadmapOptions options = 2;
}

message UpdateRoadmapResponse {
  // Metrics of the resultant solution.
  SolutionMetrics metrics = 1;
}

service IrisBuilder {
  [...]
  // Update the roadmap by solving a set of motion problems and saving their results.
  rpc UpdateRoadmap(UpdateRoadmapRequest) 
    returns (UpdateRoadmapResponse) {}
}

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.

3 participants