Clean up repository #1
Description
Encounter with Mihail has shown that repo is in a really bad state. Many test files are deprecated, there is no way for an external user to understand how to use the code. There possibly are some (hopefully minor) bugs. We have to:
- Get those test scripts that are illustrative in shape and store them as example case studies (working code + some comments).
- Get rid of the rest.
- Provide autotests
- Make a decent README.md
- Optional: think of implementing some kind of API (some handy functions to easily access model from other code, e.g. Mihail's ML stuff)
I suggest we do it after the analytical verification and current conference busyness, but before or in parallel with implementation of destruction model.