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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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.
The text was updated successfully, but these errors were encountered: