Skip to content

Morphemes from other cards assigned to selected card #364

@JSchoreels

Description

@JSchoreels

Hello,

I noticed something yesterday that I was able to fix in someway that re-appeared today after a recalc :

First, this is my setup :

Image

But I noticed some cards had very very low Due value, and wrong morphemes when I selected "show morphemes". For example :

Image
Card Type	Card 1
Note Type	Yomitan JP
Deck	Japan::1. Vocabulary::Yomitan
Preset	Vocabulary
Card ID	1755539664421
Note ID	1755539664421

Based on the morphs, I think it took the card 上の人 to compute morphs :

But this card also has others morphs

Image
Card Type	Card 1
Note Type	Yomitan JP
Deck	Japan::1. Vocabulary::Yomitan
Preset	Vocabulary
Card ID	1755539432567
Note ID	1755539432567

That is in fact the 事がある cards which also has wrong morphs

Image
Card Type	Card 1
Note Type	Yomitan JP
Deck	Japan::1. Vocabulary::Yomitan
Preset	Vocabulary
Card ID	1755539370967
Note ID	1755539370967

A few minutes ago, doing multiple recalcs didn't fixed.
I then emptied all my Filtered Decks and recalcs and and it did fixed it. I wonder if the FIltered Card that are moved from decks to decks are not causing issues ?

Image

The cardids doesn't seem to have changed between the bugged and fixed state. Is the cardids the only way cards and their morphemes are linked together ?

Extra Bug :
I'm investigating if the issue doesn't come become of the custom priority-files generated by the Generators, since I started to have the issue when using those. I notice that if I select a study plan that doesn't contain a word, the morphes itself won't even be seen in the card anymore **(WRONG : **That cards just don't get the morph correctly even with "Collection" as the priority selected)****

Image

Notice how the 挫 is not in the morphes, and thus the card gets an extremely good score at easiness and it's the next due card. I attached those study plan..
ReZero-study-plan-frequency-file.csv
ReZero-priority-file.csv

Metadata

Metadata

Assignees

Labels

awaiting-answersIssues with this label will be automatically closed after 21 days of inactivitybugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions