Marker/edge centric fc #169
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!169
Loading…
Reference in a new issue
No description provided.
Delete branch "marker/edge_centric_fc"
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?
This pull request adds an implementation for EdgeCentricFCParcels and EdgeCentricFCSpheres following the API of the functional connectivity base class.
Codecov Report
100.00% <ø> (ø)93.43% <95.55%> (+0.02%)Flags with carried forward coverage won't be shown. Click here to find out more.
100.00% <ø> (ø)88.88% <88.88%> (ø)100.00% <100.00%> (ø)100.00% <100.00%> (ø)92.85% <100.00%> (+2.38%)Reminder to merge this PR after #107.
I think it's missing an entry in the doc/bultin section.
@ -0,0 +68,4 @@) -> None:self.coords = coordsself.radius = radiusif radius is None or radius <= 0:Do we really need > 0? In nilearn terms (same as junifer), radius=0 means "single voxel".
@ -0,0 +68,4 @@) -> None:self.coords = coordsself.radius = radiusif radius is None or radius <= 0:From nilearn's docs,
radius = Noneextracts signal from single voxel, not sure about 0 though. I think the condition can be improved in the sense that,radius is Noneis valid so it can be removed. This was copied fromFunctionalConnectivitySpheres, so need to update that as well. I can open a new PR to address this for both.This is done now.
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinates@LeSasse Is there any related publication explaining the method?
@ -0,0 +68,4 @@) -> None:self.coords = coordsself.radius = radiusif radius is None or radius <= 0:Yes please. The SphereAggregator takes care of that error. There's no reason to check it in other markers with a different condition (unless it invalidates the marker)
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesFrom the class' docstrings:
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesCan you add this to the docs?
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesLike you mean in the
builtin.rst?@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinateswe can also add this one as it was published a bit earlier (by the same group): https://www.nature.com/articles/s41593-020-00719-y but the 2021 one was the one i used as a reference for implementation
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesyes
The idea is that people looking at markers list can know what they are.
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesthis paper is also on topic but by a different group and more of a reaction to the eFC method, but may be an interesting read for users: https://www.nature.com/articles/s41467-022-29775-7
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesWhich column should it go in then?
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesIn the description.
@ -182,6 +182,16 @@ Available- Calculate (f)ALFF and aggregate using spheres placed on coordinatesI have added the reference.
These lines are not covered by unit tests.
I will add a test.
Cheers @LeSasse!