[wish] Release SAMPLE datasets
Yi Coder 1.5b is potentially a great model for fine-tuning on one's own codebase. It'd be great if you could release some SAMPLE portions of the dataset used for base training & instruction tuning (and perhaps recipes), so that fine-tuning could be done in a compatible format.
I have an app that includes built-in Python scripting with an app-specific API, and would love to add a chatbot tuned on that API, so that users could get small scripts written from natural language prompts, or even written and executed, without the user ever needed to see the code.
Hi π @twardoch , thank you so much π. We've already forwarded the request regarding the example data for the Coder model. We also have some example datasets for fine-tuning available at https://github.com/01-ai/Yi/tree/main/finetune/yi_example_dataset/data. Although they are not directly related to code, the format is the same. Thanks again!
Yi Coder 1.5b is potentially a great model for fine-tuning on one's own codebase. It'd be great if you could release some SAMPLE portions of the dataset used for base training & instruction tuning (and perhaps recipes), so that fine-tuning could be done in a compatible format.
I have an app that includes built-in Python scripting with an app-specific API, and would love to add a chatbot tuned on that API, so that users could get small scripts written from natural language prompts, or even written and executed, without the user ever needed to see the code.
Hi twardoch,
Pasting my reply from github issue:
Unfortunately we will not be releasing our data, but I'd be happy to provide some directions for your requirement.
For pertaining, check https://huggingface.co/datasets/bigcode/starcoderdata and https://huggingface.co/datasets/bigcode/the-stack-dedup .
For code SFT, check Code Feedback / CodeAlpaca / Evol-Instruct-code.
For library-specific SDK, start with library-specific SFT pairs mixed with general-purpose SFT first, continue train is very difficult to do correctly without performance loss, and python codes are not extremely hard to generalize. Just remember to keep your SFT pairs as diverse(both semantic-wise and task-wise) and as high-quality as possible.
Best Regards,
Nuo