We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The joint ordering is hardcoded in the network. It would be nice to expose this information somewhere
I wonder whether this can be enforced via a set of metadata to be inserted directly in the model, maybe using https://github.com/microsoft/onnxconverter-common/blob/d35ea904798313cec54ca8baf3aa1d11358d19f8/onnxconverter_common/metadata_props.py#L33 Anyhow, I am not sure if this is possible, so feel free to ignore this comment
I wonder whether this can be enforced via a set of metadata to be inserted directly in the model, maybe using https://github.com/microsoft/onnxconverter-common/blob/d35ea904798313cec54ca8baf3aa1d11358d19f8/onnxconverter_common/metadata_props.py#L33
Anyhow, I am not sure if this is possible, so feel free to ignore this comment
Originally posted by @S-Dafarra in ami-iit/bipedal-locomotion-framework#659 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The joint ordering is hardcoded in the network. It would be nice to expose this information somewhere
Originally posted by @S-Dafarra in ami-iit/bipedal-locomotion-framework#659 (comment)
The text was updated successfully, but these errors were encountered: