Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
engine
engine
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pulse Physiology Suite
  • engineengine
  • Wiki
  • Creating a Scenario

Last edited by Rachel Clipp Aug 14, 2020
Page history

Creating a Scenario

We use scenario files to test models and use cases for Pulse. We create at least one scenario per action/condition. Some of our scenarios test a full range of severities and some test an injury and a treatment (multiple actions). It is important to create scenarios for any new functionality and add them to the Test Suite.

Creating a Scenario

All scenarios can be found in the 'data\human\adult\scenarios' directory. A detailed description of all of the scenario components can be found at Scenario File.

When setting up your scenario(s), think about testing the breadth of functionality. For example, test the range of your condition; activate and deactivate your action, test the range of your action; and add treatment to your action or condition if relevant. You may need multiple scenarios to test all of this functionality.

Executing Scenarios

There are two options for executing scenarios and viewing the results. You can use the Pulse Scenario Driver or the Test Suite.

The Pulse Scenario Driver is good for intial debugging as it is inside the development environment. See the Pulse Scenario Driver page for instructions on set up and use.

However, adding and executing your scenario(s) through the Test Suite is preferable as you will automatically generate plots and can compare you previous results. See the Test Suite page for instructions on adding and executing your scenario.

Adding Scenarios to the Test Suite

After you have completed your testing, you will want to add your scenario to the Test Suite to ensure it is part of the nightly verification testing. See the Test Suite for instructions on adding your scenario(s) to the full scenario list.

Clone repository
  • Adding a Parameter
  • Contributing to Pulse
  • Creating a Scenario
  • Creating a Unit Test
  • Creating a condition
  • Creating an Action
  • Extending a System
  • Generating Documentation
  • Modifying a System Circuit
  • Pulse Scenario Driver
  • Test Suite
  • Updating Baselines
  • Updating Documentation
  • Using C#
  • Using CLion
View All Pages