Smart offline checker - Githubissues

precice / preeco-orga

Organization and material for the preECO project

MIT License

3 stars 1 forks source link

Smart offline checker #1

Open uekerman opened 8 months ago

uekerman commented 8 months ago

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 commented 7 months ago

Ongoing endeavour:

https://github.com/precice/precice/issues/2004
https://github.com/precice/precice/issues/1865 (required for data flow checks)
https://github.com/precice/precice/pull/1911 https://github.com/precice/precice/issues/1512 Deadlocks in coupling schemes
https://github.com/precice/precice/issues/531
https://github.com/precice/precice/issues/1997
https://github.com/precice/precice/issues/778

Existing more fundamental problems:

https://github.com/precice/precice/issues/899

fsimonis commented 7 months ago

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?