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

backend: unify data conversion methods, uint and array performance #3810

Open
fm3 opened this issue Feb 21, 2019 · 3 comments
Open

backend: unify data conversion methods, uint and array performance #3810

fm3 opened this issue Feb 21, 2019 · 3 comments

Comments

@fm3
Copy link
Member

fm3 commented Feb 21, 2019

currently duplicated in isosurfaceservice and finddataservice (as of #3682)

@fm3
Copy link
Member Author

fm3 commented May 25, 2022

The duplication mentioned above has been resolved in the meantime.

However, we now have multiple concepts for typed arrays (UnsignedInteger, spire, ucar multiArrays), which should be unified (needs performance testing)

@jstriebel
Copy link
Contributor

I'd recommend to have a look here as well before tackling this issue:
https://github.com/lasersonlab/ndarray.scala

@fm3 fm3 changed the title refactor backend: extract data conversion methods refactor backend: extract and unify data conversion methods May 26, 2022
@fm3 fm3 changed the title refactor backend: extract and unify data conversion methods refactor backend: unify data conversion methods May 31, 2022
@fm3
Copy link
Member Author

fm3 commented May 31, 2022

I created a design doc / analysis here. Unfortunately, I do not currently have a unified solution for all use cases.

https://www.notion.so/scalableminds/Design-Doc-Typed-Arrays-in-Backend-e4432cf17eef483281eee8eb9623fbaf

@fm3 fm3 changed the title refactor backend: unify data conversion methods backend: unify data conversion methods, uint and array performance Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants