Improve the interface to the svZeroDSolver

[ktbolt]

Use Case

The svFSIplus solver supports a callable interface to the lumped parameter network (LPN) solver.

Problem

Using the svZeroDSolver solver is activated with the

<Couple_to_svZeroD type="SI"> </Couple_to_svZeroD>

solver XML keyword using an ambiguous SI type name (silicon?).

The data needed to setup the svZeroDSolver is stored in a text file with hard-coded name svZeroD_interface.dat

interface library path:
../../../../svZeroDSolver/build/src/interface/libsvzero_interface.dylib

svZeroD input file:
svzerod_3Dcoupling.json

svZeroD external coupling block names to surface IDs (where surface IDs are from *.svpre file):
RCR_coupling 0

Initialize external coupling block flows:
0

External coupling block initial flows (one number is provided, it is applied to all coupling blocks):
0.0

Initialize external coupling block pressures:
1

External coupling block initial pressures (one number is provided, it is applied to all coupling blocks):
0.0

This file uses a custom a format.

Solution

1. It might be good to introduce a Coupling keyword that defines how boundary conditions are coupled.

2. The information needed to setup the svZeroDSolver should be defined using XML in the solver input file

<ZeroDSolver name="zd_semi_implicit_coupling">
  <Coupling_type> semi-implicit </Coupling_type>. 
  <Interface_library> svZeroDSolver/build/src/interface/libsvzero_interface.dylib <Interface_library>
  <Input_file> svzerod_3Dcoupling.json </Input_file>
  <Coupling_block>
     <Names_to_surface_ID> RCR_coupling 0 </Names_to_surface_ID>
     <Flows> 
       <Initialize> false </Initialize>
      </Flows> 
     <Pressure> 
        <Initialize> true </Initialize>
        <Value> 0.0 </Value>
      </Pressure> 
  </Coupling_block>
</ZeroDSolver>

This provides a uniform way to represent information.

Maybe add a Time_dependence_coupling keyword to remove the ambiguity of <Time_dependence> Coupling </Time_dependence>

   <Add_BC name="lumen_outlet" >
      <Type> Neu </Type>
      <Time_dependence_coupling>  zd_semi_implicit_coupling </Time_dependence_coupling>
   </Add_BC>

Alternatives considered

Do nothing.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines