Another point from today's WFDB group meeting (and following some discussion between @peterhcharlton and @manlik-brownsrdr) was the suggestion that we should (1) make it easier for people to find and share "wfdb-compatible" software (2) improve motivation for people to share.
e.g. If I submit a new WFDB-compatible algorithm to PhysioNet, I should be able to:
Understand what it means for my software to be WFDB-compatible
Formally label my software as WFDB-compatible (e.g. with a tag/label)
Allow others to easily discover the software on PhysioNet with a "WFDB tools" search.
All WFDB-compatible datasets should carry a similar WFDB-compatible label, so that it is easy to identify which algorithms can be used on which datasets. @bemoody @cx1111 @ikarosilva @manlik-brownsrdr @briangow
When implementing this approach, we may want to consider how the functionality can generalize beyond "WFDB". e.g. maybe the same general idea could apply to OMOP tools and data.
Another point from today's WFDB group meeting (and following some discussion between @peterhcharlton and @manlik-brownsrdr) was the suggestion that we should (1) make it easier for people to find and share "wfdb-compatible" software (2) improve motivation for people to share.
e.g. If I submit a new WFDB-compatible algorithm to PhysioNet, I should be able to:
All WFDB-compatible datasets should carry a similar WFDB-compatible label, so that it is easy to identify which algorithms can be used on which datasets. @bemoody @cx1111 @ikarosilva @manlik-brownsrdr @briangow
When implementing this approach, we may want to consider how the functionality can generalize beyond "WFDB". e.g. maybe the same general idea could apply to OMOP tools and data.