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
How open-source friendly are APIs, SDKs of the suported/tested devices? and what other features the supported devices offer (image quality, frame streaming, regulatory approvals, AI-based US, etc)?
#28
Open
mxochicale opened this issue
Feb 2, 2022
· 1 comment
I wonder if there is any sort of comparison of the supported portable devices and how open-source friendly are such devices with other features (costs, regulatory approvals, AI-based US, etc). Let me draft a table based on I can see in the repo. The table might provide a bit of the overview for the supported devices with ITKPOCUS. I guess as I dig in into the devices I will add a bit more details but feel free to edit it or maybe suggest create a PR to be add it in the documentation.
Device brand, url
Model
Cost (date)
API programming language, SDK, OS-support, github, etc
C++, Fully supported on Windows 32/64 bit with Visual Studio 2105 and above
image quality?
USA FDA 510(k) clearance, EU CE Mark and MDD 93/42 EEC compliant, ISO 13485:2016 compliant and certified, Safety testing, IEC 60601 safety and EMC, Materials biocompatibility, Acoustic power output
Hi Miguel, that's a great idea. The image quality metrics are something we currently are working to publish. Sorry for the delay in reply, my notifications were inadvertently disabled on this repo.
Thanks for sharing such great project!
I wonder if there is any sort of comparison of the supported portable devices and how open-source friendly are such devices with other features (costs, regulatory approvals, AI-based US, etc). Let me draft a table based on I can see in the repo. The table might provide a bit of the overview for the supported devices with ITKPOCUS. I guess as I dig in into the devices I will add a bit more details but feel free to edit it or maybe suggest create a PR to be add it in the documentation.
Miguel
The text was updated successfully, but these errors were encountered: