Given by Geoffrey C. Fox at Second Pasadena Workshop on HPCC Software on January 10-11,1995. Foils prepared January 21,1995
Abstract * Foil Index for this file
We discussed 12 application areas -- "vignettes" -- of which 3 -- all from industry -- are contained in final short report
|
We discussed at length the impact of "non-technical" issues such as setting up:
|
These non-technical issues lead to technical points which ensure a better more predictable HPCC software development environment |
This table of Contents
Abstract
Chair: Geoffrey Fox |
Co-Chair: Andy White |
Secretary: Ken Hawick |
January 10-12,1995 Pasadena |
We discussed 12 application areas -- "vignettes" -- of which 3 -- all from industry -- are contained in final short report
|
We discussed at length the impact of "non-technical" issues such as setting up:
|
These non-technical issues lead to technical points which ensure a better more predictable HPCC software development environment |
Non-technical Characteristics of broad significance such as academia vs industry, and/or |
Technical characteristics of specific applications (regular vs irregular) |
Identified several specific technical issues |
Coupled to "broad non-technical issues" identified in Question 2.1. |
1) need for better debuggers, profilers, performance monitoring tools |
2) need for more stable operating systems |
3) need for tools to aid in code migration to parallel systems, whether it be in the form of libraries, or other software engineering tools. |
4) need to reduce the latencies due to system software |
5) need for looking at exciting and innovative applications areas, (to help the HPCC industry by stimulating new demands). This might involve very data intensive applications (in contradistinction to compute intensive ones) but also harder and more complex problems, irregular data structures and less obviously load balanceable problems. |
1) Viable base model: Build HPCC software on an internally viable base such as distributed computing or the WWW. |
2) Internally consistent model: areas where business case for HPCC is internally viable (eg decision support) |
3) Partnership model: Government supported teams collaborating with industry teams (eg oil and gas) |
4) Pulse/Seed support model: IGA teams to develop applications (eg Europort, IBM, TMC,...) |
5) Ongoing support model: of areas of national importance, but without identified commercial markets (NSA, Weapons, QCD) |
6) Dual benefit model: Government market bootstraps viable commercial market or vice versa. |
Categories are not rigid but (six) approximately defined regions in complex multidimensional space (they could be merged or overlapped). Different application areas have different investment strategies |
Different applications have a different mix of metrics such as:
|
Need to involve a larger group of non HPCC communities |
For instance, most of the messages on networks are
|
But MPI standrards set internally to HPCC and did not explicitly involve ATM/Internet community/standard processes |
HPF focusses on regular multidimensional arrays in an excellent standards forum that ignores
|
Need HPVRML and a broader community |
NASTRAN |
Real-time embedded systems |
Aerospace manufacturing |
Crisis management |
Nuclear Weapons |
Environmental Modeling |
Mission to Planet Earth |
Data Intensive Applications |
High end CFD |
Centric |
Computational Chemistry |
QCD |
Currently the tail is wagging the dog - the BIG dog? |
What is the market area that is big enough upon which to base viable HPCC standards (eg SMP, distributed systems or WWW)? |
What are the top three standards? |
Industry/market application driven |
Tools and tools funding which are implied by viable enterprise models |
Viable base and Pulse/Seed funding enterprise models appear to be high priority |
Low latency (eg real-time) |
design and manufacturing |
data intensive (eg crisis management) |
business |
event-driven modeling and simulation |