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

Move TaskComposerProblem input to base class and change type to tesseract_common::AnyPoly #407

Conversation

Levi-Armstrong
Copy link
Contributor

@Levi-Armstrong Levi-Armstrong commented Nov 6, 2023

Addresses #399

Copy link
Contributor

@marip8 marip8 Nov 6, 2023

Choose a reason for hiding this comment

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

Since all tasks will now be required to put their input data in the problem directly, would it make more since for the executor to put the input data in the correct place in the internal data storage object, rather than having this separate task* do it? Otherwise, it seems like all pipelines from here on out will need to have this as the first task in the pipeline

* I understand this this task also checks that the input is a composite instruction, but it's other major function is to put the input data into the correct spot in the data storage object for downstream tasks

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Lets add it as an issue to investigate if this is the right thing to do.

@Levi-Armstrong Levi-Armstrong merged commit fe80ad5 into tesseract-robotics:master Nov 6, 2023
6 of 10 checks passed
@Levi-Armstrong Levi-Armstrong deleted the feat/MoveTaskComposerProblemInput branch November 6, 2023 22:16
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