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 the GUI generates a warning if there is a missing camera trigger file. However if no video data was collected, then this file wont exist. Now we check for saved video data before issuing a warning. If saved video data does exist, the warning is logged as an error
What issues or discussions does this update address?
resolves #442
Describe the expected change in behavior from the perspective of the experimenter
Removes confusing warning message in 447 rigs
Describe any manual update steps for task computers
Pull Request instructions:
Describe changes:
Right now the GUI generates a warning if there is a missing camera trigger file. However if no video data was collected, then this file wont exist. Now we check for saved video data before issuing a warning. If saved video data does exist, the warning is logged as an error
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?