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
The paper
Unable to Reproduce Moshi's Performance on llamaQuestions Dataset
I attempted to replicate Moshi's performance on the llamaQuestions dataset as reported in the paper, but achieved only 13%.
Testing Methodology:
I used the inference method detailed at: https://github.com/kyutai-labs/moshi/blob/main/moshi/README.md#api
Request for Clarification:
Could you please release the test script for LlamaQuestions?
Observation:
If the script used is https://github.com/kyutai-labs/moshi/blob/main/scripts/moshi_benchmark.py, it does improve performance to 55%. However, it seems unusual to perform inference 10 times for same question.
Attached is my testing process file.
moshi_llamaQ.zip
The text was updated successfully, but these errors were encountered:
afaik they didn't release the paper's model but only a demo, less powerful version
Sorry, something went wrong.
No branches or pull requests
Due diligence
Topic
The paper
Question
Unable to Reproduce Moshi's Performance on llamaQuestions Dataset
I attempted to replicate Moshi's performance on the llamaQuestions dataset as reported in the paper, but achieved only 13%.
Testing Methodology:
I used the inference method detailed at:
https://github.com/kyutai-labs/moshi/blob/main/moshi/README.md#api
Request for Clarification:
Could you please release the test script for LlamaQuestions?
Observation:
If the script used is https://github.com/kyutai-labs/moshi/blob/main/scripts/moshi_benchmark.py, it does improve performance to 55%. However, it seems unusual to perform inference 10 times for same question.
moshi_llamaQ.zip
The text was updated successfully, but these errors were encountered: