Currently using PyDICOM to read Sonoque dicom images. Evaluate what is missing from GDCM so that ITK IO can be used.

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

https://github.com/KitwareMedical/ITKPOCUS/blob/master/itkpocus/itkpocus/sonosite.py#L229

Interson doesn't store overlays in its native formats, so preprocessing isn't necessary, but the IO isn't implemented in Python.

Current documentation includes a step to confirm parameters in Visual Studio before building Sonivate. Push that parameter-passing into the CMakeLists.txt.

Add build process and testing badges where appropriate.

I'm having difficulty getting the out-of- docs/ .md files to render images correctly. I've tried using the myst-parser and m2r2 but the documentation isn't great and they simply aren't working.

Currently require IntersonStream to be built as a 32-bit application due to the vendor's 32-bit DLL. Consider wrapping the DLL ala this article.

Hello, I connected the clarius scanner, android tablet, and PC all under the same wifi network, and did everything as per readme. Slicer say the connection status is ON, however I do not see any data under Data I/O in slicer. We were able to ping the IP as well. Please let me know if I am missing something obvious.

Provide load_and_preprocess for the other probes (see sonoque.py). Kind of clunky to handle the video IO elsewhere.

Vendor's don't necessarily store version information in their file formats. Add a version parameter to future-proof preprocessing.

Clarius ruler spacing is variable, or at the least, newly changed to 0.2cm per tick as opposed to 1cm per tick. Need to update API to take spacing as a parameter and think long-term about making it discoverable.

Make CI testing automatic.

1. Using OpenIGTLinkIF plugin show the various devices streaming to Slicer

A write-up confirming the relationship between the 4x4 matrix used in pyigtl and OpenIGTLink and ITK image metadata. In seems that pygitl doesn't encode the spacing and direction directly (inferring it from the 4x4 matrix) but then parts of the OpenIGTLink standard suggest these are separate fields. Recommend examining the OpenIGTLink C++ implementation and the pygitl implementation to confirm.

1. Add mobileapi as an external dependency, not including the source
2. Prove a local.properties_template and add it to build instructions
3. Find a way to automated the empty libpthread.a generation
4. Separate OpenIGTLink-Android into its own build

Goal is to merge https://github.com/KitwareMedical/IntersonArraySDKCxx into this repo so that it is properly maintained and is better advertised. It would go into the Interson subdirectory.

Need more unit tests, especially for the preprocessing.

The Clarius spacing is set to 1.0 and needs to instead pull the micronsPerPixel from the Clarius API.