Given by Ken Flurchick (OSC) at ASC Gateway Project Review Wright Technology Network Dayton on July 22 99. Foils prepared Aug 21 99
Outside Index
Summary of Material
Overall Architecture and Linkage to Middle Tier |
Tasks are Entry, Problem Description, Code toolbox, Results Toolbox |
For each area, we give Tasks, Status and Plans |
Outside Index Summary of Material
Page 1 |
OSC |
PSE Development |
and |
The CCM-PSE |
Joint OSC / NPAC |
Page 2 |
Develop a PSE front end |
Develop the PSE-WebFlow Interface |
(with NPAC) |
Implement the PSE for CCM |
Project Goals |
PSE and WFS |
The PSE is the user view of the Gateway. |
The PSE transforms a science problem to requests for specific computational resources. |
The PSE-WFS interface is the translation of the users requests to access to resources. |
WFS contains user session information and site specific information. |
WFS provides communication to all other components of the middle tier (e.g. Globus, RIB, etc.) |
Page 3 |
Web Flow Server |
Input:Abstract Task |
Output:Resource Specification RSL |
WFS Task |
PSE-WFS Flow |
Page 4 |
Page 5 |
Tasks : Entry |
Entry (part of PSE-WFS interface) |
Requirements for entry |
Authentication, authorization, secure |
communication with middle tier. |
Direct access to middle tier services (e.g. file services) |
Restore state information from previous gateway |
session or updating session information |
Direct access to other components of the PSE |
Status : Entry |
Entry |
Requirements for entry |
WFS can process user login and return a |
user "Welcome Page" |
Current middle tier services include: |
exit from the Gateway |
file services |
a navigator for the PSE. |
State information includes user information and job |
information. Storage and retrieval of state information |
is under discussion, currently using XML files. |
The PSE navigator will link to PSE components. |
Page 6 |
Plans : Entry |
Entry |
PSE requirements for entry. Complete entry |
requirements and implementation by 8/31/99. |
A complete list of middle tier services to be specified |
by 9/1/99. |
State information will be specified by 8/15/99. |
Storage and retrieval of state information discussion is |
to be scheduled. |
The PSE navigator will link to PSE components. |
There are many technical issues to resolve. |
Target is 8/31/99. |
Page 7 |
Page 8 |
Tasks : Problem Description |
Problem Description |
PSE Problem Description |
Translate the scientific problem statement into a way to |
solve the problem. The common view is |
Property to compute |
System under study |
Methods(s) to solve the problem |
Provide the user a mechanism to enter this information |
(interactive pages, forms etc.) and storing this information. |
Tools to develop and maintain the domain specific |
mappings from problem to codes(s) which can solve the |
problem. |
Page 9 |
Status : Problem Description |
Problem Description |
PSE Problem Description |
Supporting material and discussions on methods, accuracy, and so |
on. Plus access to external information. Material for CCM exists |
and a general object description, XML translation and tools are being |
developed. |
A general mechanism to describe problems has been developed. It is |
implemented in XML and provides for a range of problem specific |
information including code and job information. The object is called |
the Problem Descriptor. |
A general mechanism to provide the mapping from problem to |
code(s) has been developed. This mapping contains domain specific |
resource specifications that need to be generalized. |
As the Problem to Code to Resources process is specified, tools to |
develop and maintain this information are being developed. The |
mappings are domain specific. |
Page 10 |
Plans : Problem Description |
Problem Description |
Tools to develop and maintain problem description supporting |
material will be specified and developed. This problem description |
material includes discussions on methods, accuracy, and so on. |
Initial object specification: 8/15/99, tools available: 9/15/99. |
The current framework of the Problem Descriptor needs to |
incorporate all the relevant scientific components and be |
extensible. 9/15/99 is a target for CCM and 9/30 for a compilation |
of discussions with other CTA's |
The problem to codes and code to resources process is under |
discussion. (TBD) |
Plans include the development of tools based on experience |
constructing the mappings above. (TBD) |
Page 11 |
Tasks : Code Toolbox |
Code Toolbox |
This toolbox generates input files. Each code will need a |
separate set of pages to develop the input. One component |
is to provide translators from one input format to another. |
Provide access to code documentation, input help and other |
information, such as documentation from a code author. |
This toolbox needs to generate the resource descriptor for |
the WFS. |
Status : Code Toolbox |
Code Toolbox |
A simple form for several CCM codes has been developed. |
Currently specifying the description of the toolbox to allow |
other PSE developers to incorporate other codes. |
Linking to external material from the WFS is under investigation. |
A framework for the resource specification has been developed. |
Page 12 |
Plans : Code Toolbox |
Code Toolbox |
The toolbox specification is available 8/31/99. And the CCM |
version is available 9/15/99. |
Linking to external material from the WFS is under investigation. |
A possible mechanism to support this is available 8/15/99. |
A general framework for the resource specification is available |
9/15/99. |
Page 13 |
Tasks : Results Toolbox |
Results Toolbox |
CTA specific analysis of the results. The immediate goal is to |
provide the user with sufficient information to determine that |
the job ran successfully. |
Provide access to tools for detailed analysis, such as code |
specific visualization or general visualization tools. |
Tools to develop and maintain analysis tools and links to |
external applications. |
Page 14 |
Status : Results Toolbox |
Results Toolbox |
CTA specific applications have been constructed. |
Interaction with WFS to provide access to the output files and |
archival mechanisms has begun. Specifications for the Result |
Descriptor is underway. |
No progress on general tools. |
Page 15 |
Plans : Results Toolbox |
Results Toolbox |
Specifications for the Result Descriptor is available 8/31/99. |
Design toolbox for adding analysis applications to the PSE. |
(TBD) |
Page 16 |
Page 16 |
Plans : Summary |
Page 17 |
Entry |
PSE requirements for entry. Complete entry requirements and implementation by 8/31/99. |
A complete list of middle tier services to be specified by 9/1/99. |
State information will be specified by 8/15/99. |
Storage and retrieval of state information discussion is to be scheduled. |
The PSE navigator will link to PSE components. There are many technical issues to resolve. Target is 8/31/99. |
Problem Description |
Tools to develop and maintain problem description supporting material. Initial object specification 8/15/99 and tools available 9/15/99. |
The current framework of the Problem Descriptor for CCM is available 9/15/99 and a compilation of discussions with other CTA's is available 9/30. |
The problem to codes and code to resources is under discussion. (TBD) |
The development of tools to provide the mappings above. (TBD) |
Plans : Summary |
Results |
Specifications for the Result Descriptor is available 8/31/99. |
Design toolbox for adding analysis applications to the PSE. (TBD) |
Page 18 |