View Source

Attention of:

Missing days

Conflicting events:

Plan

Spend a month to implement/improve/document features in MercuryDPM we all deem important
Dates: April 23- May 24, 2019
This can be topics particular to your research, but more improtantly general improvements.
We make a list of topics, everyone picks what he will work on (in groups, possibly).
We have daily meetings to discuss progress.
At the end of the month we release a new version of MercuryDPM.

Tasks:

Check what still needs to be done from last years list: MercuryMonth April 2018 and put into new list.
@all: if you have features that are needed, add them; ideally before next weeks meeting; who works on what can be decided later

What	Who	Priority	Comments
JIRA Jobs	All		Everyone who still has open JIRA jobs, finish them
oomph-lib coupling		ViPr + Mitchel	Define and implement an interface between MercuryDPM and oomphlib
Documentation		Thomas	Force laws: Add references, explanations to the force laws
	...		A lot of code needs documentation; this is a good place to start for beginners to get familiar with the code
		Juan	User Manual
Parallel code			Generalise restarting
Efficiency			Part of Mercury needs to become more efficient.
Paper	Anthony Thornton Thomas Weinhart
Meltable DEM	Yousef Shaheen