NinJo Project Status June 2004 DWD. NinJo Project Status. The NinJo Team at the last team meeting. Status of Software Development

(1)

DWD

NinJo

Project Status

June 2004

NinJo

Project Status

June 2004

DWD

The NinJo Team at the last team meeting

The

The NinJo

NinJo Team at the last team meeting

Team at the last team meeting

DWD

NinJo Project Status

Overview

NinJo

NinJo Project Status

Project Status

Overview Overview

Status of Software Development

User Input

Layers

Diagram based applications

Servers

Batch

Hard- and Software-Benchmarks

NinJo Hardware and Java VMs

Release Planning

Features and Versions

Training and Roll-Out

DWD

Typical software development cycle consists in

Writing and reviewing Requirement specs

( and Design Documents of course )

User Evaluation

User Evaluation Meeting after each major NinJo

release

0.7 ( December 2003), 0.8 ( May 2004), 0.9

(September 2004 )

Results of Eval-Meeting are integrated in the

release planning

User input mainly on usability and features

Status of Software Development

User Input

Status of Software Development

User Input User Input

DWD

Status of Software Development

User Input: Enhancing the usability

Status of Software Development

User Input:

User Input:Enhancing the usabilityEnhancing the usability

We tried to integrate most of the user requests

e.g. Navigator

Fast Access to Use Cases

myGUI

Favorites

Spinner-Buttons ( e.g. Grid-Layer: model / model-run, level )

Undo / Redo

DWD

Status of Software Development

User Input: Configuration

Status of Software Development

User Input:

User Input:ConfigurationConfiguration

In NinJo nearly everything is configurable!

The application itself

The workspace

The scenes

The attributes

Not all the parameters of the evaluation versions where properly configured

We had to establish a working group that

takes care of all the issues

provides color tables, plot models, isoline

(2)

DWD

Status of Software Development

Layers: Remember the client architecture

Status of Software Development

Layers:

Layers:Remember the client architectureRemember the client architecture

Layer Container Layer Container

DWD

MSC has created it’s first layer!

Status of Software Development

Layers: Radar Layer

Status of Software Development

Layers: Radar Layer Layers: Radar Layer

But everything will be redesigned to allow for something like this

DWD

Status of Software Development

Layers: Radar, SCIT Layer

Status of Software Development

Layers: Radar, SCIT Layer Layers: Radar, SCIT Layer Display of storm cells

and their attributes

Currently DWD only

WebStart-able

Workshop on a generic layer shortly

DWD

Status of Software Development

Layers: Satellite Layer

Status of Software Development

Layers: Satellite Layer Layers: Satellite Layer Displays all satellites

User need not care about projection and satellite position

MSG integrated

Color composits available

Currently work on re-introducing mosaics and polar orbiting satellites in progress

DWD

Switzerland has created it’s first layer too!

Algorithms based on the work of B. Jobard ,

although completely rewritten in Java!

Streamlines: Switzerland

Status of Software Development

Layers: Streamline layer

Status of Software Development

Layers: Streamline layer Layers: Streamline layer

DWD

Application in a secondary window

The meteogram ist the first app to use the highly flexible diagram framework

Will be able to display observations and NWP data

Benny Koza will give a talk on the diagram framework

Status of Software Development

Diagrams: Meteograms

Status of Software Development

Diagrams:

(3)

DWD

Status of Software Development

Diagrams:

Diagrams:Aerological Aerological DiagramsDiagrams

Application in secondary window

First prototype shows that the diagram

framework can be adapted sucessfully

Both Observations and NWP-data

DWD

Status of Software Development

Diagrams:

Diagrams:Cross-Cross-SectionsSections

Secondary Window

Application in secondary window

Integrates many data types

NWV: Based on model or pressure levels

Radar: based on Volume scans

Obs: Temps and surface data

Currently NWV-only

DWD

Status of Software Development

Secondary Window Application: Instant 3D

Status of Software Development

Secondary Window Application: Instant 3D Secondary Window Application: Instant 3D

Instant 3D First prototype automated mapping of 2D-Paramaters in 3D-Scene Makes use of Unified-GOF (2D-scene graphs can be reused)

DWD

Status of Software Development

Layers:

Grib-Enhancements

Status of Software Development

Layers:

GribGrib--EnhancementsEnhancements

Transparency Intelligent Weather depiction New arrows Field cropping DWD

Status of Software Development

Applications: AP 2003

Status of Software Development

Applications: Applications: AP 2003AP 2003 AP2003 Supporting the weather forecast process Warning and monitoring Nowcasting Data modification

Point data based

Consolidated

forecasts

DWD

Status of Software Development

Batch Processing

Status of Software Development

Batch Processing

Image and vector products can be created

jpg, png, tiff...

PDF, FLASH, PS incl. Animations Flexible legend with

html-style language

SMS-based scheduling

Sophisticated layout and NinJo scheduler to come ( March 2004 )

Basis for application serving ( NinJo 1.0+)

(4)

DWD

NinJo Hardware Benchmarks

Goals of the Benchmark

NinJo

Hardware Benchmarks

Goals of the Benchmark

To provide benchmarks on which the decision

on the future NinJo client hardware can be based and to find the most suitable benchmark for the NinJo client hardware invitation to tender.

To compare the performance of the

NinJo-Client software on different platforms (Windows (Intel-Xeon), Windows (AMD-Opteron), MAC-OS X(G5), and Linux (Intel – XEON) )

To optimize the performance of the linux

servers.

To make sure that the planned amount of data

can be handled by the NinJo system

DWD

Server Benchmark Hardware

Fujitsu Siemens Primergy RX300

Suse Linux 9

2 x Intel Xeon 3,06 GHz,

4 GB memory

2 system disks Raid 1, 36 GB @ 15K each

4 data disks, 73 GB @ 15K each

Adaptec Raid Controller U320, 2Ch 2i/2e,

128MB

Sun or IBM JDK

DWD

Server Benchmark

Server Benchmark-

-

Results

Data Throughput during Import w. different Raids and

Data Throughput during Import w. different Raids and VMsVMs

NinJo-Linux-Server Performance 3,47 5,09 0,00 6,02 9,22 16,67 7,64 21,16 0,00 5,89 11,96 17,01 0,00 5,00 10,00 15,00 20,00 25,00

RAID 5 RAID 1 RAID 10 1 Import / SUN 2 Import / SUN 4 Import / SUN 1 Import / IBM 4 Import / IBM

RAID 0 1 Import 2 Import 4 Import

M B y te / s e c DWD 119 6,5 58,3 247,5 14,10 13,90 2591 1216 19,5 6,3 36,2 95,3 0,7 0,7 1345 730 66,5 21,5 115,0 365,0 1,5 2,0 14217 2392 0,1 1 10 100 1000 10000

Import Hofmüller LatLon Metadata Sounding Time Series

Time Volume

Volume

RAID10 / SUNRAID10 / IBMSUN MCH

Server Benchmark

Server Benchmark-

-

Results

Comparison DWD

Comparison DWD--Linux Linux Server versus Sun 480Server versus Sun 480

RAID 10 IBM with 4 import threads, SUN MCH import with 2 import threads

Server

Import Data retrieval client-server

Logarithmic scaling!

DWD

Client Benchmark Hardware

Fujitsu-Siemens Celsius R610,

2 * Xeon 3,2 GHz, 1MB cache

2GB RAM,

2 * 73 GB U320 SCSI disks @ 15 K, RAID 0,

NVIDIA FX 1000, 128 MB

Windows XP or Suse Linux 9.0

Apple G5 2 * G5 GHz, 2 GHz 2 GB RAM 1 * 160 GB, SATA @ 7.2K ATI Radeon 9800, 128 MB MAC OS X 10.3.

IBM Intellistation A pro

2 * Opteron 248, 2,2 GHz

3 GB RAM

1 * 36 GB SCSI disk, 1 * SATA data disk @ 7.2K

NVIDIA FX 1100, 128 MB Windows XP DWD

Client Benchmarks

9141 8188 12141 10703 12543 18043 14912 16884 16375 21266 24720 41634 142884 0 5000 10000 15000 20000 25000 30000 35000 40000 45000 50000 Opteron (IBM), WIN XP,

Java 1.4.2 Java 1.5ß Xeon ( Siemens), WIN XP,

Java 1.4.2 Java 1.5ß Xeon (Siemens), Linux, Java 1.4.2 , SUN Java 1.5ß , SUN Java, 1.4.1, IBM G5, (Apple), OS X Java 1.4.2

FavoritesNew Favorites with Graphik

(5)

DWD

Layer Based Client Benchmarks

Application Performance, Layer based

167 276 668 183 679 214 390 1077 227 871 706 430 996 310 942 1519 879 1712 831 1519 1015 687 7076 464 1497 0 500 1000 1500 2000

Georaster Geovector Pointdata Satellite Grid/Isoline

T im e i n m s

OPTERON XPXEON XP XEON LINUX, SUNXEON LINUX, IBMMAC G5

DWD

Release Planning

Milestones

Release Planning

Milestones Milestones Designphase Integration Architecture und Frameworks Prototyp 1 Requirement specs Version 0.3 Version 1.0 Framework-training Implementation Version 0.2 2000 I II III IV 2001 I II III IV 2002 I II III IV 2003 I II III IV 2004 I II III IV Version 0.6 Version 0.6 Version 0.5 Version 0.7 Version 0.8 Evaluation Evaluation Evaluation Version 0.4 Version 0.9 Evaluation DWD

Release Planning

Key Features Key Features

NinJo 1.0 ( late 2004 / early 2005 )

Animation ( Usable GUI and handling)

AutoMon ( Warning and Monitoring (AP 2003 )

Batch ( to be integrated in SMS, w/o soph. legends)

Capture ( Data snapshot for training and reports )

CrossSection ( Using Diagram Framework )

Graphical Editor (first version without data editing)

SCIT / KONRAD

Lightning

Meteogram

Radar ( perhaps no Cell View )

Satellite (incl. SAF + polar orbiting satellites )

Soundings DWD

Release Planning

Key Features 2 Key Features 2 NinJo 1.1 ( summer of 2005 ) Archive ( RDBMS access )

Batch ( automated legends )

Formulas

On Screen Analysis ( Field Modification )

Point Forecast Editing ( AP 2003: MMO )

Layers based on base point data layer

Road Weather Layer ( DWD: SWIS )

Storm Warning Layer ( DWD: Sturmwarn )

MOS Layer ( GMOS, TAF-Guidance )

Warning Layer ( AP 2003: EPM )

and further - requested - functionalities in all

layers DWD

Release Planning

Key Features 3 Key Features 3 NinJo 1.2 ( late 2005 ) 3D ( Instant 3D ) OOG ( AP 2003: Consolidated PTP ) Replay Trajectories

On Screen Analysis ( Field Modification, if

requested )

and further - requested - functionalities in all

layers

DWD

Release Planning

Training and Roll-Out

Release Planning

Training and Roll

Training and Roll-

-Out

Out

Training at DWD and MetInfoBw

Training the trainers ( July )

Forecaster training early September-mid October

System-Administrator training late January 2005,

early February 2005

First Clients will be installed for forecster training

Second batch of machines end of January

2005 including servers

Installation during February 2005

Parallel operation with MAP ( legacy