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.

Sign up for GitHub

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

Jump to bottom

Decide on dtype conventions #52

Open
J08nY opened this issue Oct 26, 2023 · 0 comments
Open

Decide on dtype conventions #52

J08nY opened this issue Oct 26, 2023 · 0 comments
Assignees
@J08nY
Labels
docs Documentation enhancement New feature or request

Comments

@J08nY
Copy link
Owner

J08nY commented Oct 26, 2023

Trace processing functions can (and do) change the dtype of traces they process. Not of the inputs but of the outputs. This should be at least documented and a sensible strategy should be chosen to:

  • Make sure the results make sense and have enough precision.
  • Make sure the results are not unnecessarily large/precise.
  • (Potentially) Follow similar conventions as numpy/scipy to not surprise people, as we usually just wrap some of their functionality.
@J08nY J08nY added enhancement New feature or request docs Documentation labels Oct 26, 2023
@J08nY J08nY self-assigned this Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@J08nY J08nY

Labels
docs Documentation enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@J08nY