-
Notifications
You must be signed in to change notification settings - Fork 155
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
ValueError: path while running the extractor #2820
Comments
@kshtjkumar, which version are you using. This was an error for Windows computer that was fixed previously. Could you post the exact paths you're using? (Feel free to put ... if there are parts you want to edit for privacy). E.g. recording = se.read_xx(r'E:\Users\...\experiment1\...\file.xx') |
current version of this notebook is : 0.99.1 |
I would update that to at least 0.100.x I believe the Windows fix was around that time. Otherwise you have to sort on the same drive where the data is. So you could test E: -> E: |
|
I dont mind updating but then I will have to change a lot of syntax and waveform extraction also for the newer version. |
For version 0.100.x you won't have to change anything. syntax changes with version 0.101.0. |
Hi here is my reader path, can you help with the changes ? |
My only recommendation for the path is that you should use a raw string instead. Windows paths can escape so using a raw string will protect you. file2 =r"E:\CEAF_PC_BACKUP\monica_EEG_GSstudy\L37_1_19_1_24_240120_102532\L37_1_19_1_24_240120_102532_merged.rhs" notice the |
Also as an FYI we've updated intan for neo 13.1 so now there is a difference between RHD and RHS amplifier stream. So that code may break with a future version of neo. Just in case you update. |
tried this it didnt work, same mounting error. |
After updating to spikeinterface 0.100.x? |
updated to 0.100.1, here is the error:
|
We fixed the drive error! So that's one down. So this is a multiprocessing error. What did you set And did you download the most recent 0.100.6 for example? |
not sure what is n_jobs, I can try 0.100.6 too! |
If you haven't messed with it then it should default to 1 except in |
this is after 0.100.6
|
Does anything appear in your terminal? When mountsort5 runs it usually starts printing stuff. Do you get to that point or does it break earlier? |
Okay cool, it is failing at the write_binary. Could you try: ss.run_sorter("mountainsort5", rec_ecog_ref, output_folder=output_folder, n_jobs=1) And see what it does? This might be pretty slow but it will help us diagnose things! |
it did work, but it is ver very slow! |
Cool. Okay so the problem is in the multiprocessing. Could you try setting |
so basically last time also when i tried the n_jobs argument it gave this error, previous run was executed without mentioning the n_jobs, so by default it took that as 1. here is the error:
|
Sorry then what did you change when it worked and when it didn't work? |
i just removed the n_jobs argument. |
I mean from when it failed due to the broken process and it actually working. It just randomly worked or you made a specific change? |
no after updating to 0.100.6 , i ran this command : but it gave the error : So i ran this command: this is the one which is very slow. |
If you type
What does it say? Because it was saying that it wasn't letting you change the
|
|
Sorry that was my typo you were right to type: si.get_global_job_kwargs() I'm still trying to figure out what if causing the multiprocessing to fail sometimes. |
sure! |
I am loading the file from hard disk (drive E) and running the extractor, is there something wrong with my code in assigning the path for the sorter ?
The text was updated successfully, but these errors were encountered: