This was a summary of some conclusions of a workshop at Purdue Sept. 25-27,1995 and presented at ARPA PI meeting at San Antonio, February 14,1996
|
The recommendations fall into three broad areas:
|
Basic Research in Architecture of and Technologies for Problem Solving Environments
-
These are both PSE components and the technologies/methodologies to build PSE's
|
Promotion of Interactions between academic, commercial, government computer science and user communities
|
Construction of (rapid) prototypes of "complete" (useable) PSE's for defense applications
|
This was a summary of some conclusions of a workshop at Purdue Sept. 25-27,1995 and presented at ARPA PI meeting at San Antonio, February 14,1996
|
The recommendations fall into three broad areas:
|
Basic Research in Architecture of and Technologies for Problem Solving Environments
-
These are both PSE components and the technologies/methodologies to build PSE's
|
Promotion of Interactions between academic, commercial, government computer science and user communities
|
Construction of (rapid) prototypes of "complete" (useable) PSE's for defense applications
|
Computational Geometry and Grid generation
|
Collaborative Computing linked to configuration controlled databases with humans and computers in the loop
|
Multi-level object technology for reusable, maintainable, robust software which is performance portable -- focus on complete PSE and not just computational kernels
|
Mechanisms for validating correctness of numerical code
|
Metacomputing -- PSE's are naturally set up as cross-country (institution) distributed computing systems
|
Wrapper technology for legacy Systems (Rockwell tells me next DoD aircraft needs 10,000 separate programs to be run!)
|
Large scale knowledge base systems for particular domains -- real engineers must use these PSE's
|
As well as normal scalable algorithms, software, filesystems, databases etc.
|
Many researchers (e.g. Grand Challenge collaborations) are developing independently what are essentially PSE's for physics, chemistry, engineering ....
-
Most do not know they are developing a PSE and that by using such a framework, they could (re)use work of others.
|
Need to gather these communities -- academia, government, industry, computer technology, application development -- together to establish framework for development of standards, exchange experiences (what works and what doesn't) and requirements
|
This discussion should include libraries, interfaces, data-structures, representation, middleware and PSE components
|
Of course all this basic research needs to be tested and evaluated!
|
We should create some complete scientific and/or engineering prototype PSE's
|
This should be multi-disciplinary on both computer technology side (algorithms, software, user-interface, artificial intelligence, database, collaboration etc.) and on application side
|
Choose an area where PSE adds value to an established computational area rather than proposing a new solution
-
So we test PSE approach and not role of computation in a particular area
|
Set-up as microcosm of proposed general case with distributed loosely coupled development as well "entries" in key components
|