Answer the questions below in detail. Your responses will be emailed to experimenters.
If the experimenters must do anything new, provide detailed step by step instructions on the wiki
If computer maintainers need to manually update anything, provide detailed step by step instructions
Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
If you use the keyword "skip email" in the title, it will skip the email updates
Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
Merges from "production_testing" into "main" should use the keyword "update main"
Describe changes:
Right now, a large portion of the manual updates are pip install calls for new packages, or versioning. Now I've added pip install --upgrade -e . to the daily update script which ensures that all requirements are installed.
What issues or discussions does this update address?
Should save significant time on the part of scientists
Describe the expected change in behavior from the perspective of the experimenter
none
Describe any manual update steps for task computers
Pull Request instructions:
Describe changes:
Right now, a large portion of the manual updates are
pip install
calls for new packages, or versioning. Now I've addedpip install --upgrade -e .
to the daily update script which ensures that all requirements are installed.What issues or discussions does this update address?
Describe the expected change in behavior from the perspective of the experimenter
Describe any manual update steps for task computers
Was this update tested in 446/447?