1. Virtual Parallel Languages and Environments
    1. Geoffrey Fox NPAC
    2. Andrew Sherman SCA
    3. Cal Rbbens Virginia Tech
    4. Manish Parashar Texas
  2. Sherman SCA -I
    1. *Agrees with my analysis and goals with different technology
    2. *Virtual Shared Memory very good for PSE
    3. *Store data so greater than one process can examine at same time -- enables computational steering and monitoring simultaneously
    Sherman SCA -II
    1. *Khoros-Paradise System for Navy -- Khoros natural as Navy interested in signal processing
    2. *Paradise replaces transport mechanism in Khoros and you have virtual shared memory -- not file -- between modules
    3. *Piranha does scheduling of different modules including replication of the different stateless(often true) Khoros modules
    4. *This enables parallel Khoros
  3. Parashar -- Black Hole
    1. *Process involved complex cycle between CS and application scientists to identify requirements
    2. *Merged multipole, black hole and FEM technologies
    3. *DAGH Technologies for parallel adaptive hierarchical AMR implemented in C++
    4. *Has shadow grid hierarchy for on the fly error estimaion
    5. *Good performance compared to hand coded software
    6. *C++ driver calls Fortran routines in coarse grain model
  4. Ribbens
    1. *Was in ELLPACK project at Purdue -- a user not developer of languages
    2. *Works with engineers at Virginia Tech
    3. *There is no holy grail language or paradigm
    4. *Some sacrifice in raw performance possible
    5. *MDO codes need shell scripts/wrappers
  5. Ribbens
    1. *Compares with Pasadena1 workshop
      1. -likes HPF and MPI forum process
      2. -Not clear if good progress in tools
      3. -What about process of building "advanced prototype"
    2. *Is there a PSE forum -- is problem well defined
    3. *Sems to agree Web is a reasonable starting point
    4. *Agrees that AVS is a good model and in general visual programming environment
    5. *What is a VPE (Virtual Parallel Environment)
    6. *How important/useful is:
      1. -visual programming
      2. -shared address space
      3. -a template
      4. -existing code re-use -- one trusts existing code!
  6. Questions from Audience -- I
    1. *Why shared memory in Sherman's example
      1. -User sees conventional Khoros
      2. -Systems uses shared memory
    2. *Ribbens says shared memory supports incrementalism
    3. *Only developers or expert users will address closely coupled applications
    4. *Skjellum -- Java linked to MPI -- abandon PERL
  7. Questions from Audience -- II
    1. *Do we agree on division between coarse grain and fine grain parallelism
    2. *AVS/Khoros checks if modules should be connected
    3. *Is set of modules the correct model!
      1. -Smith says no -- do top down -- he seems to be very puristic as current modules "artificial" -- I don't agree!
      2. -rather mix top down and bottom up approaches
    4. *PDE's solvers are clearly used cf. NASTRAN but PSE"S are not taking world by storm
    5. *Typical discussion of interdisciplinary research with industry, computer science -- application interaction, computational scien