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:
Uses a cached copy of the training schedule to set the IACUC protocol and Project Name when starting a new mouse
The cached copy is refreshed every 2 minutes (process running on my computer), and saved at /allen/aind/scratch/dynamic_foraging/DynamicForagingSchedule.csv
If the mouse is not on the schedule, no IACUC protocol is set, and the Project Name defaults to "Behavior Platform"
If the project description file is not present, then the Project Name defaults to "Behavior Platform"
Since the ephys rigs and 428 are not on the schedule, they will not have these fields set. But if the mouse went through training in 446/447, then it will already be set by the time the mouse goes to ephys/428
What issues or discussions does this update address?
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:
/allen/aind/scratch/dynamic_foraging/DynamicForagingSchedule.csv
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?