The Nordic Pile replication code
The Nordic Pile is a repository with the aim of providing tools and code to download and replicate a large nordic language dataset. The dataset consists of many smaller datasets combined together. With the objective to cover a broad set of language modalities.
Workflow
To propose a new dataset be added to the Nordic Pile, open an issue.
Your issue should include a description of the dataset, its size, what language(s) it is in,
a link to the data, and any other relevant information. If a project manger approves your proposal,
they will change its label to and add it to
. Datasets that we elect to not include in the current version of the Pile will receive a
or
label. We will now focus on datasets in the languages of the nordics: Swedish, Danish, Norwegian and Finnish.
To claim responsibility for implementing an unclaimed dataset,
leave a comment on one of our unassigned issues. Once a dataset
has been assigned to you, make the necessary changes to datasets.py and pile.py
in a fork and submit a pull request. If you require, you can also
submit a script for processing the data as shown here.
To raise an issue that is not proposing a new dataset,
open an issue with the tag or
as appropriate.
Data ready for final implementation should meet the following criteria:
- The data must be in lm_dataformat format.
- The data must be shuffled.
Attribution
This initiative is heavily inspired by Eleuther AIs The Pile project.
https://www.eleuther.ai/
https://pile.eleuther.ai/
Datasets
| Dataset | Status |
|---|---|
| Wikipedia-Swedish | 🙋♀️ Waiting for contributor |
| Wikipedia-Danish | 🙋♀️ Waiting for contributor |
| Wikipedia-Norwegian | 🙋♀️ Waiting for contributor |
| Wikipedia-Finnish | 🙋♀️ Waiting for contributor |
| Swedish Parliament | 🙋♀️ Waiting for contributor |
Metadata
Release files for the-nordic-pile 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| the-nordic-pile-0.0.2.tar.gz | 5.9 kB | Without provenance | Details for the-nordic-pile-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| the_nordic_pile-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for the_nordic_pile-0.0.2-py3-none-any.whl |
Total release size: 12.2 kB
Release files / the-nordic-pile-0.0.2.tar.gz
| Download URL | the-nordic-pile-0.0.2.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
06b1bc5cccb58e4ea77a8e6928ebed3867e8f202af1efb4dda6be2a1c292df9a
|
|
BLAKE2b-256 checksum How to use checksums |
b094779fbec2c77aa48347e060d11b97c103596e302090740942bcde31552daf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.0 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.12
|
Release files / the_nordic_pile-0.0.2-py3-none-any.whl
| Download URL | the_nordic_pile-0.0.2-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
16b4506c51f69a9e8220753ec325bcee312fe4be9750e4d1ba2811c5e7e24845
|
|
BLAKE2b-256 checksum How to use checksums |
4a37ef14f7915026c6c22691fc80dfb8a2cad4b2c705b6b673cc3fa8c921a0b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.0 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.12
|
Security for the-nordic-pile 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.