[BUG]: extMDN coordinates are falsely registered as extDMN coordinates in junifer #251
No reviewers
Labels
No labels
CRITICAL
Stale
WIP
bug
concept
coordinate
dataset
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
maintenance
maps
marker
mask
on hold
parcellation
preprocess
question
ready
storage
template-space
triage
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!251
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/emdn-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there an existing issue for this?
Current Behavior
In this table the extended multiple-demand network is correctly listed as
extMDN, but when using the following marker:one gets the following error:
Using the
list_coordinates()function, it seems clear why:The naming is incorrect in junifer (
extDMN)Expected Behavior
It should have the correct name and the marker should work.
Steps To Reproduce
described above
Environment
Bug in the documentation:
eMDNextDMNis the Extended Default Mode Network.Codecov Report
100.00% <ø> (ø)Flags with carried forward coverage won't be shown. Click here to find out more.