Fix dtypes handled in the labels of the decoders #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stes
force-pushed
the
celia/dtype-decoder
branch
from
06199ad to
cf77d2e
Compare
|
Seems like the
I'll disable the comment function for now so we can merge this and other upcoming PRs, the check is still executed. |
stes
force-pushed
the
celia/dtype-decoder
branch
from
cf77d2e to
87bc21e
Compare
stes
requested changes
Jul 2, 2023
2 tasks
stes
approved these changes
Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
intandfloatsubtypes accepted to be in the labels of the decoders were hard coded, which results in errors forint8for instance.Now, it supports all subtypes of Integer and floating in numpy arrays and pytorch tensors.
Fix https://github.com/AdaptiveMotorControlLab/CEBRA-dev/pull/616