diff --git a/developer_guide.html b/developer_guide.html index 5f30e1b8..bdd63b42 100644 --- a/developer_guide.html +++ b/developer_guide.html @@ -120,10 +120,14 @@ Architecture

svZeroDSolver is written in a highly modular manner to enable reuse of code for many different applications. It is divided into a header based library in the src directory and a collection of different applications in the applications folder. Each application is written for a different use-case of svZeroDSolver, namely:

+

Architecture for svZeroDVisualization.

+

Architecture for svZeroDGUI.

Build in debug mode

For debug purposes it is recommended to build svZeroDSolver in Debug mode.

diff --git a/index.html b/index.html index 5c79f475..103ce8c2 100644 --- a/index.html +++ b/index.html @@ -151,10 +151,10 @@

Using pip

Building on Sherlock

-
module load cmake/3.23.1 gcc/12.1.0 binutils/2.38
+
module load cmake/3.23.1 gcc/14.2.0 binutils/2.38
mkdir Release
cd Release
-
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_COMPILER=/share/software/user/open/gcc/12.1.0/bin/g++ -DCMAKE_C_COMPILER=/share/software/user/open/gcc/12.1.0/bin/gcc ..
+
cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_COMPILER=/share/software/user/open/gcc/14.2.0/bin/g++ -DCMAKE_C_COMPILER=/share/software/user/open/gcc/14.2.0/bin/gcc ..
cmake --build .

@@ -352,7 +352,7 @@

Boundary conditions

Pv: Venous pressure

The above table describes the most commonly used boundary conditions. In addition, svZeroDSolver includes various closed-loop boundary conditions. Examples can be found in svZeroDSolver/tests/cases.

-

Note that the FLOW and PRESSURE boundary conditions accept mathematical expressions in bc_values. For example, values of the boundary condition can be specified as a function of time as follow:

{
+

Values of the boundary condition can be specified as a function of time as follow:

{
"bc_name": "INFLOW", # Name of the boundary condition
"bc_type": "FLOW", # Type of the boundary condition
"bc_values": {
@@ -361,16 +361,8 @@

Boundary conditions

}
},

See svZeroDSolver/tests/cases/pulsatileFlow_R_RCR.json for an example.

-

They can also be specified as a mathematica expression as follow:

{
-
"bc_name": "INFLOW", # Name of the boundary condition
-
"bc_type": "FLOW", # Type of the boundary condition
-
"bc_values": {
-
"fn": "2.0 * (4*atan(1.)) * cos(2.0 * (4*atan(1.)) * t)"
-
}
-
},
-

For an example with a mathematical expression for the boundary condition, see svZeroDSolver/tests/cases/timeDep_Flow.json.

Simulation Outputs

-

The siumulation outputs will be saved in the specified CSV file (<name_of_output_file>.csv) when running svZeroDSolver from the command line as follows:

svzerodsolver <name_of_configuration_file>.json <name_of_output_file>.csv
+

The simulation outputs will be saved in the specified CSV file (<name_of_output_file>.csv) when running svZeroDSolver from the command line as follows:

svzerodsolver <name_of_configuration_file>.json <name_of_output_file>.csv

If the name of the CSV file is not specified, the default is output.csv. The format of the file depends on the user-specified configuration within the simulation_parameters block of the JSON configuration file.

If output_variable_based is set to true, the CSV file will contain all the degrees-of-freedom in the simulation. Otherwise, only the flow and pressure at the inlets and outlets of vessels is written.

The degrees-of-freedom (DOFs) follow the following naming scheme: