Some code integration work
Toomas Laasik
This week I've been thinking how we can integrate the whole thing
together. What I found while digging our current code was a bit sad.
Different data structures, halfy implemented things, no documentation.
So to level things up a bit, I wrote some base code that uses some
classical software development techniques. I remember several weeks ago
Oleg pointed out the similar concept on our meeting. The best thing
about it is probably bringing in 3 interfaces. Each one does it's own
task and doesn't depend on others at all. There can be even multiple
implementations of one when needed. And those can be chosen runtime! Now
each one of us can start implementing some interface without disturbing
others. Implementing can mean porting already written things to current
base code.
Here are the tasks that can be done separately. I suggest that the one
who is interested in working on one of these, please write to our
mailing list. This way we won't do the same thing over and over again.
* Sparse matrix loading and saving from disk from txt format
* Vector loading and saving to disk from txt format
* Equation solver - here we may have multiple implementations
* State manager - here we may have also multiple implementations. Please
see README, to learn what this is. Basically this is executed
periodically to do something (eg print progress).
But before we can start working on those we must agree on the structures
defined in main.h. This part is critical, because this is the
communication link between interfaces and keeps them as independent as
possible. Please post your suggestions here or communicate in msn before
changing code in svn. We need that to be rock solid, because changing
those afterwards will probably break the other people's implementations.
Please also read cg/README.txt
Toomas