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
Is your suggestion related to a problem? Please describe.
Currently, detectorIndex and sourceIndex of a measurementList is an integer. However, computing StO2 using spatially resolved spectroscopy requires an array of either detectors or sources. That's just how the math works. Roughly, SRS computes the slope of ODs across multiple distances, and computes StO2 based on that, so the StO2 value is derived from multiple detectors and/or sources.
Describe the solution you'd like
Make these vectors instead of scalars
Describe alternatives you've considered
Use some hacky workaround on the manufacturer side.
Is your suggestion related to a problem? Please describe.
Currently, detectorIndex and sourceIndex of a measurementList is an integer. However, computing StO2 using spatially resolved spectroscopy requires an array of either detectors or sources. That's just how the math works. Roughly, SRS computes the slope of ODs across multiple distances, and computes StO2 based on that, so the StO2 value is derived from multiple detectors and/or sources.
Describe the solution you'd like
Make these vectors instead of scalars
Describe alternatives you've considered
Use some hacky workaround on the manufacturer side.
Additional context
For a laymen explanation of SRS, see https://www.artinis.com/blogpost-all/2022/tissue-saturation-index-tsi-absolute-oxygenation-measure-in-local-tissues
Note that both we (Artinis) and Hamamatsu (and others) use SRS for computing StO2.
The text was updated successfully, but these errors were encountered: