[skip email] updating soundcard package

[alexpiet]

• Updates Harp.SoundCard bonsai package to 0.2.0
• After merging, run dynamic-foraging-task/bonsai/setup.cmd to install the new package
  • [ ] 446 @XX-Yin @ZhixiaoSu
  • [ ] 447 @XX-Yin @ZhixiaoSu
  • [ ] 428 @hagikent
  • [ ] Ephys1 @KanghoonJ
  • [ ] Ephys3 @XX-Yin
• This is a hot fix because the SoundCard package was manually updated in the 447 computers through the bonsai IDE, which leads to inconsistencies in the Bonsai.config file. We are updating the Bonsai.config file to make sure all rigs are consistent.

[hagikent]

@alexpiet Thanks for triggering. This is what I was wondering if we should adopt now or not. This 0.2.0 is a pre-release and, according to Gonsalo, a very tentative beta (See this discussion with Josh). Given only GoCueUploader is dependent on this newest package, I kept manually adding it when needed (and @ZhixiaoSu @XX-Yin did the same for 447 yesterday). Hope this update doesn't cause any compatibility issue with existing Harp-soundcard functions used in the main foraging workflow. Let's keep eye on sound function on Mon after the merge.

[ZhixiaoSu]

@hagikent Thank you for the super helpful information! This manual installation seems to be compatible with main behavior workflow when @XX-Yin and I tested yesterday. (Sound player normally and attenuation changed tone level.) Will adding the package manually affect the daily refresh at 6 am?

[hagikent]

affect the daily refresh at 6 am?

No, but the manually added package will be pushed back to 0.1.0 next 6am. With a minor (yellow) alert from RoboAlex.

[alexpiet]

What is strange is that the update this morning didn't reset the repo. The bonsai/bonsai.config file had untracked changes after the 6am update. Completely unclear to me why this happened. I manually reset the 447 computers, but it was a mysterious process. I recompiled bonsai, and did a git pull origin main in the command line, which somehow worked. I'll close this PR for now, but in the future, when installing new bonsai packages we need to ensure there are no untracked changes.

[hagikent]

Hmm, that's mysterious... never happened to me at 446/428, where I did this manual package adding >50times.

[alexpiet]

Actually, now that I look. This warning is in the logs for 446. Maybe because no one has run mice they haven't been noticing

[alexpiet]

I updated all the 446 computers except 7CD because IT is doing something remotely

[hagikent]

Yes, Ian from IT is working on 7C, trying to solve the Soundcard compatibility issue.