I think if you set check_every sufficiently high, you should eventually see a worse fit (and maybe a very slight speed up). I think it speaks to the usefulness of check_every that I actually had to look in the code to make sure it's even still implemented. All it does is reduce the number of candidate knot locations during knot search. One reason to do this would be to make sure you don't end up with knots too close together. However, the minspan argument takes care of that in a much nicer way.
引自github:
相关问题 更多 >
编程相关推荐