You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then usually they actually don't know what's in the dataset, so they probably would need to inspect the entire folder to understand the filenames and subdirectories. It would be nice to see the file directory within each docstring to enable a more seamless dev experience.
Describe your proposed implementation
Idk how, but somehow piping the output of something like print_dir_tree of each datasets into their respective docstring?
Describe possible alternatives
Someone can just download the dataset I suppose and inspect it.
🤷🏻 seems like it would have helped you if that note were in the docstring right? It ought to work on Windows and Linux at least; I'd say if you can verify it (or something similar) works for Mac, go ahead and add it.
Describe the new feature or enhancement
When a developer is using the datasets available in
mne.datasets
e.g. https://mne.tools/stable/generated/mne.datasets.sample.data_path.htmlthen usually they actually don't know what's in the dataset, so they probably would need to inspect the entire folder to understand the filenames and subdirectories. It would be nice to see the file directory within each docstring to enable a more seamless dev experience.
Describe your proposed implementation
Idk how, but somehow piping the output of something like
print_dir_tree
of each datasets into their respective docstring?Describe possible alternatives
Someone can just download the dataset I suppose and inspect it.
Alternatively, perhaps this page can be updated and linked within each dataset function? https://mne.tools/stable/overview/datasets_index.html#datasets
Additional comments
The idea came up in mne-tools/mne-connectivity#100 (comment)
The text was updated successfully, but these errors were encountered: