• View
• Edit
• History
• Print

Statistics and test results

This page does not desribe the current implementation. It was a draft used for discussion. Parts of it has been implemented.

What statistics and test results should be stored?

Currenct practise

In solfege 2.3.4, solfege stores all the answers you give, and show you statistics for different periods of time:

• This session
• Today
• Last 7 day
• Totally

In addition to this, the harmonic and melodic interval exercises can run a test where you are asked all intervals two times. The test results for all tests are stored separately from the statistics mentioned in the list above.

Implementation

(from memory, has to double check at home:) ~/.solfege/idbyname/lessonfilename/nnnnnnnnnn where nnnnnnnnnn is an integer from int(time.time()) when the statistics was saved.

Also there is a file ~/.solfege/idbyname/lessonfilename.md5 that is the md5sum of the file. If the file changes, then all the files in ~/.solfege/idbyname/lessonfilename/ are deleted.

New setup

I'm open to big changes here, just throw in your opinion. One question we can (and should) ask is: what statistics are usefull or interesting for the user? Should we keep statistics of all the practicing, or just of the tests?

Proposal from tomcato

The results from each test defined in a lesson file will be stored in a separate file.

It is possible that we want the same lesson file to be used by two different topics. This is done by symlinking or just copying the file. A side effect if the proposal described here is that you only have to complete the test for two identical lesson files once. Does anyone think this is confusing?

We generate a md5sum for each lesson file. The test results are stored in ~/.solfege/testresults/md5sumoflessonfile/nnnnnnnn. Here nnnnnnnn is an integer representing the time the test was completed.

If we want to continue storing statistics of all the practicing the user does, we store it in ~/.solfege/practiseresults/md5sumoflessonfile/nnnnnnnn.

Upgrades

Upgrades will be handled the way statistics are today. If the lesson file has changed, then the statistics is lost. Or more precicely, with this new setup: the statistics are still there, but you have to use the old lesson file to access it. It is possible to add some sort of upgrade for lesson file changes that will not break statistics, by renaming the directly md5sumoflessonfile. But I'm not very interested in implementing it, because it will cause problems for some people that believe that the lesson files are compatible while they in reality are not.