MueFest notes

MueLu output:

• introduce json/yaml output layer for hierarchical (database-like) output for timers
• use functionality from Teuchos timers?
• unified scientific output format for Teuchos timers (Andrey might have a patch)
• reorganize verbosity levels (based on use-case and role of developer/user...)

Priority: extremely low

MueLu performance:

• wait for data analysis of James performance runs
• wait for Tobias checkin in his improved Kokkosified versions of TentativePFactory and CoalesceDropFactory

Gold files:

• Problem: refresh gold files using a simple shell script (instead of doing it by hand)
• add logic to Chris' script to check whether all tests are enabled and run in all necessary configurations

Nightly tests

• standardize naming conventions (following the scheme of the ASCIC machines)
• wait for Chris sending out an email with the naming scheme. Machine owners (geminga, enigma,...) will update the test namings for the tests running on their machines

Developer's guide

Congratulations: you found it. Please use rst to add your stuff

Repository organization

• Move research folder to a team-wide separate repository (e.g. living on software.sandia.gov)
• Meant for research done by coworkers and students.
• Meant for stuff which is not supposed to be immediately visible to the rest of the world
• treat it as an external repository (similar to what drekar is doing for the Research repository)
• Chris prefers local branches.

Reorganize/move some files in the MueLu repository

• e.g., the RAPFactory should be in MueCentral (instead of Misc)
• Jonathan has a list of some classes that should live in a different place