You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A manually created export_config.py is required in the data folder. We might want to auto-generate it because by default it is not there from the syncropatch machine.
Alternatively, it could be moved to the pcpostprocess directory.
We should add a README entry explaining how to set up this config file.
The text was updated successfully, but these errors were encountered:
Probably my bad. When I first created it, I was handling only one dataset for myself, so thought it'd make sense to leave it with the data, as it is more like a meta data file for exporting. Not sure how you would generate it automatically as it tries to specify file names that are probably different in different experiments/runs (user specifies it). I guess moving it to the export repo would make sense.
Difficult to automate because it depends what the user typed in to the SyncroPatch to name the protocol (unless we analyse the protocol definitions to spot the staircaseramp, but that seems overkill!). So maybe we keep it as it is and just manually add them all for now. @joeyshuttleworth has started doing it manually I think...
Summary
A manually created
export_config.py
is required in thedata
folder. We might want to auto-generate it because by default it is not there from the syncropatch machine.Alternatively, it could be moved to the
pcpostprocess
directory.We should add a README entry explaining how to set up this config file.
The text was updated successfully, but these errors were encountered: