Smart offline checker

[uekerman]

It should also be able to detect logical errors, such as: Data is written to mesh A and communicated via mesh B, but there is no data mapping defined between mesh A and mesh B. The checker should also be able to detect redundant actions, such as: Participant A receives mesh B, but does no use it.

[fsimonis]

Ongoing endeavour:

• Required preCICE version in the preCICE configuration file precice#2004
• Use a data-flow graph to handle data processing precice#1865 (required for data flow checks)
• Add additional cpl-scheme to compositional test precice#1911 Deadlock during initializeData in multi-coupling scheme precice#1512 Deadlocks in coupling schemes
• preCICE Config accepts <max-used-iterations> greater <max-iterations> if <timesteps-reused value="0"/> precice#531
• Non-existing mapping is not detected precice#1997
• Segfault due to changed configuration precice#778

Existing more fundamental problems:

• preCICE allows mixing different configuration files precice#899

[fsimonis]

Potential thesis

• Catalogue of problem cases.
• Implemented as an external tool (python lxml + etree is working for parsing our namespace-illformated cases)
• Goal: transfer detection know-how to a preCICE checker.

Questions per case:

• Under which circumstances does a user run into it?
• How can this be reliably detected?
• Is there a reliable solution to the problem?
• What are suggestions for the user to proceed?