Scientific Libraries: Difference between revisions
From Modelado Foundation
imported>Schulzm No edit summary |
imported>Rbbrigh No edit summary |
||
| Line 17: | Line 17: | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|''Describe how you expect to target (optimize/analyze) applications written using existing computational libraries'' | |''Describe how you expect to target (optimize/analyze) applications written using existing computational libraries'' | ||
| | |''Libraries written in MPI with C will run on XPRESS systems using UH libraries combined with ParalleX XPI/HPX interoperability interfaces. It is expected that future or important libraries will be developed employing new execution methods/interfaces'' | ||
|(TG) | |(TG) | ||
|(DEGAS) | |(DEGAS) | ||
| Line 29: | Line 29: | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|''Many computational libraries (e.g., Kokkos in Trilinos) provide support for managing data distribution and communication. Describe how your project targets applications that use such libraries.'' | |''Many computational libraries (e.g., Kokkos in Trilinos) provide support for managing data distribution and communication. Describe how your project targets applications that use such libraries.'' | ||
| | |''This issue is unresolved'' | ||
|(TG) | |(TG) | ||
|(DEGAS) | |(DEGAS) | ||
| Line 41: | Line 41: | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|''If your project aims to develop new programming models, describe any plans to integrate existing computational libraries into the model, or how you will transition applications written using such libraries to your model.'' | |''If your project aims to develop new programming models, describe any plans to integrate existing computational libraries into the model, or how you will transition applications written using such libraries to your model.'' | ||
| | |''Low-level system oriented libraries such as STDIO will be employed by the LXK and HPX systems among others. No scientific libraries per say will be built in the systems as intrinsics below the compiler level. Over time many libraries will be ported to the ParalleX model for dramatic improvements in efficiency and scalability.'' | ||
|(TG) | |(TG) | ||
|(DEGAS) | |(DEGAS) | ||
| Line 53: | Line 53: | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|''What sorts of properties (semantics of computation, information about data usage, etc.) would you find useful to your project if captured by computational libraries?'' | |''What sorts of properties (semantics of computation, information about data usage, etc.) would you find useful to your project if captured by computational libraries?'' | ||
| | |''Libraries crafted in a form that eliminated global barriers, worked on globally addressed objects, and exploited message driven computation would greatly facilitate the porting of conventional rigid models to future dynamic adaptive and scalable models such as the ParalleX based methods.'' | ||
|(TG) | |(TG) | ||
|(DEGAS) | |(DEGAS) | ||
Revision as of 19:54, May 7, 2014
Sonia requested that Milind Kulkarni initiate this page. For comments, please contact Milind.
| QUESTIONS | XPRESS | TG X-Stack | DEGAS | D-TEC | DynAX | X-TUNE | GVR | CORVETTE | SLEEC | PIPER |
|---|---|---|---|---|---|---|---|---|---|---|
| PI | Ron Brightwell | Shekhar Borkar | Katherine Yelick | Daniel Quinlan | Guang Gao | Mary Hall | Andrew Chien | Koushik Sen | Milind Kulkarni | Martin Schulz |
| Describe how you expect to target (optimize/analyze) applications written using existing computational libraries | Libraries written in MPI with C will run on XPRESS systems using UH libraries combined with ParalleX XPI/HPX interoperability interfaces. It is expected that future or important libraries will be developed employing new execution methods/interfaces | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | SLEEC | Support optimization efforts with tools that can capture some of the internal semantics of a given library (e.g., levels of multigrid V cycle or patches in an AMR library) |
| Many computational libraries (e.g., Kokkos in Trilinos) provide support for managing data distribution and communication. Describe how your project targets applications that use such libraries. | This issue is unresolved | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | PIPER will provide stack wide instrumentation to facilitate optimization - access to internal information only known to the library should be exported to tools through appropriate APIs (preferably through similar and interoperable APIs) |
| If your project aims to develop new programming models, describe any plans to integrate existing computational libraries into the model, or how you will transition applications written using such libraries to your model. | Low-level system oriented libraries such as STDIO will be employed by the LXK and HPX systems among others. No scientific libraries per say will be built in the systems as intrinsics below the compiler level. Over time many libraries will be ported to the ParalleX model for dramatic improvements in efficiency and scalability. | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | N/A |
| What sorts of properties (semantics of computation, information about data usage, etc.) would you find useful to your project if captured by computational libraries? | Libraries crafted in a form that eliminated global barriers, worked on globally addressed objects, and exploited message driven computation would greatly facilitate the porting of conventional rigid models to future dynamic adaptive and scalable models such as the ParalleX based methods. | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | Attribution information about internal data structures (e.g., data distributions, patch information for AMR) as well as phase/time slice information |