Skip to content

Create and document type aliases for gsplat size typesΒ #117

@swahtz

Description

@swahtz

πŸ“‹ Originally created by @fwilliams

Original author: @fwilliams
Date: 2024-12-13T21:18:46Z


(Original issue by @harrism in old repo)

πŸ’­ thought (non-blocking): ‏ This means we support at most 2B Gaussians. We should probably define our own integer type for this, because someday we will want to increase this limit.

Originally posted by @harrism in https://github.com/voxel-foundation/fvdb/pull/388#discussion_r1877052339

Basically, we want to protect ourselves from the future need to increase the number of gaussians we support.

For image sizes, I don't see this being as risky because images tend to be in the thousands of pixels in each dimension. But we are already talking about billions of gaussians. So we don't want to hard code uint32_t everywhere. (Not to mention we may want sizes to be signed.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Gaussian SplattingIssues related to Gaussian splattng in the core librarycore libraryCore fVDB library. i.e. anything in the _Cpp module (C++) or fvdb python moduledocumentationImprovements or additions to documentationv0.1

    Type

    No type

    Projects

    Status

    No status

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions