igorbusch
commented
6 days ago Anything that can be damaging to equipment, even if it’s very rare like 1% of the time, please report in order to shift our protocols. We discussed the repair list in detail and a few of the occurrences in the lab. We discussed the Slack statuses, everyone has seemingly been using them, and it's helpful. George thinks it’s a good idea to introduce standard emojis for different places, so we noted the ones decided on in Slack. Karla is officially not a volunteer anymore but a paid staff member. Mahlon mentioned that during EEG 101 it should be reinforced to try reworking the ground/reference when encountering artifacts in all channels or inability to get a majority of the channels green. Perhaps the easiest thing to do is to record a video(s) that will serve as a good reference for new RAs for what to do when capping and encountering those situations where troubleshooting the issue comes from easy fixes. We will start adding those items to a Google Drive folder. Olivia already has a folder in the equipment-management folder, but we are considering creating a new one with more recent training items. The issues with the grounds are inconsistent and not always re-creatable so there has to be some way to centralize and track every kind of issue. The EEG-use log is the current place where any trouble is reported, at the end of the tracker in a space for notes. Mahlon will update the tracker for Thrive and Read to make error-reporting clearer, looking for obvious issues that stop people from reaching maximum impedance, etc.
This meeting:
Felix practicing CN series talk
Next meeting: Kia present overview of quals