Update README.md with new sub-datasets

README.md

@@ -12,6 +12,10 @@ pretty_name: Chameleon
 size_categories:
 - 1K<n<10K
 configs:
+- config_name: BASE
+  data_files: "BASE/*.h5" 
+- config_name: DFS_MRP
+  data_files: "DFS_MRP/*.h5" 
 - config_name: DFS
   data_files: "DFS/*.h5"
 - config_name: RD
@@ -25,9 +29,10 @@ configs:
 # Chameleon
 
 The `Chameleon` is a dataset designed for side-channel analysis of obfuscated power traces. 
-It contains real-world power traces collected from a 32-bit RISC-V System-on-Chip 
-implementing four hiding countermeasures: Dynamic Frequency Scaling (DFS), 
-Random Delay (RD), Morphing (MRP), and Chaffing (CHF). 
+It contains real-world power traces collected from a 32-bit RISC-V System-on-Chip implementing four hiding countermeasures: 
+Dynamic Frequency Scaling (DFS), Random Delay (RD), Morphing (MRP), and Chaffing (CHF).
+The dataset includes side-channel power traces without any active countermeasure (BASE)
+as well as the combination of Dynamic Frequency Scaling and Morphing (DFS_MRP).
 Each side-channel trace includes multiple cryptographic operations 
 interleaved with general-purpose applications.
 
@@ -57,13 +62,15 @@ from datasets import load_dataset
 
 sub_dataset = load_dataset("hardware-fab/Chameleon", '<sub_dataset>')
 ```
-Replace `<sub_dataset>` with `DFS`, `RD`, `MRP`, or `CHF`.
+Replace `<sub_dataset>` with `BASE`, `DFS`, `RD`, `MRP`, `CHF`, or `DFS_MRP`.
 
 ## Dataset Structure
 
 The dataset is divided per hiding countermeasure. Each file has the following structure:
-* **Data:** The data are power traces of 134,217,550 time samples. DFS, RD, MRP, and CHF datasets
- contain 256, 512, 512, and 1024 data respectively. The traces capture the SoC execution of AES encryptions interleaved with general-purpose applications.
+* **Data:** The data are power traces of 134,217,550 time samples.
+ BASE, DFS, RD, MRP, CHF, and DFS_MRP sub-dataset
+ contain 256, 256, 512, 512, 1024, and 256 data respectively.
+ The traces capture the SoC execution of AES encryptions interleaved with general-purpose applications.
 * **Metadata:** The metadata are divided into three groups:
   * **Ciphers:** This group contains the AES inputs:
     * `key`: The secret key used for AES encryption.
@@ -71,7 +78,8 @@ The dataset is divided per hiding countermeasure. Each file has the following st
   * **Pinpoints:** This group contains the start and end time samples of each AES execution in each trace file.
     * `start`: The starting sample of the AES encryption. It takes values ranging from 0 to 134,217,550.
     * `end`: The ending sample of the AES encryption. It takes values ranging from 0 to 134,217,550.
-  * **Frequencies:** This group provides labels for each power trace, indicating the frequency changes during the measurement. _Notably, this metadata is only available for the DFS dataset_.Each metadata has two fields:
+  * **Frequencies:** This group provides labels for each power trace, indicating the frequency changes during the measurement.
+      _Notably, this metadata is only available for the sub-datasets with DFS enabled_. Each metadata has two fields:
     * `samples`: This field denotes the time sample at which a frequency change happens, with integer values ranging from 0 to 134,217,550.
     * `frequencies`: This field specifies the new operating frequency starting from the corresponding sample. It can take floating values from 5MHz to 100MHz.
 
@@ -85,6 +93,22 @@ keeping the remaining 15 fixed.
 
 | Chunk          | First key byte values | Disk size (GB) | # Data  |
 |----------------|----------------|----------------|----------------|
+| base_chunk_1.h5  | [0x00-0x0f] | 4.3  | 16 |  
+| base_chunk_2.h5  | [0x10-0x0f] | 4.3  | 16 |  
+| base_chunk_3.h5  | [0x20-0x2f] | 4.3  | 16 |  
+| base_chunk_4.h5  | [0x30-0x3f] | 4.3  | 16 |  
+| base_chunk_5.h5  | [0x40-0x4f] | 4.3  | 16 |  
+| base_chunk_6.h5  | [0x50-0x5f] | 4.3  | 16 |  
+| base_chunk_7.h5  | [0x60-0x6f] | 4.3  | 16 |  
+| base_chunk_8.h5  | [0x70-0x7f] | 4.3  | 16 |  
+| base_chunk_9.h5  | [0x80-0x8f] | 4.3  | 16 |  
+| base_chunk_10.h5 | [0x90-0x9f] | 4.3  | 16 |  
+| base_chunk_11.h5 | [0xa0-0xaf] | 4.3  | 16 |  
+| base_chunk_12.h5 | [0xb0-0xbf] | 4.3  | 16 |  
+| base_chunk_13.h5 | [0xc0-0xcf] | 4.3  | 16 |  
+| base_chunk_14.h5 | [0xd0-0xdf] | 4.3  | 16 |  
+| base_chunk_15.h5 | [0xe0-0xef] | 4.3  | 16 |  
+| base_chunk_16.h5 | [0xf0-0xff] | 4.3  | 16 |
 | dfs_chunk_1.h5  | [0x00-0x0f] | 4.3  | 16 |  
 | dfs_chunk_2.h5  | [0x10-0x0f] | 4.3  | 16 |  
 | dfs_chunk_3.h5  | [0x20-0x2f] | 4.3  | 16 |  
@@ -149,6 +173,22 @@ keeping the remaining 15 fixed.
 | chf_chunk_14.h5 | [0xd0-0xdf] | 17.2 | 64 |  
 | chf_chunk_15.h5 | [0xe0-0xef] | 17.2 | 64 |  
 | chf_chunk_16.h5 | [0xf0-0xff] | 17.2 | 64 |
+| dfs_mrp_chunk_1.h5  | [0x00-0x0f] | 4.3  | 16 |  
+| dfs_mrp_chunk_2.h5  | [0x10-0x0f] | 4.3  | 16 |  
+| dfs_mrp_chunk_3.h5  | [0x20-0x2f] | 4.3  | 16 |  
+| dfs_mrp_chunk_4.h5  | [0x30-0x3f] | 4.3  | 16 |  
+| dfs_mrp_chunk_5.h5  | [0x40-0x4f] | 4.3  | 16 |  
+| dfs_mrp_chunk_6.h5  | [0x50-0x5f] | 4.3  | 16 |  
+| dfs_mrp_chunk_7.h5  | [0x60-0x6f] | 4.3  | 16 |  
+| dfs_mrp_chunk_8.h5  | [0x70-0x7f] | 4.3  | 16 |  
+| dfs_mrp_chunk_9.h5  | [0x80-0x8f] | 4.3  | 16 |  
+| dfs_mrp_chunk_10.h5 | [0x90-0x9f] | 4.3  | 16 |  
+| dfs_mrp_chunk_11.h5 | [0xa0-0xaf] | 4.3  | 16 |  
+| dfs_mrp_chunk_12.h5 | [0xb0-0xbf] | 4.3  | 16 |  
+| dfs_mrp_chunk_13.h5 | [0xc0-0xcf] | 4.3  | 16 |  
+| dfs_mrp_chunk_14.h5 | [0xd0-0xdf] | 4.3  | 16 |  
+| dfs_mrp_chunk_15.h5 | [0xe0-0xef] | 4.3  | 16 |  
+| dfs_mrp_chunk_16.h5 | [0xf0-0xff] | 4.3  | 16 |  
 
 Following the structure of the dataset, below are HDF5 fields used and their atomic type: 
 
@@ -209,7 +249,7 @@ that has been modified to implement the analyzed hiding methods. In particular,
 we implement random delay and dynamic frequency scaling in hardware,
 while morphing and chaffing are software-implemented. Notably, 
 the CPU is clocked at 50MHz for all acquisition campaigns, 
-except for the DFS one, for which the DFS actuator 
+except for the DFS ones, for which the DFS actuator 
 is instructed to change the operating frequency of
 the computing platform randomly at its maximum speed.