|
|
| (One intermediate revision by the same user not shown) |
| Line 57: |
Line 57: |
| </div> | | </div> |
| </div> | | </div> |
| </div>
| |
|
| |
|
| <div id="misc-news" class="mainpage_row">
| |
| <div class="mainpage_box"> | | <div class="mainpage_box"> |
| <h3><span class="header_icon" aria-hidden="true" role="presentation">[[File:News.png|20px|middle]]</span><span> [[:Category:News|News]]</span></h3> | | <h3><span class="header_icon" aria-hidden="true" role="presentation">[[File:News.png|20px|middle]]</span><span> [[:Category:News|News]]</span></h3> |
| Line 81: |
Line 79: |
| </div> | | </div> |
| </div> | | </div> |
|
| |
| =About this Wiki=
| |
| This wiki presently serves to inform the development of a HiHAT framework in seven ways:
| |
| # [[Glossary and References]]
| |
| # [[Usage models]]
| |
| #* prosaic descriptions of how HiHAT would be used
| |
| #* Examples: static vs. dynamic, C++ features, task graph vs. imperative interfaces, multiple files vs. one source file
| |
| #* purpose: get a deeper appreciation of new usages, see commonalities and patterns across multiple usages
| |
| # [[User stories]]
| |
| #* formulaic, succinct and more rigorous descriptions of what is wanted out of HiHAT
| |
| #* As a <role>, I want <function> so that <benefit>, such that <acceptance criteria>
| |
| #* purpose: get more rigorous about what is needed
| |
| # [[Applications]]
| |
| #* Brief description of app and its business importance
| |
| #* Brief description of app domain
| |
| #* Qualitative or quantitative analysis of where and how it would benefit from HiHAT
| |
| #* Expected time table for delivery of a solution (e.g. readiness for the arrival of a new supercomputer at a USG lab), and resources available to implement it with HiHAT
| |
| #* purpose: identify apps that could lead vehicles that drive the development of an open source project and that would be a poster child that would build confidence for others to follow
| |
| # [[Runtime Clients]]
| |
| #* Language or tasking runtimes that are clients on top of the HiHAT user and common layers
| |
| #* Descriptions, key characteristics
| |
| # [[Implementation Modules]]
| |
| #* Implementations of HiHAT user and common layer functionality, provided by vendors or third parties
| |
| # [[Reference]]
| |
| #* pointers to other related work that could be of interest to this community that doesn't fit into the above categories
| |
|
| |
| Some key points about this wiki and what gets posted here
| |
| * All contributions of ideas and code examples here are considered public. There are no implied restrictions on the reuse of intellectual property or code, in open source or proprietary contexts.
| |
| * This is a community effort. It is expected that the whole community will benefit from the considerable efforts of many generous and conscientious people who are working for the common good. Thanks for your investment!
| |
|
| |
| For a HiHAT framework to be viable, it needs to support several targets, provide common building blocks, services and transformations in an open architecture, and enable a variety of different applications and frameworks to be built on top. The diagram below suggests one possible arrangement.
| |
|
| |
| [[File:HiHAT_Diagram.png|center|600px|caption="Possible HiHAT architecture"]]
| |
|
| |
| Please refer to the '''[[HiHAT SW Stack]]''' page for a discussion of how various SW components might interact.
| |
|
| |
| If the middle layers are modular, implementations can be created, plugged in, and iteratively refined. They may be freely shared or premium versions could be offered commercially.
| |
