What is the format/syntax for the "modifier_file" in the modification classes?

Pulse Physiology Engine
1

Hello! I am looking to modify the Cerebral Perfusion Pressure in my pulse simulation by adding/subtracting values. There’s a class, “SECardiovascularMechanicsModification”, used to modify the cardiovascular system here: which uses a set of default examples, but also has a method to take in a modifier file.

What is the syntax of that file and what are the limits of what parameters can be modified? I haven’t been able to find any documentation or examples using a custom modifier file on the github. Thanks!

2

Modification of the system can be done via this action by filling out a SECardiovascularMechanicsModifiers object in the action, or a filename of a file containing the json of this object.

While we do provide a method to serialize that object to its protobuf binding object, we don’t seem to have the 2 methods to turn that binding object to a string, then to a file. You could easily write those based on these 2 methods on the SEPatient

Then when you can create modifier objects and serialize those to file, and refer to those file paths in the action instead.

We have not really tested the limits of the modifiers, this functionality is still a work in progress.
We have tested modification from 0.5 to 2.0 here

The file based modifiers has not been tested either, but the code seems to be there…

3

Thank you for replying! As a clarification, I want to add a new type of modification to the set of available modifications, and am wondering how deep into pulse I need to go to implement that?

My current thoughts are to:

  1. Add a “has_CPP_modifier” and “get_CPP_modifier” to physiology.py
  2. Modify my python script to set the value of my CPP modifier.
  3. Modify CardiovascularModel.cpp after line 1238 to check for any modifiers and set our value appropriately

Before I went fully into the weeds on the model, I figured I should check if there are other modifications that will need to be made to pulse deeper in the code or if that approach is solid.

4

In order to support all the interaction between various coding laguages, we use Protobuf as the schema definition language for our data model.

So you would:

  1. Modify the schema object
  2. Update the C++ Header and Class as well as its binding translation to and from methods
  3. Update the python class and its binding translation to
  4. (Update Java and C#, but we can skip those for now)
  5. Use m_MechanicsModifiers with your new property where you need to in CardiovascularModel
5

Thanks!

6

Between 1 and 2, you should manually regenerate the protobuf bindings using the run command

run protoc

Look for any errors…