Scientific Libraries: Difference between revisions
From Modelado Foundation
imported>Milind No edit summary |
imported>Schulzm (added PIPER) |
||
| Line 26: | Line 26: | ||
|(CORVETTE) | |(CORVETTE) | ||
|SLEEC | |SLEEC | ||
| | |Support optimization efforts with tools that can capture some of the internal semantics of a given library | ||
|- 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.'' | ||
| Line 38: | Line 38: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |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 | ||
|- 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.'' | ||
| Line 50: | Line 50: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
| | |N/A | ||
|- 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?'' | ||
| Line 62: | Line 62: | ||
|(CORVETTE) | |(CORVETTE) | ||
|N/A | |N/A | ||
|( | |Attribution information about internal data structures (e.g., phases, data distributions, patch information for AMR) | ||
|} | |} | ||
Revision as of 05:33, May 1, 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 | (EXPRESS) | (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 |
| 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. | (EXPRESS) | (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 |
| 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. | (EXPRESS) | (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? | (EXPRESS) | (TG) | (DEGAS) | (D-TEC) | (DynAX) | (X-TUNE) | (GVR) | (CORVETTE) | N/A | Attribution information about internal data structures (e.g., phases, data distributions, patch information for AMR) |