Skip to content

Pull request for 133: Updates to production guidelines #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jmshapir merged 2 commits into from
Nov 23, 2025
Merged

Pull request for 133: Updates to production guidelines #134

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cbe5f9a
Randomization for #133
jmshapir Nov 3, 2025
8a2be2b
Branches for #133
jmshapir Nov 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/production.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Production encompasses the steps we take before we circulate or submit a paper d
* Do not create a subissue branch until you are ready to make edits.
* When creating a subissue branch, branch off of the main production branch.
* Avoid compiling on subissue branches unless necessary.
* When merging a subissue branch, merge back to the main production branch.
* When merging a subissue branch, merge back to the main production branch and update other open production branches.
* Skip review of pulls for tasks where work has already been reviewed by multiple RAs, except where PI review is requested below.

* When producing task deliverables:
Expand Down Expand Up @@ -95,6 +95,7 @@ Production encompasses the steps we take before we circulate or submit a paper d
#### Deliverables

* Check the below and notify the PI of any suggested changes.
* Randomization is controlled (e.g. by fixed seeds)
* Bootstraps and simulations run with sufficiently high number of draws
* Quadrature accuracy set sufficiently high
* Tolerances on solvers satisfactory
Expand Down