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

directory errors when running scripts #12

Open
rythorpe opened this issue May 4, 2022 · 2 comments
Open

directory errors when running scripts #12

rythorpe opened this issue May 4, 2022 · 2 comments

Comments

@rythorpe
Copy link

rythorpe commented May 4, 2022

I've been trying to run through the basic pipeline here but keep running into I/O errors with the current directory structure. In particular, it looks like there should be an ~/ERPscanr/data directory with a few downstream branches. I'm happy to add the appropriate directories manually, though it'd be helpful if you could give me a quick snapshot to speed things up.

@TomDonoghue
Copy link
Member

TomDonoghue commented May 16, 2022

Hey @rythorpe - sorry for a bit of delay, I've been away a bit recently.

You are right that there is a data directory that is used / needed for completely recollecting and reprocessing the data. (If you just want to explore the previously collected data, I believe you should be able to drop in the folder available on OSF to the data folder). Otherwise, the data folder mostly follows the LISC directory layout, with some project specific tweaks (note that in ERPscanr, terms are stored elsewhere, figure sub-folders are custom, and the background sub-folder is also custom). This should have been better documented somewhere (my bad on that).

For a short cut, here is a snapshot of the data folder as it looks for me - you should be able to follow this, and generate LISC directory structures to create the tree you need to collect / process things, etc.
Screen Shot 2022-05-16 at 12 46 57 PM

Let me know if that works, and/or if there are any other issues! When I get a chance, I'll try and add some better detailing of this to the repo here.

@rythorpe
Copy link
Author

This is perfect - thanks @TomDonoghue!

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

2 participants