Skip to content

Potentially unexpected behavior when maxruns is not set but jointp and minruns are #2

@megan-k-ayers

Description

@megan-k-ayers

If my understanding is correct (I'm new to Stata!), in this case maxruns defaults to 1, so rerandomization will continue until the number of tries hits minruns even if the jointp criteria is met.

Ideally users are looking at the default values and realize this, but one idea to make this clearer is to force the user to specify maxruns and minruns if jointp is set rather than using the default.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions