Datasets:
Update README.md
Browse files
README.md
CHANGED
|
@@ -31,4 +31,73 @@ configs:
|
|
| 31 |
path: data/original-*
|
| 32 |
- split: augmented
|
| 33 |
path: data/augmented-*
|
|
|
|
|
|
|
|
|
|
| 34 |
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 31 |
path: data/original-*
|
| 32 |
- split: augmented
|
| 33 |
path: data/augmented-*
|
| 34 |
+
license: cc
|
| 35 |
+
language:
|
| 36 |
+
- en
|
| 37 |
---
|
| 38 |
+
|
| 39 |
+
# Model Card - Beverage Energy Tracker Dataset
|
| 40 |
+
|
| 41 |
+
## Purpose
|
| 42 |
+
This dataset was created to analyze and model the energy related characteristics of common beverages based on measurable features. It is intended for educational and experimental machine learning use cases, such as binary classification and feature importance analysis.
|
| 43 |
+
|
| 44 |
+
## Composition
|
| 45 |
+
The dataset contains:
|
| 46 |
+
- 30 manually collected real world samples in the `original` split
|
| 47 |
+
- 300 label preserving synthetic samples in the `augmented` split
|
| 48 |
+
Each sample includes:
|
| 49 |
+
- 5 input features (category, Added sugar(g), Calories, Volume, Energy rating)
|
| 50 |
+
- 1 binary target variable indicating the sugar level (is high sugar?)
|
| 51 |
+
|
| 52 |
+
## Collection
|
| 53 |
+
Data was manually gathered from the product description pages of:
|
| 54 |
+
- Starbucks
|
| 55 |
+
- ALDI USA
|
| 56 |
+
- MarketDistrict
|
| 57 |
+
- Amazon
|
| 58 |
+
- Walmart
|
| 59 |
+
|
| 60 |
+
Feature values such as sugar content, calories, volume and category were noted for each drink. Energy rating collected from consumers (Friends). The binary target (`is_high_sugar?`) was assigned based on sugar content (0 if <20g).
|
| 61 |
+
|
| 62 |
+
## Preprocessing & Augmentation
|
| 63 |
+
- Basic preprocessing: cleaned column names, ensured numerical features were floats/integers.
|
| 64 |
+
- For augmentation, **label preserving jitter techniques** were used:
|
| 65 |
+
- Gaussian noise was added to continuous features (`Added sugar (g)`, `Calories`).
|
| 66 |
+
- ±1 encoding step changes applied to the integer feature (`Energy rating`), clipped to valid bounds (1-5).
|
| 67 |
+
- Categorical fields (`Beverage type`, `Volume`) were left unchanged to preserve label consistency.
|
| 68 |
+
- This process expanded the dataset to 300 augmented samples.
|
| 69 |
+
|
| 70 |
+
|
| 71 |
+
## Labels
|
| 72 |
+
- **Features:**
|
| 73 |
+
- `Beverage type` (categorical, string)
|
| 74 |
+
- `Added sugar (g)` (float)
|
| 75 |
+
- `Calories` (float)
|
| 76 |
+
- `Volume` (categorical, 300 mL or 355 mL)
|
| 77 |
+
- `Energy rating` (int, 1–5)
|
| 78 |
+
- **Target:**
|
| 79 |
+
- `is high sugar?` – integer label, also used for prediction tasks
|
| 80 |
+
|
| 81 |
+
## Splits
|
| 82 |
+
- `original`: 30 real world examples
|
| 83 |
+
- `augmented`: 300 synthetic samples via jitter based augmentation
|
| 84 |
+
|
| 85 |
+
## Intended Use / Limitations
|
| 86 |
+
- **Use cases:** regression/classification practice, feature importance exploration, interpretable ML projects
|
| 87 |
+
- **Limitations:** small original sample size, subjective energy rating label, dataset not exhaustive of all beverage categories
|
| 88 |
+
|
| 89 |
+
This dataset is **not** intended for nutrition advice or commercial recommendation engines.
|
| 90 |
+
|
| 91 |
+
## Ethical Notes
|
| 92 |
+
- No personally identifiable information is included.
|
| 93 |
+
- Energy ratings are subjective and approximate.
|
| 94 |
+
- Consumers should not use this data for health or fitness decisions.
|
| 95 |
+
|
| 96 |
+
## License
|
| 97 |
+
This dataset is released under the **Creative Commons Attribution 4.0 International (CC BY 4.0)** license.
|
| 98 |
+
|
| 99 |
+
## AI Usage Disclosure
|
| 100 |
+
ChatGPT (GPT-4) was used as a **teammate throughout the process** to assist with:
|
| 101 |
+
- On the go Python coding
|
| 102 |
+
- Augmentation approach
|
| 103 |
+
- Polishing and formatting the final dataset and notebook
|