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
Sometimes, it is a strategy to keep the dataset order as listed in the config. In that case, we need to prevent shuffling the merged dataset.
Add a config parameter that prevents shuffling.
No response
The text was updated successfully, but these errors were encountered:
I agree with the sentiment.
The answer has always been "just comment out the shuffle line in the code"
But really what makes Axolotl stand out among these tools is that it's config based instead of making users change code.
I believe that putting these rich options into the config file will give Axolotl a huge usability advantage.
Sorry, something went wrong.
I agree with the sentiment. The answer has always been "just comment out the shuffle line in the code" But really what makes Axolotl stand out among these tools is that it's config based instead of making users change code. I believe that putting these rich options into the config file will give Axolotl a huge usability advantage.
Thank you for agreeing :) I have just written a PR addressing this issue. Please take a look when you have a moment.
No branches or pull requests
🔖 Feature description
Sometimes, it is a strategy to keep the dataset order as listed in the config. In that case, we need to prevent shuffling the merged dataset.
✔️ Solution
Add a config parameter that prevents shuffling.
❓ Alternatives
No response
📝 Additional Context
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: