-
Notifications
You must be signed in to change notification settings - Fork 627
Simplify scale #3351
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
base: main
Are you sure you want to change the base?
Simplify scale #3351
Conversation
f546c5e
to
f57a9b0
Compare
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Benchmark changes
Comparison: https://github.com/scverse/scanpy/compare/329ad666f280b3e7335b3735a04a0a97f430e6f2..233d8a346423bea0043baef72595adf3fddc3d3e More details: https://github.com/scverse/scanpy/pull/3351/checks?check_run_id=40505086063 |
@Intron7 any idea what I did wrong? Why do the benchmarks say that it uses more memory? |
@Intron7 ping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would make the default code path for csr even faster. otherwise LGTM
for more information, see https://pre-commit.ci
scale_sparse
has a lot of code that’s not needed.This PR also fixes zappy compatibility for
scale
, not that anyone is using it as far as I know.