Question about large-scale data training and packing algorithm for MOSS-style inputs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 138
- PR merge metrics
- No merged PRs in 30d
Description
Thank you for your great work on MOSS—it’s been very inspiring!
I believe the model couldn't have been trained on individual samples sequentially due to efficiency concerns. Given MOSS's unique input format (delay shifting), standard sequence packing algorithms might not apply directly.
Could you please share:
What strategy was used for training data packing/grouping?
Any special considerations for handling the special tokens during batching?
If custom padding/packing approaches were developed, would you be willing to share the method?
This information would be extremely helpful for my own research with similar architectures. Thanks in advance for your insights!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points to inspect. It asks maintainers to explain the training data packing strategy, batching special-token handling, and any custom padding or packing method; completion would require a documented answer rather than a scoped code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100