BSC-LT
/

salamandra-2b-instruct-aina-hack

@@ -45,7 +45,7 @@ base_model:
 ![](./images/salamandra_header.png)
-# Salamandra Model Card
 Salamandra is a highly multilingual model pre-trained from scratch that comes in three different
 sizes — 2B, 7B and 40B parameters — with their respective base and instruction-tuned variants.
@@ -212,259 +212,6 @@ The remaining 10% comes from smaller sources in various languages.
 The model was trained for 3 epochs, with two final rounds of 0.3B higher-quality tokens each,
 meaning that the total number of tokens seen during pre-training amounts to roughly 7.8 trillion tokens.
-We provide an extense Datasheet section following the best practices defined by [(Gebru et al., 2021)](https://arxiv.org/pdf/1803.09010).
-<details>
-<summary>Datasheet</summary>
-#### Motivation
-**For what purpose was the dataset created? Was there a specific task in mind? Was there a specific gap that needed to be filled? Please provide a description.**
-The purpose of creating this dataset is to pre-train the Salamandra family of multilingual models with high performance in a large number of
-European languages (35) and code (including 92 different programming languages). In addition, we aim to represent especially the co-official
-languages of Spain: Spanish, Catalan, Galician, and Basque. This is the reason why we carry out an oversampling of these languages.
-We detected that there is a great lack of massive multilingual data, especially in minority languages (Ostendorff & Rehm, 2023), so part of
-our efforts in the creation of this pre-training dataset have resulted in the contribution to large projects such as the Community OSCAR
-(Brack et al., 2024), which includes 151 languages and 40T words, or CATalog (Palomar-Giner et al., 2024), the largest open dataset in
-Catalan in the world.
-**Who created the dataset (e.g., which team, research group) and on behalf of which entity (e.g., company, institution, organization)?**
-The dataset has been created by the Language Technologies unit (LangTech) of the Barcelona Supercomputing Center - Centro Nacional de
-Supercomputación (BSC-CNS), which aims to advance the field of natural language processing through cutting-edge research and development
-and the use of HPC. In particular, it was created by the unit's data team, the main contributors being Javier Saiz, Ferran Espuña, and
-Jorge Palomar.
-However, the creation of the dataset would not have been possible without the collaboration of a large number of collaborators, partners,
-and public institutions, which can be found in detail in the acknowledgements.
-**Who funded the creation of the dataset? If there is an associated grant, please provide the name of the grantor and the grant name and number.**
-This work/research has been promoted and financed by the Government of Catalonia through the [Aina project](https://projecteaina.cat/).
-#### Composition
-**What do the instances that comprise the dataset represent (e.g., documents, photos, people, countries)? Are there multiple types of instances (e.g., movies, users, and ratings; people and interactions between them; nodes and edges)? Please provide a description.**
-The dataset consists entirely of text documents in various languages. Specifically, data was mainly sourced from the following databases and
-repositories:
-- **Common Crawl:** Repository that holds website data and is run by the Common Crawl non-profit organization. It is updated monthly and is
-  distributed under the CC0 1.0 public domain license.
-- **GitHub:** Community platform that allows developers to create, store, manage, and share their code. Repositories are crawled and then
-  distributed with their original licenses, which may vary from permissive to non-commercial licenses.
-- **Wikimedia:** Database that holds the collection databases managed by the Wikimedia Foundation, including Wikipedia, Wikibooks, Wikinews,
-  Wikiquote, Wikisource, and Wikivoyage. It is updated monthly and is distributed under Creative Commons Attribution-ShareAlike License 4.0.
-- **EurLex:** Repository that holds the collection of legal documents from the European Union, available in all of the EU’s 24 official
-  languages and run by the Publications Office of the European Union. It is updated daily and is distributed under the Creative Commons
-  Attribution 4.0 International license.
-- **Other repositories:** Specific repositories were crawled under permission for domain-specific corpora, which include academic, legal,
-  and newspaper repositories.
-We provide a complete list of dataset sources at the end of this section.
-**How many instances are there in total (of each type, if appropriate)?**
-The dataset contains a diverse range of instances across multiple languages, with notable adjustments for certain languages. English
-represents the largest portion, accounting for 39.08% of the total data. Spanish was upsampled by a factor of 2, bringing its share to 16.59%,
-while Catalan (1.84%), Basque (0.26%), and Galician (0.36%) were also upsampled by 2. On the other hand, code-related data was downsampled
-by half, making up 6.42% of the total. Other prominent languages include French (6.59%), Russian (5.39%), German (4.25%), and Hungarian
-(3.93%), with several additional languages contributing between 1% and 2%, and smaller portions represented by a variety of others.
-**Does the dataset contain all possible instances or is it a sample (not necessarily random) of instances from a larger set? If the dataset is a sample, then what is the larger set? Is the sample representative of the larger set (e.g., geographic coverage)? If so, please describe how this representativeness was validated/verified. If it is not representative of the larger set, please describe why not (e.g., to cover a more diverse range of instances, because instances were withheld or unavailable).**
-The dataset is a sample from multiple sources, with different weights based on the primary language of the content: Spanish, Catalan,
-Basque, and Galician content was upsampled by a factor of two, while programming languages were downsampled by a factor of half. Other
-sources were sampled in proportion to their occurrence.
-**What data does each instance consist of? “Raw” data (e.g., unprocessed text or images) or features? In either case, please provide a description.**
-Each instance consists of a text document processed for deduplication, language identification, and source-specific filtering. Some
-documents required optical character recognition (OCR) to extract text from non-text formats such as PDFs.
-**Is there a label or target associated with each instance? If so, please provide a description.**
-Each instance is labeled with a unique identifier, the primary language of the content, and the URL for web-sourced instances. Additional
-labels were automatically assigned to detect specific types of content —harmful or toxic content— and to assign preliminary indicators of
-undesired qualities —very short documents, high density of symbols, etc.— which were used for filtering instances.
-**Is any information missing from individual instances? If so, please provide a description, explaining why this information is missing (e.g., because it was unavailable). This does not include intentionally removed information, but might include, e.g., redacted text.**
-No significant information is missing from the instances.
-**Are relationships between individual instances made explicit (e.g., users’ movie ratings, social network links)? If so, please describe how these relationships are made explicit.**
-Instances are related through shared metadata, such as source and language identifiers.
-**Are there recommended data splits (e.g., training, development/validation, testing)? If so, please provide a description of these splits, explaining the rationale behind them.**
-The dataset is split randomly into training, validation, and test sets.
-**Are there any errors, sources of noise, or redundancies in the dataset? If so, please provide a description.**
-Despite removing duplicated instances within each source, redundancy remains at the paragraph and sentence levels, particularly in
-web-sourced instances where SEO techniques and templates contribute to repeated textual patterns. Some instances may also be duplicated
-across sources due to format variations.
-**Is the dataset self-contained, or does it link to or otherwise rely on external resources (e.g., websites, tweets, other datasets)? If it links to or relies on external resources, a) are there guarantees that they will exist, and remain constant, over time; b) are there official archival versions of the complete dataset (i.e., including the external resources as they existed at the time the dataset was created); c) are there any restrictions (e.g., licenses, fees) associated with any of the external resources that might apply to a dataset consumer? Please provide descriptions of all external resources and any restrictions associated with them, as well as links or other access points, as appropriate.**
-The dataset is self-contained and does not rely on external resources.
-**Does the dataset contain data that might be considered confidential (e.g., data that is protected by legal privilege or by doctor–patient confidentiality, data that includes the content of individuals’ non-public communications)? If so, please provide a description.**
-The dataset does not contain confidential data.
-**Does the dataset contain data that, if viewed directly, might be offensive, insulting, threatening, or might otherwise cause anxiety? If so, please describe why. If the dataset does not relate to people, you may skip the remaining questions in this section.**
-The dataset includes web-crawled content, which may overrepresent pornographic material across languages (Kreutzer et al., 2022). Although
-pre-processing techniques were applied to mitigate offensive content, the heterogeneity and scale of web-sourced data make exhaustive
-filtering challenging, which makes it next to impossible to identify all adult content without falling into excessive filtering, which may
-negatively influence certain demographic groups (Dodge et al., 2021).
-**Does the dataset identify any subpopulations (e.g., by age, gender)? If so, please describe how these subpopulations are identified and provide a description of their respective distributions within the dataset.**
-The dataset does not explicitly identify any subpopulations.
-**Is it possible to identify individuals (i.e., one or more natural persons), either directly or indirectly (i.e., in combination with other data) from the dataset? If so, please describe how.**
-Web-sourced instances in the dataset may contain personally identifiable information (PII) that is publicly available on the Web, such as
-names, IP addresses, email addresses, and phone numbers. While it would be possible to indirectly identify individuals through the
-combination of multiple data points, the nature and scale of web data makes it difficult to parse such information. In any case, efforts are
-made to filter or anonymize sensitive data during pre-processing, but some identifiable information may remain in the dataset.
-**Does the dataset contain data that might be considered sensitive in any way? If so, please provide a description.**
-Given that the dataset includes web-sourced content and other publicly available documents, instances may inadvertently reveal financial
-information, health-related details, or forms of government identification, such as social security numbers (Subramani et al., 2023),
-especially if the content originates from less-regulated sources or user-generated platforms.
-#### Collection Process
-**How was the data collected?**
-This dataset is constituted by combining several sources, whose acquisition methods can be classified into three groups:
-- Web-sourced datasets with some preprocessing available under permissive license (p.e. Common Crawl).
-- Domain-specific or language-specific raw crawls (p.e. Spanish Crawling).
-- Manually curated data obtained through collaborators, data providers (by means of legal assignment agreements) or open source projects
-  (p.e. CATalog).
-**What mechanisms or procedures were used to collect the data? How were these mechanisms or procedures validated?**
-According to the three groups previously defined, these are the mechanisms used in each of them:
-- Open direct download. Validation: data integrity tests.
-- Ad-hoc scrapers or crawlers. Validation: software unit and data integrity tests.
-- Direct download via FTP, SFTP, API or S3. Validation: data integrity tests.
-**If the dataset is a sample from a larger set, what was the sampling strategy?**
-The sampling strategy was to use the whole dataset resulting from the filtering explained in the ‘preprocessing/cleaning/labelling’ section,
-with the particularity that an upsampling of 2 (i.e. twice the probability of sampling a document) was performed for the co-official
-languages of Spain (Spanish, Catalan, Galician, Basque), and a downsampling of 1/2 was applied for code (half the probability of sampling a
-code document, evenly distributed among all programming languages).
-**Who was involved in the data collection process and how were they compensated?**
-This data is generally extracted, filtered and sampled by automated processes. The code required to run these processes has been developed
-entirely by members of the LangTech data team, or otherwise obtained from open-source software. Furthermore, there has been no monetary
-consideration for acquiring data from suppliers.
-**Over what timeframe was the data collected? Does this timeframe match the creation timeframe of the data associated with the instances? If not, please describe the timeframe in which the data associated with the instances was created.**
-Data were acquired and processed from April 2023 to April 2024. However, as mentioned, much data has been obtained from open projects such
-as Common Crawl, which contains data from 2014, so it is the end date (04/2024) rather than the start date that is important.
-**Were any ethical review processes conducted? If so, please provide a description of these review processes, including the outcomes, as well as a link or other access point to any supporting documentation.**
-No particular ethical review process has been carried out as the data is mostly open and not particularly sensitive. However, we have an
-internal evaluation team and a bias team to monitor ethical issues. In addition, we work closely with ‘Observatori d'Ètica en Intel·ligència
-Artificial’ (OEIAC) and  ‘Agencia Española de Supervisión de la Inteligencia Artificial’ (AESIA) to audit the processes we carry out from an
-ethical and legal point of view, respectively.
-#### Preprocessing
-**Was any preprocessing/cleaning/labeling of the data done? If so, please provide a description. If not, you may skip the remaining questions in this section.**
-Instances of text documents were not altered, but web-sourced documents were filtered based on specific criteria along two dimensions:
-- Quality: documents with a score lower than 0.8, based on undesired qualities, such as documents with low number of lines, very short
-  sentences, presence of long footers and headers, and high percentage of punctuation, obtained through CURATE (Palomar-Giner et al., 2024)
-  were filtered out.
-- Harmful or adult content: documents originating from Colossal OSCAR were filtered using LLM-Datasets (Ostendorff et al., 2024) based on
-  the perplexity from a language model (‘harmful_pp’ field) provided by the Ungoliant pipeline (Abadji et al., 2021).
-**Was the “raw” data saved in addition to the preprocessed/cleaned/labeled data? If so, please provide a link or other access point to the “raw” data.**
-The original raw data was not kept.
-**Is the software that was used to preprocess/clean/label the data available? If so, please provide a link or other access point.**
-Yes, the preprocessing and filtering software is open-sourced. The [CURATE](https://github.com/langtech-bsc/CURATE) pipeline was used for Spanish Crawling and CATalog,
-and the [Ungoliant](https://github.com/oscar-project/ungoliant) pipeline was used for the OSCAR project.
-#### Uses
-**Has the dataset been used for any tasks already? If so, please provide a description.**
-Pre-train the Salamandra model family.
-**What (other) tasks could the dataset be used for?**
-The data can be used primarily to pre-train other language models, which can then be used for a wide range of use cases. The dataset could
-also be used for other tasks such as fine-tuning language models, cross-lingual NLP tasks, machine translation, domain-specific text
-generation, and language-specific data analysis.
-**Is there anything about the composition of the dataset or the way it was collected and preprocessed/cleaned/labeled that might impact future uses? Is there anything a dataset consumer could do to mitigate these risks or harms?**
-Web-crawled content is over-represented with standard language varieties, impacting language model performance for minority languages.
-Language diversity in data is crucial to avoid bias, especially in encoding non-standard dialects, preventing the exclusion of demographic
-groups. Moreover, despite legal uncertainties in web-scraped data, we prioritize permissive licenses and privacy protection measures,
-acknowledging the challenges posed by personally identifiable information (PII) within large-scale datasets. Our ongoing efforts aim to
-address privacy concerns and contribute to a more inclusive linguistic dataset.
-**Are there tasks for which the dataset should not be used?**
--
-#### Distribution
-**Will the dataset be distributed to third parties outside of the entity on behalf of which the dataset was created? If so, please provide a description.**
-The dataset will not be released or distributed to third parties. Any related question to distribution is omitted in this section.
-#### Maintenance
-**Who will be supporting/hosting/maintaining the dataset?**
-The dataset will be hosted by the Language Technologies unit (LangTech) of the Barcelona Supercomputing Center (BSC). The team will ensure
-regular updates and monitor the dataset for any issues related to content integrity, legal compliance, and bias for the sources they are
-responsible for.
-**How can the owner/curator/manager of the dataset be contacted?**
-The data owner may be contacted with the email address langtech@bsc.es.
-**Will the dataset be updated?**
-The dataset will not be updated.
-**If the dataset relates to people, are there applicable limits on the retention of the data associated with the instances? If so, please describe these limits and explain how they will be enforced.**
-The dataset does not keep sensitive data that could allow direct identification of individuals, apart from the data that is publicly
-available in web-sourced content. Due to the sheer volume and diversity of web data, it is not feasible to notify individuals or manage data
-retention on an individual basis. However, efforts are made to mitigate the risks associated with sensitive information through
-pre-processing and filtering to remove identifiable or harmful content. Despite these measures, vigilance is maintained to address potential
-privacy and ethical issues.
-**Will older versions of the dataset continue to be supported/hosted/maintained? If so, please describe how. If not, please describe how its obsolescence will be communicated to dataset consumers.**
-Since the dataset will not be updated, only the final version will be kept.
-**If others want to extend/augment/build on/contribute to the dataset, is there a mechanism for them to do so?**
-The dataset does not allow for external contributions.
-</details>
 ### Finetuning Data
 This instruction-tuned variant has been trained with a mixture of 276k English, Spanish, and Catalan multi-turn instructions gathered from open datasets:

 ![](./images/salamandra_header.png)
+# Salamandra Model Card (Aina Hack)
 Salamandra is a highly multilingual model pre-trained from scratch that comes in three different
 sizes — 2B, 7B and 40B parameters — with their respective base and instruction-tuned variants.
 The model was trained for 3 epochs, with two final rounds of 0.3B higher-quality tokens each,
 meaning that the total number of tokens seen during pre-training amounts to roughly 7.8 trillion tokens.
 ### Finetuning Data
 This instruction-tuned variant has been trained with a mixture of 276k English, Spanish, and Catalan multi-turn instructions gathered from open datasets: