Add support of using both Comet and Viewer at the same time #2488
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tancik
approved these changes
Oct 4, 2023
|
@tancik just curious when the next release is? |
|
It will be post CVPR. We are planning to package the new viewer and gaussian splatting into the release so it's a bit larger than normal. |
|
Thanks @tancik. So next Summer 2024 is the next release? Or did you by chance mean Neurips in December? |
|
It'll be this year. 🙂 After CVPR meant after the deadline, which most of the core team/maintainers are currently tied up with! The paper deadline is 11/17 and the supplementary is 11/26. |
|
hi @brentyi just curious what the current timelines are for the next release? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our previous PR #2431, we forgot to update the is_viewer_enabled function, causing an issue where Comet and the Viewer could not be used simultaneously. This issue has now been resolved. Additionally, I took the opportunity to slightly refactor the function, making it easier to update in the future.