Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Permission request: non-commercial research mirror of tokenized UltraData sets (SHADOW-125M)

Abierto
  • ¿Algo no está bien?
#383 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
huggingface
Área
data

Línea de trabajo

No repository file, test, or implementation entry point is identified. Review the cited UltraData dataset cards and MiniCPM5 tokenizer terms, then determine whether OpenBMB can grant the requested redistribution permission. Done means recording a clear approval, limitation, or refusal for the proposed public tokenized mirror.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hi OpenBMB team,

I'm Sai Kiran Bathula (Hugging Face / GitHub: QLNI), an independent researcher building SHADOW, a family of small ternary (1.58-bit) language models designed to run offline on a laptop CPU.

Already released:

Next: SHADOW-125M. This is a ternary, looped transformer over a frozen 512-bit word table, with ternary Engram memory and a separately trained retrieval index. It uses your MiniCPM5 tokenizer, and we plan to train on about 2T tokens from your UltraData family: Ultra-FineWeb / -L3, UltraX, UltraData-Math, UltraData-Code, SFT-2605, SFT-Agent-2609 and RL-2609. Your data recipe and the MiniCPM5-2B results are the reason we chose it.

Your cards say "no unauthorized unchanged redistribution", so we're asking before posting anything. We would like written permission to host a tokenized copy (MiniCPM5 token ids, in the mix and order we train on) in a public Hugging Face dataset repo, for non-commercial research use only.

Why public:

  • Cost. Tokenizing 2T tokens takes about a week of CPU time, and private storage for ~5 TB is a monthly cost a small independent project can't carry. A public repo removes both.
  • Reproducibility. Researchers can rerun our exact training without re-tokenizing, and our paper can point to the exact data.

What we would do:

  • Release it strictly as non-commercial, research-only, stated at the top of the card.
  • Label it clearly as derived from OpenBMB UltraData, not our data, with links to every source dataset and citations of your papers.
  • Keep your redistribution notice and the terms of each upstream source on the card.
  • Include a per-shard manifest (source file, revision) and honour any takedown request from you or rights holders within 48 hours.

If a full mirror isn't possible, we would welcome permission for part of it (for example only Ultra-FineWeb-L3 and UltraData-Math). Otherwise we'll keep the tokens private and publish only the recipe and the file list.

Thank you for releasing this data.
Sai Kiran Bathula (QLNI)

Lenguaje dominante
Jupyter Notebook
Estrellas
11.1k
Forks
766
Merge medio
5 h 3 min
PR fusionados (30 d)
6

Preparar el entorno

Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenBMB/MiniCPM

Todos los issues de OpenBMB/MiniCPM

Issues similares

Más issues de Data Engineering

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.