Skip to content

Dropout keys are too deterministic #423

@seanmor5

Description

@seanmor5

Right now we build a bunch of keys up front in layer compilation and pass them to dropout, but this is actually insufficient as the key will be fixed for every computation. That means we'll end up masking the same part of each layer during dropout, which is not at all correct.

Instead, we probably need to treat dropout keys as state and aggregate them during training like we do with some normalization stats

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions