-
Notifications
You must be signed in to change notification settings - Fork 99
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
deprecate sapporo_light? #845
Labels
Comments
Sapporo_light has a number of deficiencies and from a ph4 standpoint, it only works properly with sapporo2. It still some issues, but it’s a basis for what we need, I think.
Steve
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 28 days if no further activity occurs. Thank you for your contributions. |
stale
bot
added
the
stale
Issues that have been around for a while without updates
label
Jul 2, 2022
rieder
removed
the
stale
Issues that have been around for a while without updates
label
Jul 30, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 28 days if no further activity occurs. Thank you for your contributions. |
stale
bot
added
the
stale
Issues that have been around for a while without updates
label
Sep 28, 2022
rieder
added
keep-open
and removed
stale
Issues that have been around for a while without updates
labels
Oct 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't know of any reason why sapporo_light should be preferred over sapporo2.
If there are none, I suggest deprecating sapporo_light in favour of sapporo2.
And perhaps sapporo2 could be updated to support Vulkan (which I think would increase the number of supported GPUs greatly), see treecode/sapporo2#5.
The text was updated successfully, but these errors were encountered: