Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-generate export_config.py #16

Open
kwabenantim opened this issue Jun 28, 2024 · 2 comments
Open

Auto-generate export_config.py #16

kwabenantim opened this issue Jun 28, 2024 · 2 comments

Comments

@kwabenantim
Copy link
Member

Summary

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.

@chonlei
Copy link
Member

chonlei commented Aug 8, 2024

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.

@mirams
Copy link
Member

mirams commented Aug 8, 2024

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants