Analyzing data with TDT storename containing '\'

[MannyEsguerra]

Windows 10, GuPPy version as of 11/6/2024

I need to analyze data that uses the TDT Storename 'Cn1\'.
storesList.csv thus contains these storenames:

415A,415C,465A,465C,Cn1\1,Cn1\2,Cn1\4,Cn1\6,Cn1\8,Cn1\10
control_LeftBox,control_RightBox,signal_LeftBox,signal_RightBox,Cn1\_1,Cn1\_2,Cn1\_4,Cn1\_6,Cn1\_8,Cn1\_10

The backslash character is causing problems at the "Extract timestamps" step, and throwing this error:

OSError: Unable to create file (unable to open file: name = 'D:\Data\Manny\OptoGEVI_Cohort4_SYNAPSE\pTrain_Opto_RealTime-250504\ME84-ME85-250824-102749\ME84-ME85-250824-102749_output_3\Cn1\_1_LeftBox.hdf5', errno = 2, error message = 'No such file or directory', flags = 13, o_flags = 302)

How should I deal with storenames that contain the \ escape character, so this file and path are created properly?

[pauladkisson]

I recently started working on this project, and the main developer (@venus-sherathiya) is currently on vacation until 9/3, so I can take a crack at this bug.

Would it be possible for you to share the raw data that is causing this problem so I can take a look? My email is paul.wesley.adkisson@gmail.com

[MannyEsguerra]

Email and TDT data block sent. Thank you.

[pauladkisson]

Thank you for sharing the data! I was able to put together a fix here. If you would like to test it out, simply check out the fix_backslash_in_storenames branch (git checkout fix_backslash_in_storenames). In any case, it will be merged into main shortly, as soon as Venus gets back.

I'd like to ask you if you would be willing to give your permission to add this data to our testing data repository here. This will allow us to make sure that GuPPy doesn't accidentally run into this bug again.

[MannyEsguerra]

I'll check out your branch and test it on the rest of the data from this cohort. Thank you!

Feel free to add that data block for testing. Just be aware it's all control data (should be no responses to opto stimulation), and there's really nothing else unusual about it except for me trying to use the 'Cn1' events.

Edited to add: the edited code works great, as expected. Looking forward to seeing it in main.