<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Memory Learning Revisited</title>
	<atom:link href="http://aloedream.animeblogger.net/archives/253/feed" rel="self" type="application/rss+xml" />
	<link>http://aloedream.animeblogger.net/archives/253</link>
	<description>enjoying my nightmare</description>
	<pubDate>Mon, 23 Nov 2009 01:26:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kitsune</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17950</link>
		<dc:creator>Kitsune</dc:creator>
		<pubDate>Thu, 26 Feb 2009 04:15:56 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17950</guid>
		<description>I've been using Mnemosyne for some time and quite pleased with it. There are many similar programs, but,  based on what I read, they are not very reliable.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using Mnemosyne for some time and quite pleased with it. There are many similar programs, but,  based on what I read, they are not very reliable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17744</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Tue, 17 Feb 2009 01:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17744</guid>
		<description>So you're not hot for graphs... /writes down in little notebook titled 'lolikitianology notes' XD</description>
		<content:encoded><![CDATA[<p>So you&#8217;re not hot for graphs&#8230; /writes down in little notebook titled &#8216;lolikitianology notes&#8217; XD</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lolikitsune</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17741</link>
		<dc:creator>lolikitsune</dc:creator>
		<pubDate>Mon, 16 Feb 2009 22:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17741</guid>
		<description>Clarification: graphs melt Jason.</description>
		<content:encoded><![CDATA[<p>Clarification: graphs melt Jason.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17688</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Sat, 14 Feb 2009 23:28:29 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17688</guid>
		<description>&lt;em&gt;Anki should adjust the next interval to suit.&lt;/em&gt;

I noticed it feels better after the first interval is completed.

&lt;em&gt;I may have missed something though.&lt;/em&gt;

Same here. I simply noticed that I had about 6 imported categories but the cards were being learned not from the first category imported; without the randomized learning setting.

&lt;em&gt;It would be easy to implement a textual report in a plugin if you wanted to.&lt;/em&gt;

I may look into it, even just for a weekly outlook.

&lt;em&gt;Anki has been designed to scale to decks of 100,000 cards or more, and such a setting would not be efficient.&lt;/em&gt;

I can see the issue of "what" to select when thousands of cards all have the same comparative age. The wrong selecting may take much longer, and may not be worth it. The randomized learning setting does well enough.

&lt;em&gt;Your comments about the documentation are quite fair&lt;/em&gt;

Perhaps it is where my confusion came from. One thing that comes to mind is the Mark feature, which I was unable to see where I could look at marked cards other than in the Edit All window. I'm more clear after playing with it for a few weeks, but some friends and family installed it after I mentioned SRS and they were a bit confused as well. I think it is less about the exact use and features vs some general guidelines to studying.</description>
		<content:encoded><![CDATA[<p><em>Anki should adjust the next interval to suit.</em></p>
<p>I noticed it feels better after the first interval is completed.</p>
<p><em>I may have missed something though.</em></p>
<p>Same here. I simply noticed that I had about 6 imported categories but the cards were being learned not from the first category imported; without the randomized learning setting.</p>
<p><em>It would be easy to implement a textual report in a plugin if you wanted to.</em></p>
<p>I may look into it, even just for a weekly outlook.</p>
<p><em>Anki has been designed to scale to decks of 100,000 cards or more, and such a setting would not be efficient.</em></p>
<p>I can see the issue of &#8220;what&#8221; to select when thousands of cards all have the same comparative age. The wrong selecting may take much longer, and may not be worth it. The randomized learning setting does well enough.</p>
<p><em>Your comments about the documentation are quite fair</em></p>
<p>Perhaps it is where my confusion came from. One thing that comes to mind is the Mark feature, which I was unable to see where I could look at marked cards other than in the Edit All window. I&#8217;m more clear after playing with it for a few weeks, but some friends and family installed it after I mentioned SRS and they were a bit confused as well. I think it is less about the exact use and features vs some general guidelines to studying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Elmes</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17671</link>
		<dc:creator>Damien Elmes</dc:creator>
		<pubDate>Sat, 14 Feb 2009 09:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17671</guid>
		<description>Thanks for the reply.

Adjusting the original 8-12 hours to something a bit bigger won't do any harm. Anki should adjust the next interval to suit.

Looking at the Mnemosyne source code, it looks like the default setting will show the cards in the order they're added, just like Anki. It uses the order the cards are in the deck, not the day they were added. I may have missed something though.

Re textual statistics, most users prefer the graphs. It would be easy to implement a textual report in a plugin if you wanted to.

A setting to compare card age is unlikely - Anki has been designed to scale to decks of 100,000 cards or more, and such a setting would not be efficient.

Your comments about the documentation are quite fair - it is lacking, and is something I plan to fix for 1.0, but the interface is still changing at this point.</description>
		<content:encoded><![CDATA[<p>Thanks for the reply.</p>
<p>Adjusting the original 8-12 hours to something a bit bigger won&#8217;t do any harm. Anki should adjust the next interval to suit.</p>
<p>Looking at the Mnemosyne source code, it looks like the default setting will show the cards in the order they&#8217;re added, just like Anki. It uses the order the cards are in the deck, not the day they were added. I may have missed something though.</p>
<p>Re textual statistics, most users prefer the graphs. It would be easy to implement a textual report in a plugin if you wanted to.</p>
<p>A setting to compare card age is unlikely - Anki has been designed to scale to decks of 100,000 cards or more, and such a setting would not be efficient.</p>
<p>Your comments about the documentation are quite fair - it is lacking, and is something I plan to fix for 1.0, but the interface is still changing at this point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan A</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17651</link>
		<dc:creator>Ryan A</dc:creator>
		<pubDate>Fri, 13 Feb 2009 16:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17651</guid>
		<description>Demien,

Maybe I'm doing it wrong, since I'm only guessing at the proper way to do SRS.

The 8-12 hour interval is on cards I've yet to learn. So on Day 1, I implied that those cards were recently moved from New to Failed. By the morning of Day 2, I usually feel comfortable after a few reviews to grade them Hard (the 8-12 hour interval). The result is that these cards reappear that evening when I review, rather than the next morning (which I'd prefer).

As far as the functionality, I believe it works correctly, to these settings, so if I were to review in the evenings, it would show me the next day. Perhaps my timing for learning new cards is off, but for a most cards, I only feel comfortable after keeping them in failed on the first day they appear, and if I start to remember them on the next day, I grade them with an interval (usually happens in the morning).

Reviewing the group of previous days' failed cards in the morning, then pushing ones I know to an interval, allows new cards to be put in the failed queue in the morning. I review the new cards from morning to evening, and the next morning I usually grade them with an interval (aiming for the next day). If there are no slots available in the failed queue, no new cards will come out [and no scheduled review cards will be reviewed; or so I've observed].

[Maybe 'Failed' should be called 'Learning']

&lt;blockquote&gt;Complaining that you had to change the settings so that Anki shows new cards in random order is unfair. It’s the same default as Mnemosyne.&lt;/blockquote&gt;

I'm not sure if the default ordering is the same in Mnemosyne, as I started without the random order setting, and never needed to change that setting. My thought is that Mnemosyne showed new cards in order per category, but it selected cards from multiple categories, regardless if the category's contents are older than another category.

I noticed that Anki does card level ordering over the whole deck, so if a set of cards are imported into a tag, and another set is inserted to a tag just after, the first tag's contents will be learned first. 

Mnemosyne's learning was spread evenly over the categories, cards in order, per category.

This may not be entirely true, depending on how Mnemosyne compares card dates. If it uses the DATE, then cards imported anytime during a day will be considered the same age. Anki seems to use the full DATETIME for comparing age. I haven't looked at the code, but it's just a hunch.

This would invalidate what I said about Mnemosyne learning evenly over categories, because cards imported at a later day would be learned later.

[Hopefully that made sense]

&lt;blockquote&gt;Many people have reported that new cards spread throughout reviews make the reviews more fun. If you have set a reasonable number of new cards per day, it’s not dangerous.&lt;/blockquote&gt;

I would have liked to do it this way, but once the Failed queue is full the reviews will not proceed. Again, could be error in my method.

&lt;blockquote&gt;Reviewing cards in order of oldest first (the default) makes getting rid of the bulk of your reviews easily. This reduces the chances of the number of cards building up to unmanageable levels.&lt;/blockquote&gt;

The randomization of review is trickery I enjoy. As long as the review count isn't over say 250, I personally don't have an issue with large review sets.

&lt;blockquote&gt;It would be good if you could evaluate those points objectively instead of just being against change.&lt;/blockquote&gt;

You're definitely right about that. I suppose I send mixed signals on both Mnemosyne and Anki with these posts. I can admit being subjective about the change from Mnemosyne to Anki, so here's some hard things I think would be good:

&lt;ul&gt;
&lt;li&gt;Textual statistics which don't require the graphing library&lt;/li&gt;
&lt;li&gt;A setting which specifies how to compare card age (by second, minute, hour, day)&lt;/li&gt;
&lt;li&gt;Tips/tutorial on the &lt;em&gt;way&lt;/em&gt; to study with the default options (I'm guessing that grading failed cards on an interval should happen in the evening)&lt;/li&gt;
&lt;li&gt;Tips on the relation between Failed queue and New (if failed is full, no new cards will be shows, etc)&lt;/li&gt;
&lt;li&gt;Something like Tip of the Day, or a repository of tips/hints (not really that important)&lt;/li&gt;
&lt;/ul&gt;

Of course, I'm being unfair ^_^ that the way users work to stimulate thought and more intrigue. I think my personal issues could be cleared up if there was a good tutorial of how to set it up for the way a person wants to review, or some simple insight on the timing.

Even if I have my grumbles with it, Anki is a great and sleek piece of software. I truly appreciate the comments from you, and it shows you are a committed developer, which is just as noteworthy since it shows the software has spirit and more possibilities... Honestly, Mnemosyne is solid and suffices, but it seems to be going Latin [much less possibilities].</description>
		<content:encoded><![CDATA[<p>Demien,</p>
<p>Maybe I&#8217;m doing it wrong, since I&#8217;m only guessing at the proper way to do SRS.</p>
<p>The 8-12 hour interval is on cards I&#8217;ve yet to learn. So on Day 1, I implied that those cards were recently moved from New to Failed. By the morning of Day 2, I usually feel comfortable after a few reviews to grade them Hard (the 8-12 hour interval). The result is that these cards reappear that evening when I review, rather than the next morning (which I&#8217;d prefer).</p>
<p>As far as the functionality, I believe it works correctly, to these settings, so if I were to review in the evenings, it would show me the next day. Perhaps my timing for learning new cards is off, but for a most cards, I only feel comfortable after keeping them in failed on the first day they appear, and if I start to remember them on the next day, I grade them with an interval (usually happens in the morning).</p>
<p>Reviewing the group of previous days&#8217; failed cards in the morning, then pushing ones I know to an interval, allows new cards to be put in the failed queue in the morning. I review the new cards from morning to evening, and the next morning I usually grade them with an interval (aiming for the next day). If there are no slots available in the failed queue, no new cards will come out [and no scheduled review cards will be reviewed; or so I've observed].</p>
<p>[Maybe 'Failed' should be called 'Learning']</p>
<blockquote><p>Complaining that you had to change the settings so that Anki shows new cards in random order is unfair. It’s the same default as Mnemosyne.</p></blockquote>
<p>I&#8217;m not sure if the default ordering is the same in Mnemosyne, as I started without the random order setting, and never needed to change that setting. My thought is that Mnemosyne showed new cards in order per category, but it selected cards from multiple categories, regardless if the category&#8217;s contents are older than another category.</p>
<p>I noticed that Anki does card level ordering over the whole deck, so if a set of cards are imported into a tag, and another set is inserted to a tag just after, the first tag&#8217;s contents will be learned first. </p>
<p>Mnemosyne&#8217;s learning was spread evenly over the categories, cards in order, per category.</p>
<p>This may not be entirely true, depending on how Mnemosyne compares card dates. If it uses the DATE, then cards imported anytime during a day will be considered the same age. Anki seems to use the full DATETIME for comparing age. I haven&#8217;t looked at the code, but it&#8217;s just a hunch.</p>
<p>This would invalidate what I said about Mnemosyne learning evenly over categories, because cards imported at a later day would be learned later.</p>
<p>[Hopefully that made sense]</p>
<blockquote><p>Many people have reported that new cards spread throughout reviews make the reviews more fun. If you have set a reasonable number of new cards per day, it’s not dangerous.</p></blockquote>
<p>I would have liked to do it this way, but once the Failed queue is full the reviews will not proceed. Again, could be error in my method.</p>
<blockquote><p>Reviewing cards in order of oldest first (the default) makes getting rid of the bulk of your reviews easily. This reduces the chances of the number of cards building up to unmanageable levels.</p></blockquote>
<p>The randomization of review is trickery I enjoy. As long as the review count isn&#8217;t over say 250, I personally don&#8217;t have an issue with large review sets.</p>
<blockquote><p>It would be good if you could evaluate those points objectively instead of just being against change.</p></blockquote>
<p>You&#8217;re definitely right about that. I suppose I send mixed signals on both Mnemosyne and Anki with these posts. I can admit being subjective about the change from Mnemosyne to Anki, so here&#8217;s some hard things I think would be good:</p>
<ul>
<li>Textual statistics which don&#8217;t require the graphing library</li>
<li>A setting which specifies how to compare card age (by second, minute, hour, day)</li>
<li>Tips/tutorial on the <em>way</em> to study with the default options (I&#8217;m guessing that grading failed cards on an interval should happen in the evening)</li>
<li>Tips on the relation between Failed queue and New (if failed is full, no new cards will be shows, etc)</li>
<li>Something like Tip of the Day, or a repository of tips/hints (not really that important)</li>
</ul>
<p>Of course, I&#8217;m being unfair ^_^ that the way users work to stimulate thought and more intrigue. I think my personal issues could be cleared up if there was a good tutorial of how to set it up for the way a person wants to review, or some simple insight on the timing.</p>
<p>Even if I have my grumbles with it, Anki is a great and sleek piece of software. I truly appreciate the comments from you, and it shows you are a committed developer, which is just as noteworthy since it shows the software has spirit and more possibilities&#8230; Honestly, Mnemosyne is solid and suffices, but it seems to be going Latin [much less possibilities].</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Damien Elmes</title>
		<link>http://aloedream.animeblogger.net/archives/253/comment-page-1#comment-17648</link>
		<dc:creator>Damien Elmes</dc:creator>
		<pubDate>Fri, 13 Feb 2009 13:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://aloedream.animeblogger.net/?p=253#comment-17648</guid>
		<description>If you see the same 8-10 hours on the second day after reviewing, it sounds like you're not using the latest version of Anki. 

The default 8-12 hour intervals were chosen because many people like to review at night and then again the next morning.

As for the failed cards being in order, this ensures that every card you see has been waiting for as long as possible. SuperMemo displays the final drill in order too AFAIK, and Mnemosyne's approach often ends up showing the same failed card very soon after it was previously seen - and sometimes multiple times in a row.

Anyway, if you've made mistakes on the cards, they're likely to be difficult to remember. I don't see order as being a big problem here.

As for the graphs, all the information is available in the deck if you want to write a plugin. The majority of people want graphs, not text.

Complaining that you had to change the settings so that Anki shows new cards in random order is unfair. It's the same default as Mnemosyne.

Many people have reported that new cards spread throughout reviews make the reviews more fun. If you have set a reasonable number of new cards per day, it's not dangerous.

Reviewing cards in order of oldest first (the default) makes getting rid of the bulk of your reviews easily. This reduces the chances of the number of cards building up to unmanageable levels.

Basically, I think many of the points you raised are simply the fact that Anki doesn't perform the way you were used to with Mnemosyne. It would be good if you could evaluate those points objectively instead of just being against change. And Anki can be customized fairly easily to behave similarly to Mnemosyne, so attacking the defaults when they work well for other people seems a bit unfair.</description>
		<content:encoded><![CDATA[<p>If you see the same 8-10 hours on the second day after reviewing, it sounds like you&#8217;re not using the latest version of Anki. </p>
<p>The default 8-12 hour intervals were chosen because many people like to review at night and then again the next morning.</p>
<p>As for the failed cards being in order, this ensures that every card you see has been waiting for as long as possible. SuperMemo displays the final drill in order too AFAIK, and Mnemosyne&#8217;s approach often ends up showing the same failed card very soon after it was previously seen - and sometimes multiple times in a row.</p>
<p>Anyway, if you&#8217;ve made mistakes on the cards, they&#8217;re likely to be difficult to remember. I don&#8217;t see order as being a big problem here.</p>
<p>As for the graphs, all the information is available in the deck if you want to write a plugin. The majority of people want graphs, not text.</p>
<p>Complaining that you had to change the settings so that Anki shows new cards in random order is unfair. It&#8217;s the same default as Mnemosyne.</p>
<p>Many people have reported that new cards spread throughout reviews make the reviews more fun. If you have set a reasonable number of new cards per day, it&#8217;s not dangerous.</p>
<p>Reviewing cards in order of oldest first (the default) makes getting rid of the bulk of your reviews easily. This reduces the chances of the number of cards building up to unmanageable levels.</p>
<p>Basically, I think many of the points you raised are simply the fact that Anki doesn&#8217;t perform the way you were used to with Mnemosyne. It would be good if you could evaluate those points objectively instead of just being against change. And Anki can be customized fairly easily to behave similarly to Mnemosyne, so attacking the defaults when they work well for other people seems a bit unfair.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
