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

[ENH] Store hard and soft losses as Python scalars instead of 0-dimensional NumPy arrays #3

Closed
ulupo opened this issue May 14, 2024 · 0 comments · Fixed by #4
Closed
Assignees
Labels
breaking Backward-incompatible changes enhancement New feature or request
Milestone

Comments

@ulupo
Copy link
Collaborator

ulupo commented May 14, 2024

No description provided.

@ulupo ulupo added the enhancement New feature or request label May 14, 2024
@ulupo ulupo self-assigned this May 14, 2024
@ulupo ulupo changed the title Store hard and soft losses as Python scalars instead of 0-dimensional NumPy array [ENH] Store hard and soft losses as Python scalars instead of 0-dimensional NumPy arrays May 14, 2024
@ulupo ulupo added the breaking Backward-incompatible changes label May 14, 2024
@ulupo ulupo added this to the 0.1.1 milestone May 14, 2024
ulupo added a commit to ulupo/DiffPaSS that referenced this issue May 14, 2024
Use .item() instead of dccn for losses. Change type annotations accordingly.
@ulupo ulupo closed this as completed in #4 May 14, 2024
ulupo added a commit that referenced this issue May 14, 2024
Use .item() instead of dccn for losses. Change type annotations accordingly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Backward-incompatible changes enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant