You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LiNT uses the difficulty score and level that are calculated in t-scan, but also stores the level boundaries for some of its own visuals and explanatory texts. This results in some wonkiness when the formula is updated in t-scan but not (yet) in LiNT.
A possible solution is that t-scan could
Associate version numbers with difficulty formulas.
Let the user pick the version to use when starting the scan. Should default to the latest version, of course.
Then LiNT would continue to request the "old" formula until we update it.
This would also be a neat feature for researchers - while updates to the formula are always minor, it is nice for comparison if you can make sure that everything is scanned with the same formula.
The text was updated successfully, but these errors were encountered:
LiNT uses the difficulty score and level that are calculated in t-scan, but also stores the level boundaries for some of its own visuals and explanatory texts. This results in some wonkiness when the formula is updated in t-scan but not (yet) in LiNT.
A possible solution is that t-scan could
Then LiNT would continue to request the "old" formula until we update it.
This would also be a neat feature for researchers - while updates to the formula are always minor, it is nice for comparison if you can make sure that everything is scanned with the same formula.
The text was updated successfully, but these errors were encountered: