Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Synthetic data smoke test. #75
Synthetic data smoke test. #75
Changes from 26 commits
bbde0a4
4661907
d5cdd97
9baa1c7
a6b983f
7ed9f25
d4145c5
8248778
be2f1aa
935c922
2e6e01c
45774d9
e9c1a4f
f14910b
f6df7e3
7b16b5a
b75b354
6f7da79
5433344
2405815
9a2a599
86d333e
84793e9
82c1887
d9fe782
418a1e9
19a30e0
dc26558
dc881c3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How was the data saved from this notebook? And were there any offsets applied to the synthetic keypoint? I wanted to test whether it finds the ground truth offset when given different initial offsets in the
model.yaml
file, but it always returns the initial offset without any changes.This notebook doesn't run as is; the rendering is cell 3 is different for me from the one shared, and the last cell throw an error:
KeyError: "Invalid name '0'. Valid names: ['base', 'world']"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, it's just not ready for that. I changed to the title to reflect that it's just a smoke test... ie it runs with out crashing.
This PR isn't to provide that level of functionality, sadly. I've created #81 to track the next steps. Please feel free to add any specific requests to that.
As for the data generation, I created a single frame of fake data (not even collected from an actual Mujoco run) just to give an output.
Also, if you think there are any comments that need to be added to the code to make this clear, also lmk.
Large diffs are not rendered by default.
Check warning on line 88 in stac_mjx/stac.py
Codecov / codecov/patch
stac_mjx/stac.py#L88
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense 👍
Check warning on line 235 in stac_mjx/stac.py
Codecov / codecov/patch
stac_mjx/stac.py#L234-L235
Check warning on line 238 in stac_mjx/stac.py
Codecov / codecov/patch
stac_mjx/stac.py#L238
Check warning on line 355 in stac_mjx/stac.py
Codecov / codecov/patch
stac_mjx/stac.py#L354-L355
Check warning on line 358 in stac_mjx/stac.py
Codecov / codecov/patch
stac_mjx/stac.py#L358