Re: [Memaid-users] Grade's for vocabulary learing and Categories

[Andreas G. <agr...@ya...>]

Thanks, Peter and David, for your responses. You both helped me well
improving my usage and view of memaid.

I changed inasmuch as I begin to thing off memaid as a recalling-aid,
not so much a learning tool. memaid keeps knowledge active, there often
needs to be a learning process before - where memaid may or may not help
well. In my restaurant example, it doesn't help much if I don't feed 
this vocabulary into a separate database using low grades to enforce
frequent and focused repetition (aka drilling exercise)


> More or less. So more "NN Training Time" - longer you will wait (e.g. after 
> pressing "quit"), but *MemAid will be better prepared to schedule repetitions 
> for you.

In the fox code, you use user input time to train the net for 2 seconds,
so it get's trained quite often and for a rather big total of seconds.
For kmemaid, this get's done only once on exit (or when saving), but for
a maximum of 10 secs. So a first sight it seems that kmemaid doesn't
spend as much time training the net. Would this be a favourable thing to
change within kmemaid? How important is training time?

> > Talking about categories, I, for one, would love to see them in memaid.
> 
> Peter's PyQT_MemAid has them, but plain MemAid will probably also have them, 
> sooner or later - if somebody will have enough lack of categories and will 
> implement them. :)

"enough lack of categories" - huh ?

> I understand your need. I could argue a bit about economy of over-working on 
> (some) items to have higher retention rate - I personally prefer to stick on 
> normal schedules and have nice feeling that I learn the most-optimally: good 
> retention with relatively small amount of time spend of learning.

I have read your articles and support your points. Once, I heard a
saying the "to a child with a hammer, everything looks like a nail". I
guess that's what happened here to me :-) Memaid is/might be optimal for
consequent, disciplined learning, but fails for ad-hoc, time-pressed
item-acquisition. I didn't realize in the beginning - I had a new hammer
:-)


Keep up the good work, and many thanks for your support,

Andreas