Hello Francois, hoping all is well. Thanks as always for an excellent and useful software.
I've sent this as a private note as it is unclear if useful to send in the Forum.
In regards to wpli in BS below: [unclear how this testing/checking relates to main current BS development goals, but surely having clarity/validity regarding the connectivity metrics is important BS to continue to grow as a go to for E/MEG analytics.] If there is no timeline and if there remain many unknowns, that is fine of course, but important to know.
My apologies if my questions are naive, and I presume they reflect targets for BS developers anyway.
- it seems that changes were made recently on github to BS code for wpli - and it's not clear what the resolution was there
- however, from notes/exchanges here in the Forum, and in the Github notes
it remains unclear - whether wpli estimates were valid before last changes on Date X
- whether new wpli estimates are correct/valid after Date Y
- what's the difference between the two versions
- how are these BS versions different specifically from the published wpli, dwpli,
- were the tutorial pages updated to reflect or document these changes?
The above also brings up worries about any other connectivity metrics in BS
We would love to lean on and trust BS for large sample data analyses,
but without more (and consistent) clarity on metrics details such as the above, it suggests that it's up to the users of the software to do validity checks on any/all connectivity measures being used,
to dig into the unique code for each, compare with code/methods in other software,
and then make best choice possible.
One last question for you: Do you think the field will have to do something like the below for each metric of interest across softwares ? I am sure you are familiar with other similar recent work, e.g., MNE across softwares.
See figure 5 for example here:
https://www.biorxiv.org/content/10.1101/2022.08.03.502683v1.abstract