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
At minimum, the optimal combination step is duplicated in our report text and visual reports. We should review the logging code to ensure that report text is only logged once, as appropriate.
In the five-echo test's current report (emphasis mine):
TE-dependence analysis was performed on input data. An adaptive mask was then generated, in which each voxel's value reflects the number of echoes with 'good' data. Multi-echo data were then optimally combined using the T2* combination method (Posse et al., 1999). Multi-echo data were then optimally combined using the T2* combination method (Posse et al., 1999). Multi-echo data were then optimally combined using the T2* combination method (Posse et al., 1999). Next, components were manually classified as BOLD (TE-dependent), non-BOLD (TE-independent), or uncertain (low-variance). This workflow used numpy (Van Der Walt, Colbert, & Varoquaux, 2011), scipy (Jones et al., 2001), pandas (McKinney, 2010), scikit-learn (Pedregosa et al., 2011), nilearn, and nibabel (Brett et al., 2019). This workflow also used the Dice similarity index (Dice, 1945; Sørensen, 1948).
Additional Detail
Next Steps
Review logging code
Eliminate duplicated text by adding a report argument to the relevant functions and setting to False when called 2+ times. See fit_loglinear for an example:
The text was updated successfully, but these errors were encountered:
tsalo
added
bug
issues describing a bug or error found in the project
documentation
issues related to improving documentation for the project
reports
issues related to boilerplate generation or visual reports
and removed
documentation
issues related to improving documentation for the project
labels
Dec 30, 2020
Summary
At minimum, the optimal combination step is duplicated in our report text and visual reports. We should review the logging code to ensure that report text is only logged once, as appropriate.
In the five-echo test's current report (emphasis mine):
Additional Detail
Next Steps
report
argument to the relevant functions and setting toFalse
when called 2+ times. Seefit_loglinear
for an example:tedana/tedana/decay.py
Line 158 in 45e5ad7
The text was updated successfully, but these errors were encountered: