... | ... | @@ -2,43 +2,17 @@ |
|
|
|
|
|
This is the wiki associated with the [ExaHyPE gitlab project at LRZ](https://gitlab.lrz.de/exahype/ExaHyPE-Engine). It consists of pages written in the [Gitlab flavoured Markdown format](https://github.com/gitlabhq/gitlabhq/blob/master/doc/user/markdown.md) and can be offline [accessed and edited as a git repository](https://gitlab.lrz.de/exahype/ExaHyPE-Engine/wikis/git_access). See the [page index](https://gitlab.lrz.de/exahype/ExaHyPE-Engine/wikis/pages) for a list of all available pages.
|
|
|
|
|
|
## Resources, technical infrastructure, work progress
|
|
|
- The different systems we operate can be found at the [infrastructure](infrastructure) page.
|
|
|
- The wiki page [git branches](git branches) explains how we use git.
|
|
|
- There is an extensive tutorial how to do the [Eclipse import](Eclipse_import) in order to use the powerful IDE. See also how to [import ExaHyPE guidebook as Eclipse TeX project](eclipse_import_texlipse).
|
|
|
- There is a guide how to get [supermuc internet access](supermuc internet access) e.g. in order to clone the ExaHyPE code repository at [SuperMUC](https://www.lrz.de/services/compute/supermuc/)
|
|
|
- The 8-page [review about the Aug 2016 state of the Code Generation in ExaHyPE](/uploads/5434126726600fa20b5a73a2865f5222/report.pdf) ([CodeGen.zip](/uploads/111dbabbb33f1807f48fe8ee92b1bc20/CodeGen.zip))
|
|
|
- Dominic's [nine months review report](/uploads/032a4422709d0a9dab5976053d5bb1af/nmr_charrier.pdf) gives an overview of some of the algorithms we use in ExaHyPE . Note that the AMR part is a little outdated already. There are further errors in the space-time predictor computation.
|
|
|
- Svens [list of benchmarks](list of benchmarks) that we currently have.
|
|
|
- A number of documentations have been uploaded at the [projectplace document platform](https://service.projectplace.com/pp/pp.cgi/0/1137110372?op=wget#/tab_docs), look for *deliverables* and *reporting*.
|
|
|
- We started a guide on how to translate PDE kernels written in [Fortran to C/C++](fortran_to_c).
|
|
|
- Guides how to use [ExaHyPE on Windows](windows) or [ExaHyPE on Mac OS X](mac) (Macbooks, iMacs). Also [Clang compiler](https://gitlab.lrz.de/exahype/ExaHyPE-Engine/issues) works.
|
|
|
- How to [compile and use the Trento research/example code for ADERDG](TrentoFortranCode), especially with the *Tecplot* dependency.
|
|
|
- How to do [Convergence Studies](Convergence Studies) with the framework.
|
|
|
- ExaHyPE [Application Reference architecture](ARA) draft
|
|
|
- A [list of papers](papers) as reference to the methods.
|
|
|
- We have a number of [videos](videos) about ExaHyPE at various places.
|
|
|
- There are vast definitions of the [exahype VTK output file format](fileformats) collected at this wiki.
|
|
|
- We have topics on [C++ code style and compilation times](code-style-and-compilation) at the wiki.
|
|
|
- The story of the [User Solver API](User Solver API)
|
|
|
- How to run benchmarks on different [supercomputers]
|
|
|
(run-benchmarks-on-supercomputers)
|
|
|
- A [Supercomputing @ Durham Hamilton Quick Start Guide](/uploads/e9a2e9d1c2ef655c33c5940c08df6987/cookbook_1_.pdf) by Tobias, [updated with DDT debugging infos](/uploads/db566999bc67fe6e0d5e0e8315a38622/cookbook_2_.pdf)
|
|
|
- [How to do debugging](howto-debug-mpi), especially parallel debugging (MPI)
|
|
|
- [How to use Intel VTune](vtune) for profiling
|
|
|
- [How to use Intel's tracing tools](Intel-Tracing-Tools)
|
|
|
- [Rationale: New ExaHyPE Toolkit](new-toolkit)
|
|
|
|
|
|
Add your guides and texts to this list by creating a new page and adding it to this list. Thus we build up a knowledge base similar to the [Peano cookbook](http://www5.in.tum.de/exahype/peano/cookbook.pdf) or the [ExaHyPE Guidebook](http://www5.in.tum.de/exahype/guidebook.pdf).
|
|
|
## Resources, technical infrastructure, user guides
|
|
|
[Introductory Guide](Intro)
|
|
|
[ExaHyPE Guidebook](http://www5.in.tum.de/exahype/guidebook.pdf)
|
|
|
[Peano cookbook](http://www5.in.tum.de/exahype/peano/cookbook.pdf)
|
|
|
|
|
|
## Communication
|
|
|
- There are annual or biannual long meetings where all developers come together at one place, called **coding days**. Documentation about these meetings is at the wiki page [Codingdays](Codingdays).
|
|
|
- We do a weekly developer meeting using Google Hangouts, called **Jour Fixe**. All jour fixes are documented in the wiki by Vasco with both a prepraratory agenda as well as minutes after the meeting. You can join our weekly reused [group channel](https://hangouts.google.com/call/5aow2vstsnef5ik3pryhupdefme).
|
|
|
- We do a weekly developer meeting using Google Hangouts, called **Jour Fixe**.
|
|
|
- We test Slack for team communication. Join https://exahype-dev.slack.com/ to explore. You can install an App on your tablet or mobile phone to stay in touch. Currently there are already ~ 7 members.
|
|
|
- Don't forget to subscribe the [mailing list](https://lists.lrz.de/mailman/listinfo/exahype). The [list archives](https://lists.lrz.de/mailman/private/exahype/) are a comprehensive documentation of problems and their solutions.
|
|
|
|
|
|
The [jourfixe](jourfixe) takes place every **Thursday, 16:00 CET** (== 15:00 @DUR).
|
|
|
|
|
|
<img src="/uploads/248b21d82ceb618e9c52b58b87b56646/exahype_jour_fixe_hangouts.jpg" width="300" class="right">
|
|
|
|
|
|
This is how our jour fixes look like. It's lot's of fun!
|
... | ... | |