Has this change gone through yet? I’ve done all the grammar points up through n3, and I think every single one is listed as troubled (I didn’t think I was doing that bad!). I have at least 360+ listed as troubled.
I also seem to have every point listed as troubled, might be accurate, but I hope not also clicking the bookmark for me doesn’t do anything. I’m on an iPad…
-
If I press the bookmark on mobile browser (Android) nothing happens
-
the bookmark is way too big on mobiles:
- would be nice to have the bookmarks during reviews in the “show grammar info” screen
I’ve solved the issue with stat page not working for me. Before I’d tried to clear the site data and cookies - still was getting 500 error from the stats page. Logging out also wasn’t helpful. Today I’ve closed all open tabs with bunpro, and after a relogin stat page started working. So closing all active tabs did the trick for me.
@Anthropos888 Bookmark should be working on mobile now. There was an issue with touch events but it was resolved.
@Leyline Glad to hear it!
@ApolloFortyNine Maybe 75% is to strict?? Maybe troubled grammar should only come after a certain number of times reviewed so smaller review totals 4 times right 1 time wrong wouldn’t count?
@Pushindawood This is awesome! I love the ability to select specific grammar points for cram. So glad we have this now!
I wonder if instead of a ‘Copy Japanese’ button, furigana could be hidden when selecting text.
Often when I copy from a Japanese sentence on Bunpro, I am only selection one or several words which I would like to look up, so I don’t need the entire sentence. I actually found some solutions when I was working on a project of my own.
Yeah for a second I thought it was a bug and was just showing all my grammar points. My list goes on and on and is a bit debilitating. I think the threshold should be more lenient. Also I think you should group them by JLPT level and have them show only on clicking the level. That way it isn’t as intimidating as just a massive block like it is right now.
I’m thinking maybe 66% (or even lower) would be better:
My averages are hovering right around 70% overall.
If you miss a grammar point twice right off the bat, you’d have to ace it 6 times in a row just to hit 0.75.
Ideally though, you should only be shown a small handful of grammar points. Maybe it should be limited to ~10-15 at a time, to not look overwhelming? The grammar points with more total reviews (or that were more recently missed) could be prioritized for display if they have to be limited.
Also, just because this is a grammar-focused site… too* strict
I actually think ignoring the first four or so reviews would definitely filter out the beginner items.
OMG love it!! The new stats page is so much better!
I actually just counted, and I apparently have 455 “troubled grammar” points, haha. I’d say that 75% accuracy is definitely far too high of a threshold.
I think it’s important to remember that forgetting (i.e. missing) reviews is an intended part of SRS. So, our accuracy shouldn’t be viewed as if it were a test score, especially since reviewing each grammar point 12 times over the course of a year (acing every single review) would be less beneficial to one’s long-term memory than missing lots of reviews and reinforcing them with extra (and more frequent!) reviews until the grammar finally starts to feel natural.
I think 75% is fine but if you’ve got a grammar point right the last 2/3 reviews in a row you probably know it well enough for it to not be troubled.
For instance I had trouble with amari months ago but now I know it well and have passed all its reviews since then, yet it still appears on troubled grammar.
agree completely…I struggle to remember just about everything…
I have 114 “troubled grammar” points and I’ve only unlocked 162…geez.
My average accuracy
I’m not great at WK either
Some of us are slower to learn and/or just don’t have great memories…
the stats need some tweaking … what would be more useful for me … rank the troubled grammar in terms of times wrong since last review or some other mathematical way of ranking them so they can be sorted or whatever so it’s easier to figure out the ones that I’m really struggling with and which ones I don’t feel like I’m struggling with anymore…also which ones are new … some way to filter/sort them …etc…
@Pushindawood You may not want to use a formula this complicated (as it could be hard for users to follow), but this is what I use in my leech script on WaniKani:
(incorrect / currentStreak^1.5) > 1
(If your system allows the current streak to be 0 instead of always a minimum of 1 you’ll need to do something about the divide by zero.)
I actually use >= 1
, but this has the downside that a single wrong answer makes that item a leech, which seems strict (WaniKani always gives you a streak of at least 1, so getting the first answer wrong means 1 / 1^1.5 = 1
.
> 1
means it requires at least two in a row wrong at first (or some other combination of right/wrong later) to make the item a leech. Plus, by using currentStreak
, you’ll consider how the user is doing right now and not just the past.
For example:
With your formula, any combination of 2 wrong and 3 right will make the item a leech. With my formula, 2 right then 2 wrong then 1 right is very different from 2 wrong then 3 right. The former would have a score of 2
, which is a leech. The latter would have a score of 0.38
, which is not.
It gives the user the benefit of the doubt that if they got an item right more recently, they’re more likely to get them right again. Of course, this only goes so far, and if you got an item wrong a bunch before, it could stay a leech despite a long current streak. And naturally it makes sense to ignore “burned” items and never consider them leeches.
P.S. I wish you had the math plugin installed so I could use Latex.
Just came here to say, thanks for the updates, and I do agree with the others saying that the current way of calculating “troubled” points is too strict. I have 274 troubled points (out of 492 total).
I like @seanblue’s suggestion, plus perhaps some of the ideas about creating a cutoff of “worst 20” or something like that.
I am completely new to Bunpro and am loving it.
I just wanted to add how much I love the bookmarks (had no idea it was a new feature, since I’m new but I am getting addicted to them already!) and actually came to ask about having them available during reviews, but I see that’s already been covered in conversation, which makes me even more happy. I am really encouraged by all that you are doing. A lot of things in this update already has me hooked. Thanks for the hard work.
Oh, speaking of available during reviews… I’d like to be able to copy both English and Japanese during reviews. I usually need to copy sentences right after failing a review and I want to post them on the forums with a question. Right now I use a script, but it would be nice to have native support there.
Very good update! Thanks
Perhaps just let us set the percentage ourselves? With so many set to troubled, I don’t believe I’ll ever take a look at them. I think being able to set it to something like 50% (so you know which ones really really need checked) would be helpful.