Skip to content

Improve benchmarking vs cesium #460

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
Closed
hombit opened this issue Dec 6, 2024 · 1 comment
Closed

Improve benchmarking vs cesium #460

hombit opened this issue Dec 6, 2024 · 1 comment
Labels
python Pull requests that update Python code

Comments

@hombit
Copy link
Member

hombit commented Dec 6, 2024

Current benchmarks with cesium are not fair: cesium doesn't provide a clear way to build a feature extractor in advance. We should benchmark with ~100-1000 light curves instead of a single one.
@hombit hombit added the python Pull requests that update Python code label Dec 6, 2024
@hombit
Copy link
Member Author

hombit commented Feb 3, 2025

Implemented in #459

@hombit hombit closed this as completed Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hombit and others