Re: [mnemosyne-proj-users] Re: Interpreting log.txt entries
Hi, Here is the code: def calculate_interval_noise(self, interval): if interval == 0: noise = 0 elif interval = DAY: noise = random.choice([0, DAY]) elif interval = 10 * DAY: noise = random.choice([-DAY, 0, DAY]) elif interval = 60 * DAY: noise = random.uniform(-3 * DAY, 3 * DAY) else: noise = random.uniform(-0.05 * interval, 0.05 * interval) return noise On Wednesday, December 15, 2010 10:09:41 pm Matt wrote: Hi Pter, I have another question: They are: scheduled interval, actual interval (could be different from scheduled interval if you review early or late), new interval, noise (random scheduling fudge factor), thinking time in seconds. Is the fudge factor a random integer between -3 and 3, where each integer is equally probable? An integer rounded from a random number drawn from a normal distribution with mean=0 and standard devation=1? Something else? Thanks! -Matt -- Peter Bienstman Ghent University, Dept. of Information Technology Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium tel: +32 9 264 34 46, fax: +32 9 264 35 93 WWW: http://photonics.intec.UGent.be email: peter.bienst...@ugent.be -- You received this message because you are subscribed to the Google Groups mnemosyne-proj-users group. To post to this group, send email to mnemosyne-proj-us...@googlegroups.com. To unsubscribe from this group, send email to mnemosyne-proj-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
[mnemosyne-proj-users] Re: Interpreting log.txt entries
Hi Pter, I have another question: They are: scheduled interval, actual interval (could be different from scheduled interval if you review early or late), new interval, noise (random scheduling fudge factor), thinking time in seconds. Is the fudge factor a random integer between -3 and 3, where each integer is equally probable? An integer rounded from a random number drawn from a normal distribution with mean=0 and standard devation=1? Something else? Thanks! -Matt -- You received this message because you are subscribed to the Google Groups mnemosyne-proj-users group. To post to this group, send email to mnemosyne-proj-us...@googlegroups.com. To unsubscribe from this group, send email to mnemosyne-proj-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
[mnemosyne-proj-users] Re: Interpreting log.txt entries
BTW, in the current 2.0 codebase, there is code to parse these log entries and write the results to an sql database (libmnemosyne/ file_formats/science_log_parser and science_server/parse_logs), which could be useful :-) For instance, when database is mentioned, three numbers follow. Example: 2010-12-09 08:00:09 : Loaded database 2 0 10 It seems that the 2 reflects the number of cards scheduled, the 0 reflects the number of cards not yet learned, and the 10 is the total deck size. Yep. Lastly, there are two pairs of numbers, and then a number that seems to range from 0 to very high (I've seen 8903.6 on just the first log I looked at). Here's where I'm getting really confused. They are: scheduled interval, actual interval (could be different from scheduled interval if you review early or late), new interval, noise (random scheduling fudge factor), thinking time in seconds. Hope this helps, Peter -- You received this message because you are subscribed to the Google Groups mnemosyne-proj-users group. To post to this group, send email to mnemosyne-proj-us...@googlegroups.com. To unsubscribe from this group, send email to mnemosyne-proj-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en.
