upload_instructions

#49
by Saauan - opened
Files changed (1) hide show
  1. README.md +107 -26
README.md CHANGED
@@ -2,24 +2,101 @@
2
  license: apache-2.0
3
  ---
4
 
 
 
 
 
 
 
 
 
 
 
 
 
5
  # Guide: How to share your data on the BoAmps repository
6
 
7
- This guide explains step by step how to share BoAmps format reports on this public Hugging Face repository.
 
 
8
 
9
  ## Table of Contents
 
 
10
  - [Guide: How to share your data on the BoAmps repository](#guide-how-to-share-your-data-on-the-boamps-repository)
11
  - [Table of Contents](#table-of-contents)
12
- - [Prerequisites](#prerequisites)
13
- - [Method 1: Hugging Face Web Interface](#method-1-hugging-face-web-interface)
14
- - [Method 2: Git (Command Line)](#method-2-git-command-line)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
15
 
16
- ## Prerequisites
 
 
 
17
 
18
- Before starting, make sure you have:
19
- - A Hugging Face account
20
- - The files you want to upload
21
 
22
- ## Method 1: Hugging Face Web Interface
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
23
 
24
  1. Log in to Hugging Face
25
  2. Go to [the boamps dataset](https://huggingface.co/datasets/boavizta/open_data_boamps)
@@ -27,25 +104,29 @@ Before starting, make sure you have:
27
  ![Access to files](screenshots/01-access-repository.png)
28
  ![Access to data folder](screenshots/02-access-data-files.png)
29
  4. Click on "Contribute" then "Upload files"
30
- ![Contribute](screenshots/03-upload-files.png)
31
-
32
- 5. Drop your files in BoAmps format (please name them clearly) and give a name to the PR (e.g. 10 reports on image classification). You can add an extended description but this is optional.
33
- The name of the files should follow this format :
34
- "report_\<publisher>_\<taskStage>_\<taskFamily>_\<infraType>_\<reportID>.json"
35
- - \<publisher>: the name of the publisher (this can be useful for gathering reports written by the same person, but you can of course create a pseudonym if you wish to remain anonymous)
36
- - \<taskStage>: mandatory field of the report
37
- - \<taskFamily>: mandatory field of the report
38
- - \<infraType>: mandatory field of the report
39
- - \<reportID>: optionnal
40
 
41
- 1. At the bottom of the page, click on "Open a Pull Request".
42
- 2. You should see your PR created in "Community" > "Pull request". Now just wait for our team to validate your PR, thank you very much for your participation and your commitment to more frugal AI, in full transparency!
43
- ![Consult](screenshots/04-consult-PR.png)
 
44
 
45
-
46
- ## Method 2: Git (Command Line)
47
 
48
  1. Clone the repository
49
  2. Create a branch
50
- 3. Add your files
51
- 4. Create a PR
 
 
 
 
 
 
 
 
 
 
 
 
 
 
2
  license: apache-2.0
3
  ---
4
 
5
+ # BoAmps open data repository
6
+
7
+ ## What is this repository?
8
+
9
+ This is the **open database of BoAmps reports**: a public collection of measurements of the energy consumption and environmental impact of AI workloads (inference, training, validation, etc.).
10
+
11
+ [BoAmps](https://github.com/Boavizta/BoAmps) is an open project by [Boavizta](https://boavizta.org/) that defines a **standard format** for reporting these measurements, so that data coming from different teams, hardware, and models can be compared and aggregated. Each entry in this repository is a report following that format: a JSON file describing *what* was run, on *which* hardware, and *how much energy* it actually measured.
12
+
13
+ A key principle: every report is based on **real, physical measurements** (via `nvidia-smi`, CodeCarbon, power meters, etc.). This is what makes the dataset a reliable, transparent basis for studying the footprint of AI.
14
+
15
+ The rest of this document is a guide for contributors who want to add their own reports.
16
+
17
  # Guide: How to share your data on the BoAmps repository
18
 
19
+ This guide explains step by step how to share BoAmps format reports on this public Hugging Face repository.
20
+
21
+ It follows the journey of a contributor: first checking whether your data is eligible, then producing and validating a report, structuring your contribution, and finally submitting it.
22
 
23
  ## Table of Contents
24
+ - [BoAmps open data repository](#boamps-open-data-repository)
25
+ - [What is this repository?](#what-is-this-repository)
26
  - [Guide: How to share your data on the BoAmps repository](#guide-how-to-share-your-data-on-the-boamps-repository)
27
  - [Table of Contents](#table-of-contents)
28
+ - [Step 1: Is my data eligible?](#step-1-is-my-data-eligible)
29
+ - [Step 2: Create and validate a report](#step-2-create-and-validate-a-report)
30
+ - [Step 3: Structure your contribution](#step-3-structure-your-contribution)
31
+ - [Step 4: Submit your contribution](#step-4-submit-your-contribution)
32
+ - [Method 1: Hugging Face Web Interface](#method-1-hugging-face-web-interface)
33
+ - [Method 2: Git (Command Line)](#method-2-git-command-line)
34
+ - [If BoAmps doesn't fit your data](#if-boamps-doesnt-fit-your-data)
35
+ - [Useful links](#useful-links)
36
+
37
+ ## Step 1: Is my data eligible?
38
+
39
+ Before investing time in a conversion, check that your data is a good fit for BoAmps:
40
+
41
+ - **The energy must be measured, not estimated.** BoAmps needs real measurements taken with tools such as `nvidia-smi`, CodeCarbon, a power meter, etc. If the energy consumption is *estimated* or *calculated* (for example with EcoLogits) rather than physically measured, it is **not** compatible with BoAmps.
42
+ - **The data must relate to AI.** The measurement should concern an AI workload: inference, training, validation, and so on.
43
+
44
+ If your data does not meet both criteria, it is unfortunately not a fit for this repository.
45
+
46
+ ## Step 2: Create and validate a report
47
+
48
+ Producing a valid report happens in three phases: mapping, conversion, and validation.
49
+
50
+ **1. Mapping.** On paper or in a working file, before writing any report:
51
+ - **Decide the scope of a report.** Depending on the source, it is often better to produce several reports with finer granularity — especially when the configuration (hardware, model) changes. Conversely, when there are many small consecutive measurements, a single report may be more appropriate. Helpful boundaries: the AI model changes, the dataset changes, the hardware changes, or the day changes (for a service measured over the long term, one report per day is reasonable). Sometimes it is as simple as *"one row of the CSV = one report"*.
52
+ - **Map each source field to a BoAmps field.** Note any conversion or computation needed (in particular unit conversions for energy or duration).
53
+ - **Identify static fields.** Some BoAmps fields may be identical across all your reports (e.g. hardware, publisher). Note them so you can reuse them.
54
+
55
+ The BoAmps field definitions live in the [`model/` folder of the BoAmps repository](https://github.com/Boavizta/BoAmps/tree/main/model) — each JSON file defines part of the schema.
56
 
57
+ **2. Conversion.** From the mapping above, convert your source data into BoAmps reports using one of:
58
+ - **Method 1 (recommended): write a Python conversion script.** See the [examples on GitHub](https://github.com/Boavizta/BoAmps/tree/main/examples). Keeping the script lets us regenerate the reports if the BoAmps model evolves.
59
+ - **Method 2: write the reports manually** or via the [online form](https://huggingface.co/spaces/soprasteria/BoAmps_report_creation).
60
+ - **Method 3:** if you are taking the measurements yourself, produce the reports directly from your measurement pipeline.
61
 
62
+ **3. Validation.** Check that your reports are well-formed with the [JSON schema validator](https://github.com/Boavizta/BoAmps/tree/main/tools/schema_validator) before submitting. This avoids back-and-forth during review.
 
 
63
 
64
+ **File naming.** Name each report file clearly, following this format:
65
+
66
+ `report_<publisher>_<taskStage>_<taskFamily>_<infraType>_<reportID>.json`
67
+
68
+ - `<publisher>`: the name of the publisher (useful for gathering reports written by the same person — you may use a pseudonym if you wish to remain anonymous)
69
+ - `<taskStage>`: mandatory field of the report
70
+ - `<taskFamily>`: mandatory field of the report
71
+ - `<infraType>`: mandatory field of the report
72
+ - `<reportID>`: optional
73
+
74
+ ## Step 3: Structure your contribution
75
+
76
+ Create a new subfolder inside `data/`, named after your source (for a public source, the name of the paper; for a private source, the organisation name plus a unique identifier for this dataset). That subfolder should contain:
77
+
78
+ ```
79
+ data/<source-name>/
80
+ ├── reports/ (MANDATORY) one or more reports in BoAmps format
81
+ ├── source_info.md (MANDATORY) a short description of the source
82
+ ├── source_data/ (OPTIONAL) the raw source data before conversion
83
+ └── conversion.py (OPTIONAL) the conversion script, if you used one
84
+ ```
85
+
86
+ - **`reports/`** - the report(s) in BoAmps format, named as described above. **(mandatory)**
87
+ - **`source_info.md`** - a brief description of: **(mandatory)**
88
+ - the type of data that was converted,
89
+ - the original authors of the data / attribution,
90
+ - the person(s) who performed the conversion,
91
+ - any conversion issues related to BoAmps (missing fields, data not detailed enough, etc.).
92
+ - **`source_data/`** - the source data before conversion (CodeCarbon CSV, the paper's dataset, data extracted from figures and tables, etc.). *(optional)*
93
+ - **`conversion.py`** - the conversion script, if the conversion was scripted. *(optional)*
94
+
95
+ Including the source data and the conversion script helps us regenerate the reports if the BoAmps model changes.
96
+
97
+ ## Step 4: Submit your contribution
98
+
99
+ ### Method 1: Hugging Face Web Interface
100
 
101
  1. Log in to Hugging Face
102
  2. Go to [the boamps dataset](https://huggingface.co/datasets/boavizta/open_data_boamps)
 
104
  ![Access to files](screenshots/01-access-repository.png)
105
  ![Access to data folder](screenshots/02-access-data-files.png)
106
  4. Click on "Contribute" then "Upload files"
107
+ ![Contribute](screenshots/03-upload-files.png)
 
 
 
 
 
 
 
 
 
108
 
109
+ 5. Upload your files following the structure from [Step 3](#step-3-structure-your-contribution). To place a file inside your source subfolder, prefix its name with the folder path (e.g. `<source-name>/reports/report_....json`) in the upload dialog. Give a name to the PR (e.g. *10 reports on image classification*). You can add an extended description, but this is optional.
110
+ 6. At the bottom of the page, click on "Open a Pull Request".
111
+ 7. You should see your PR created in "Community" > "Pull request". Now just wait for our team to validate your PR. Thank you very much for your participation and your commitment to more frugal AI, in full transparency!
112
+ ![Consult](screenshots/04-consult-PR.png)
113
 
114
+ ### Method 2: Git (Command Line)
 
115
 
116
  1. Clone the repository
117
  2. Create a branch
118
+ 3. Add your files, following the folder structure from [Step 3](#step-3-structure-your-contribution)
119
+ 4. Commit, push, and open a Pull Request
120
+
121
+ ## If BoAmps doesn't fit your data
122
+
123
+ If, during a conversion, at least one software, hardware, algorithmic, or other characteristic (data characterisation, etc.) does not seem to map onto an existing BoAmps field, please [contact us](https://github.com/Boavizta/BoAmps/issues) to discuss possible evolutions of the model.
124
+
125
+ ## Useful links
126
+
127
+ - **BoAmps model & tools (GitHub):** https://github.com/Boavizta/BoAmps
128
+ - **Field definitions (schema):** https://github.com/Boavizta/BoAmps/tree/main/model
129
+ - **Example reports & conversion scripts:** https://github.com/Boavizta/BoAmps/tree/main/examples
130
+ - **JSON schema validator:** https://github.com/Boavizta/BoAmps/tree/main/tools/schema_validator
131
+ - **Documentation (WIP):** https://boavizta.github.io/BoAmps/
132
+ - **Online report creation form:** https://huggingface.co/spaces/soprasteria/BoAmps_report_creation