Skip to content

Evaluate the "Highest-Layer" Algorithm #8

Description

@dawsonc623

The way layering is implemented in ren2 keeps track of the highest layer and scales accordingly. So, if the layers 0, 1, 2 and 1000 are used, then 0, 1, and 2 are pushed to the extremes of the positive z axis (0.9) while 1000 is pushed to the extreme of the negative z axis (-0.9). The entire middle is left unoccupied. With a big enough discrepancy, it is theoretically possible that the precision of floating point numbers could create layering issues (i.e. the low end of the layers all getting pushed to 0.999999... until the computer had no more space to store the minute differences between the layers).

Is this issue practical or problematic enough to warrant a more bulletproof algorithm?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions