CS 351Introduction

Spring 2010

Modeling and Simulation

Technologies

Dr. Jim Holten

CSE 351

Overview

• Location: Cramer 227

• Time : MW 8:00 AM to 9:15 AM

• TAs: NONE

CSE 351

Contact

• Office Hours: Fidel Coffee shop

• Time : MW 9:15 AM to 10:15 AM

• E-mail: jholten@nmt.edu

• Other times and places as needed

CSE 351

Class Goals

• Understand model forms and types

• Build models and simulations

• Build “complex system” models

• Understand error propagation effects

CSE 351

More Goals

• Develop good software engineering habits

• Understand parallel model problems

• Understand ethical considerations

CSE 351

Build from Basics

• “Java” language, libraries, and GUIs

• Analysis tools

• Explore model representation alternatives

CSE 351

Good SoftwareEngineering Habits

• Adhere to listed requirements

• Follow coding standards

• Test adequately against requirements

• Maintain backups

CSE 351

Classwork• Participation -- 30%

• Quizzes -- 20%

• Homework -- 20%

• Tests --10% each, 30% for all

CS 351

Programming

• Java unless otherwise specified:

• Perl, C, or C++ may be specified.

• Other package usage may be specified as

needed.

CSE 351

Turn-in• Tarball of project directory (<dir>)

• <dir> is <name>_HW<number>

• tar -czvf <dir>.tgz

• Send package to: jholten@nmt.edu

CSE 351

Modeling and Simulation

• Why simulate?

• Simulator components

• Simulator technologies

CSE 351

Why Simulate?

• Predict behavior before building

• Predict for future expectations

• System characterization testing

• Pretend (virtual environments)

CSE 351

Before Building

• Prototypes are often cheaper than building

• Proof-of-concept

• Evaluate design trade-offs

• Sell concepts to others

CSE 351

Predicting the Future

• Weather forecasts, hurricane paths

• Stock market

• Satellite and asteroid orbits and changes

• Earthquakes

CSE 351

System Characterization

• Sensitivity analysis

• Accuracy determination

• Behavior familiarity

CSE 351

Virtual Environments

• Training tools

• Interactive controller

• Realism experience for system use

• Games

CSE 351

Simulation Components

• The model

• The environment – equipment, software

• Inputs – Initialization, updates

• Outputs – Numbers, plots, animations

CSE 351

Simulation Environment

• Computer hardware

• Operating system

• Programming language(s)

• Supporting tools

CSE 351

Simulation Model

• Environment states (variables)

• Internal states (variables)

• Time handling (scaled steps or events)

• State interpretations

CSE 351

Simulation Inputs

• Initial setup

– Environment variables

– Model variables, and

– Output specifications/selections

• During run (periodic and interactive)

CSE 351

Simulation Outputs

• All states (allows restarts)

• Snapshots of some states

• Statistics on model states and overall run

• Metadata – data about the data (units, etc)

CSE 351

Simulation Technologies

• Simulation environments

• Programming/modelling languages

• Model characteristics supported

CSE 351

Simulation Technologies

To be continued