-
Notifications
You must be signed in to change notification settings - Fork 62
Home
justusc edited this page Nov 16, 2014
·
34 revisions
- 11/13/2014 - 11/14/2014 — MADNESS developers meeting at Argonne National Laboratory
- The MADNESS developers are meeting to discuss the current state of the code and plan the upcoming releases v0.10 and v0.11.
- 8/7/2014 - 8/8/2014 — MADNESS developers meeting at Stony Brook University
- The MADNESS developers are meeting to discuss the current state of the code and plan releases v0.10.
- 5/23/2014 — MADNESS has new maintainers!
- The new maintainers (though not new to MADNESS) are:
- Justus Calvin — world
- Edward Valeev — tensor
- Scott Thornton — mra and chem
- Florian Bischoff — mra and chem
- 5/23/2014 — MADNESS is moving to GitHub
- The MADNESS group has decided to join the wonderful community of software developers on GitHub. The final transition will take place on 5/30/2014.
- 5/23/2014 — MADNESS Hack-a-thon
- At the MADNESS hack-a-thon we discussed various code related issues, contemplated the move to GitHub, and choose new maintainers.
- C++ compiler with C++11. Supported compilers:
- Linux x86_64 — GCC 4.8.3+, GCC 4.9.1, Intel 14.x, and Intel 15.x
- OS X — clang 6.x
- BG/Q — GCC 4.7.2, clang 3.5 (maybe?)
- MPI-2 or later
- BLAS and LAPACK
- GNU Autotools
- autoconf 2.59 or later
- automake 1.11 or later
- git
- libxc
- MADxc
- TBB
- Elemental 0.84 and later
- Gperftools (recommended on Linux; do not use on OS X)
- Google Test
- Doxygen
- pkg-config
- Eigen 3 (deprecated)
- Coding Conventions
- Recommended software stack
- Doxygen
- Debugging Strategies
- How to write and use an automakefile in MADNESS
- Adding new sub-directories
- Task Profiler
- Move Semantics
- Tau Performance Analysis
- Contributors, developers and participants
- Developer Activities
- learncpp.com
- cplusplus.com
- cppreference.com
- A concise guide to intermediate C++ design from Google
- Professional C++
- summary MADNESS related mailing lists
Presently there is only one such list that is intended for internal use by developers. The list of members and message content are both private. At the group homepage new members can be sent an invitation to join by any current member (though I think that one of Robert, George or Scott must approve). The list is unmoderated.
As soon as we have users who are not developers we should add a user mailing list.