Our latest deployment is still in a beta phase, and is intended to be an intermediate release to showcase the capabilities of the BioGears® Physiology Engine. The current version of the software includes examples of all types of engine interfaces, but does not include all of the functionality or physiologic systems that will be present in the final product. This version of the software is meant to elicit feedback and enhance community involvement in establishing end product expectations.
Release Notes 6.2.0
The latest deployment includes the following notable updates:
- General bug fixes, system improvements, and tools/solver improvements
- Intoxication model for Morphine
- Effects site concentration to allow for delayed PD reactions
- Central nervous modifier to model depressed feedback mechanisms
- Noloxone reversal agent model
- New Hemorrhage model
- MCIS support for combat injury coding
- Location and severity can be flagged through MCIS
- Resistance paths handle bleed out to simulate more realistic flow behavior
- Glucagon hormone
- New nutrient kinetics model
- New metabolic production and consumption method
- Protein storage and release model (amino acids in muscle)
- Fat storage and release model
- Interactions with the Hepatic system
- New Hepatic system
- Maintains blood glucose from other substances like lactate through new gluconeogenesis method
- Lipogenesis method generates triacylglycerol due to excess glucose and amino acid
- Glycogenesis and glycogenolysis to maintain blood glucose levels
- Updated exercise model
- Coupled to nutrient kinetic handling and metabolic need
- Updated diffusion method
- New Gastrointestinal model
- Enzyme kinetics determine digestion of nutrients
- Absorption facilitated through sodium co-transporter
- Gastric secretion function allows for bile formation in chyme
- Desflurane update and fix
(Interested in a previous Version?)
The following are known issues with the current version of the software:
- Lack of a full sympathetic/parasympathetic nervous system
- Extravascular fluid exchange model is incomplete
- Peripheral resistance currently does not scale with core temperature
- Only tested a simulation up to 24 hours in length (No Sleep model)
- The Java GUI (Toolkit) doesn't support the RenalSystemValidation scenario
We are developing BioGears with various user groups in mind. We provide design decisions and functionality in several deployment packages to cater to each user group.
The packages listed below are available for Windows, Mac, and Ubuntu Linux. We recommend at least 1 GB of RAM for all downloads.
The BioGears library (run via the console executable) has a process footprint of approximately 15 MB.
The BioGears GUI and graphing scripts can run up to 512 MB of process memory due to the Java Virtual Machine (JVM) and graphing large amounts of data.
We created a software development kit (SDK) to help developers integrate the BioGears Engine into software applications. This SDK provides pre-built libraries and headers, as well as examples of programmatically using the provided interfaces. The provided application programming interfaces (APIs) provide full control over the engine to execute various actions and retrieve a wide range of calculated physiological outputs
The SDK unzips around 200 MB of files. Dynamic execution of the engine does not produce any files.
The Software Development Kit provides details of the interfaces and how to use them.
The full BioGears source code is available for users to view and review implementation, contribute improvements, and integrate or replace models for use with the BioGears systems.
The source unzips around 350 MB of files. We recommend having at least 5 GB of disk space dedicated to building BioGears. The Source Code contains all code, scripts, data, and documentation to rebuild BioGears.
We include scenarios and baselined results used for verification and validation. As changes are implemented in the code base, doing a comparison after making modifications shows how changes to the scenario files or code itself manifests in BioGears system data. This data is used extensively to validate each system individually, as well as the combined effects of insults and interventions—see the Methodology Reports for more details. The scenarios output requests match the columns in the results file; we recommend that you do not modify these scenarios.
The complete data set unzips around 2 GB of files. Execution of all scenarios provided can generate up to 20 GB of results data.