Accessing current hemorrhage severity for a compartment

I have a system where multiple different parts of my application may contribute to the severity of a hemorrhage in a single pulse compartment (e.g., at the application level, the patient may be hemorrhaging from the chest and abdomen, but in pulse these both map onto skin+muscle). Is there a way to access the current hemorrhage severity for a compartment? I’m planning to track it myself, but for unit testing that tracker it would be nice to get access to the severity directly from the pulse engine.

It looks like in the C++ interface the GetActionManager() method can give access to the current actions, which sounds like it would work. Unfortunately, I’m using the Java interface, and I don’t see how to access it from there.

Yep, you can get that information from the C++ interface pretty easily. I am currently investigating ways to get more of these type of details out of the C style interface (which serves Java, C#, python).

I also need to get out assessments, and conditions, actions, and also support dynamic data requests (so you can request the current flow of a hemorrhage)

I’m hoping to be able to have this working in the next few weeks.

1 Like

In the past I’ve used SWIG to automatically generate interfaces for other languages for C++ code. Might be something to look into.

FYI, this is working on the latest 3.x branch, and will be in the 3.2 release in the next few weeks!

You can get the compartment hemorrhage rate/volume by creating a data request, or getting the active actions from the engine.

I have NOT (but I can) add support to ‘add’ to the data requests.
So you could dynamically add a new data request for a new hemorrhage if you got that in your system
Which would update the length of the data array… and what not
Not done, but doable…

Privacy Notice