Following up on #443 , we should decide on where rig config should live long term.
Two possible suggestions were to either 1) create new branches in 'aeon_experiments' that represent rigs (e.g. 'rig_aeon4', 'rig_aeon3'), or 2) to create a new repo called 'aeon_rigs' where these branches would live.
Then, possibly, experiment branches (e.g. 'social') could find ways to pull in data from these branches (e.g. via submodules or some other way) and rig calibration files would be more modular and not pollute experiment branch workspaces.
@glopesdev please feel free to edit or add info to this.
Following up on #443 , we should decide on where rig config should live long term.
Two possible suggestions were to either 1) create new branches in 'aeon_experiments' that represent rigs (e.g. 'rig_aeon4', 'rig_aeon3'), or 2) to create a new repo called 'aeon_rigs' where these branches would live. Then, possibly, experiment branches (e.g. 'social') could find ways to pull in data from these branches (e.g. via submodules or some other way) and rig calibration files would be more modular and not pollute experiment branch workspaces.
@glopesdev please feel free to edit or add info to this.