Hello - When an h5 file is supplied to suite2p through the run_s2p command as a list in the h5py input key, the data_path key is still checked in io.utils.find_files_open_binaries and subsequently, searches the data directory. It looks like this can be fixed by re-ordering the logic in the io.utils.find_files_open_binaries which I have created a PR for. I bring this up because in default_ops, it states that the data_path is deactivated if an h5py key is provided and I would like to be able to supply the key without out suite2p looking anywhere else. Thanks!
No error, just a note stating the following coming from the io.utils package:
NOTE: using a list of h5 files:
['/tmp/nxf.ymdA9tRLDh/capsule/data/965680907.h5', '/tmp/nxf.ymdA9tRLDh/capsule/data/965980162.h5']
Describe the issue:
Hello - When an h5 file is supplied to suite2p through the run_s2p command as a list in the h5py input key, the data_path key is still checked in io.utils.find_files_open_binaries and subsequently, searches the data directory. It looks like this can be fixed by re-ordering the logic in the io.utils.find_files_open_binaries which I have created a PR for. I bring this up because in default_ops, it states that the data_path is deactivated if an h5py key is provided and I would like to be able to supply the key without out suite2p looking anywhere else. Thanks!
Reproduce the code example:
Error message:
Version information:
0.13.1
Context for the issue:
No response