Base 36h11 Apriltags - #1
Conversation
|
@crainen-nasa , can you add a couple of things to this PR so that it matches some of our other standard repos (maybe color_tools could be a decent example)? I think that should include
|
There was a problem hiding this comment.
Im sure that there could be some cleanup in the batch processing things, but I think it is worth it to just get stuff in for now, and if we want to clean it later we can! Just one comment on adding how to scale things. But after that, I am good to send this through! @eholum-nasa , can you verify that the repo structure is as expected? I think once this goes through, there is something to add for workflows, but I think this might need to go through first?
edit - I think I was able to add the ruleset anyways, so as far as I understand, I think the repo is set up as it should be
eholum-nasa
left a comment
There was a problem hiding this comment.
Just add the python license headers and LGTM! I updated branch rulesets and other defaults in the repo settings so should be g2g.
updated python license header Co-authored-by: Erik Holum <erik.holum@nasa.gov>
The 36h11 family of meshes and textures.
As well as the quick and dirty generated scripts to generate them from my mesh and the supporting source 10px tag repo.
Id like to find a cleaner way to do this that doesnt duplicate the meshes but for now this will at least be functional