one.pid2eid not working for OneSdsc instance
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by running the reproducible OneSdsc script and inspect the pid2eid path in one/api.py around line 2026, including the local cache handling for insertions. Compare this with the OneSdsc setup in deploy.iblsdsc and establish whether local pid conversion is expected to work; done means the expected behavior is documented or the reported failure is resolved and verified.
Written by the indexing model from the issue text.
Description
Reproducible script -
from deploy.iblsdsc import OneSdsc
one = OneSdsc(mode='local' , cache_rest=None)
one.pid2eid("af1e9dee-8c26-4b2b-ac43-358221048797")
I get the following error -
---------------------------------------------------------------------------
NotImplementedError Traceback (most recent call last)
Cell In[2], line 2
1 one = OneSdsc(mode='local', cache_rest=None)
----> 2 one.pid2eid("af1e9dee-8c26-4b2b-ac43-358221048797")
File ~/projects/passive_ephys/.venv/lib/python3.10/site-packages/one/api.py:2026, in OneAlyx.pid2eid(self, pid, query_type)
2024 if query_type == 'local': # and 'insertions' not in self._cache.keys():
2025 if 'insertions' not in self._cache.keys():
-> 2026 raise NotImplementedError('Converting probe IDs requires remote connection')
2027 else:
2028 # If local, use the cache table
2029 pid = UUID(pid) if isinstance(pid, str) else pid
NotImplementedError: Converting probe IDs requires remote connection
It does not work even if I use one = OneSdsc(mode='local') .
I am using the following version of ONE and iblscripts.
iblscripts 1.0.0 (Installed via pip install git+https://github.com/int-brain-lab/iblscripts.git)
ONE-api 3.3.0
Is this something expected? And let me know if I am missing something.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from int-brain-lab/iblscripts
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
int-brain-lab/iblscripts#127 · 1 comment ·
-
Automate creation of subject trials and training status tablesMay be free again @juhuntenburg claimed this 949 days ago, and no pull request is open. Open
int-brain-lab/iblscripts#91 · 1 comment · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
int-brain-lab/iblscripts#69 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
int-brain-lab/iblscripts#21 · 1 comment ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
int-brain-lab/iblscripts#18 ·
All issues in int-brain-lab/iblscripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EmbarkStudios/cargo-deny#910 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenIntegrationEngine/engine#496 ·
Maintainers usually reply within 1 day
-
documentation glm5 llm-model
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/vllm-ascend#19062 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10496 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day