We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
我看embedding_lookup接口需要提供blocknums,但是这就有一个问题:因为id对应的block是根据频率动态计算的,用户怎么知道一个id实际对应多少个block呢?看了一下代码,其中有一些逻辑是判断blocknum是否大于0,那么是否可以这么认为:当blocknum传递0时,id实际存储有几个block,那么DeepRec就返回几个block的值?还有动态调整freq和id对应的blocknum的代码的位置在哪呢?
The text was updated successfully, but these errors were encountered:
已经了解了原理,关闭这个issue。
Sorry, something went wrong.
No branches or pull requests
我看embedding_lookup接口需要提供blocknums,但是这就有一个问题:因为id对应的block是根据频率动态计算的,用户怎么知道一个id实际对应多少个block呢?看了一下代码,其中有一些逻辑是判断blocknum是否大于0,那么是否可以这么认为:当blocknum传递0时,id实际存储有几个block,那么DeepRec就返回几个block的值?还有动态调整freq和id对应的blocknum的代码的位置在哪呢?
The text was updated successfully, but these errors were encountered: