next up previous
Next: G: Technical Rationale and Up: Section II : Detailed Previous: Syracuse

F: Cost, Schedule and Milestones

Year 1:

Initial development and formal specification of Hierarchical High Level Application Modeling Framework (HLAM).

Initial definition of PetaSIM and the delineation of the relationship between PetaSIM and HLAM. Construction of first HLAM and PetaSIM prototypes.

Initial versions of data fusion and adaptive application emulators. These first emulators will emulate only a single irregular or data parallel application. The adaptive application emulator will focus on emulation of unstructured mesh and particle codes. The data fusion application emulator will emulate processing and I/O associated with data exploration.

Year 2:

A variety of HLAM representations at different levels of granularity will be generated for both application emulators. Initial performance predictions will be carried out. Results will be validated on current multiprocessor architecture using detailed simulation techniques.

Application emulators extended to represent coupled applications running on network-connected collections of multiprocessors.

Application emulator performance validated through comparison with performance of real applications.

Year 3:

HLAM representations generated for application emulators running on network-connected collections of multiprocessors.

Irregular problem aggregation routines incorporated into HLAM/PetaSIM software environment.

Irregular adaptive application emulators extended to represent coupled adaptive unstructured mesh codes, integro-differential equations solvers and particle codes. Data fusion application emulators extended to emulate multiple coupled applications that carry out image segmentation, image registration and compositing.

Options:

Year 1:

The irregular scientific application emulator will be extended to simulate behavior of Monte Carlo, multipole and structured adaptive codes.

Year 2:

The data fusion application emulator will be extended to take tertiary storage into account.

PetaSIM support added for additional collective data movement primitives, which will increase the range of multi-phase loosely synchronous problems handled.

Begin development of optimized parallel implementation of PetaSIM.

Year 3:

PetaSIM cost function will be extended to take tertiary storage into account; results validated using virtual microscope application.

Development of runtime/compile time techniques that support semi-automatic generation of HLAM/PetaSIM aggregates and modules.

Optimized parallel implementation of PetaSIM.


next up previous
Next: G: Technical Rationale and Up: Section II : Detailed Previous: Syracuse

Wes Stevens
Fri Jul 11 15:07:44 EDT 1997