Skip to content

Weird EEGDash dataset object behavior #23

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

Open
arnodelorme opened this issue Apr 7, 2025 · 1 comment
Open

Weird EEGDash dataset object behavior #23

arnodelorme opened this issue Apr 7, 2025 · 1 comment

Comments

@arnodelorme
Copy link
Contributor

ds_sexdata = EEGDashDataset({'dataset': 'ds005510', 'task': 'RestingState'}, target_name='sex') 
tmp1 = ds_sexdata[0].getitem()
tmp2 = ds_sexdata[0].getitem()
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[16], [line 1](vscode-notebook-cell:?execution_count=16&line=1)
----> [1](vscode-notebook-cell:?execution_count=16&line=1) tmp = ds_sexdata[0].getitem()

AttributeError: 'tuple' object has no attribute 'getitem'

The call for tmp1 works, but not the call for tmp2. The ds_sexdata object is being modified by the first call and transformed to a tuple.

@dungscout96
Copy link
Contributor

The first call tmp1 = ds_sexdata[0].getitem() doesn't work for me. The indexing into the ds_sexdata implicitly call the __getitem__ function, which returns a tuple. With braindecode it's one recording sample data and its label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants