File size: 12,589 Bytes
671c917 cf5e328 671c917 00060cc cf5e328 00060cc 671c917 cf5e328 671c917 cf5e328 00060cc 671c917 00060cc 671c917 00060cc 671c917 cf5e328 671c917 00060cc 671c917 00060cc 671c917 cf5e328 671c917 00060cc 671c917 00060cc 671c917 cf5e328 671c917 00060cc 671c917 cf5e328 00060cc 671c917 00060cc 671c917 cf5e328 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 | ---
license: "other"
pretty_name: "Lithology Training Dataset"
task_categories:
- other
tags:
- geology
- geoscience
- well-logs
- petrophysics
- lithology
- LAS
- wireline-logs
- supervised-learning
- subsurface
- formation-evaluation
size_categories:
- "1K<n<10K"
---
[](https://github.com/Nora-Research-Lab)
[](https://huggingface.co/NoraResearchLab)
[](https://www.linkedin.com/company/nora-research-lab)
[](https://x.com/noraresearchlab)
[](https://noraresearchlab.site)
# Lithology Training Dataset
A supervised training dataset for machine learning and AI systems that learn to identify **lithology from well-log data**.
The dataset contains **400 wells** with standardized wireline-log measurements and corresponding lithological labels.
**Training dataset:**
https://huggingface.co/datasets/NoraResearchLab/Lithology-Training-Dataset
---
## Overview
The core task is:
> Given a sequence of well-log measurements across depth, predict the lithology present at each depth interval and/or reconstruct the corresponding lithological sequence.
The dataset is designed for:
* Lithology classification
* Well-log interpretation
* Sequence modelling
* Lithological interval segmentation
* Petrophysical machine learning
* Geoscience AI
* Subsurface representation learning
* Benchmark and model development
This dataset is intended for **training and model development**.
It is separate from the independent evaluation benchmark.
---
## Dataset Size
| Property | Value |
| -------------------- | -----------------------------: |
| Total wells | **400** |
| Lithological classes | **8** |
| Primary data type | Wireline well logs |
| Label type | Rule-derived supervised labels |
| Sampling | Standardized depth grid |
| Primary task | Lithology identification |
---
## Lithology Classes
The dataset contains:
* `SHALE`
* `SANDSTONE`
* `LIMESTONE`
* `DOLOMITE`
* `ANHYDRITE`
* `SALT`
* `COAL`
* `UNKNOWN/MIXED`
`UNKNOWN/MIXED` represents intervals where the available log evidence does not provide sufficient confidence for assigning one of the principal lithological classes.
---
# Dataset Structure
The repository contains multiple Parquet tables representing different levels of the dataset.
These tables **do not share an identical schema** and should therefore be loaded independently.
```text
data/
├── logs/
│ ├── train.parquet
│ ├── validation.parquet
│ └── test.parquet
│
├── depthwise/
│ ├── train.parquet
│ ├── validation.parquet
│ └── test.parquet
│
└── intervals/
├── train.parquet
├── validation.parquet
└── test.parquet
```
The exact files available in the repository should be treated as the authoritative source for the current release.
---
## Dataset Configurations
### `logs`
Depth-indexed wireline-log measurements.
Typical structure:
```text
well_id
depth_ft
GR
RHOB
NPHI
PEF
DT
RT
CALI
...
```
This table is intended to provide the primary input features for machine-learning models.
---
### `depthwise`
Depthwise supervised labels and derived information associated with individual log samples.
Typical structure may include:
```text
well_id
depth_ft
lithology_pointwise
score
...
```
This configuration is useful for:
* Pointwise lithology classification
* Sequence modelling
* Depthwise prediction
* Label analysis
* Training supervised models
---
### `intervals`
Lithological intervals represented as continuous depth ranges.
Typical structure:
```text
well_id
interval_id
top_depth_ft
base_depth_ft
thickness_ft
lithology
...
```
This configuration is useful for:
* Lithological sequence reconstruction
* Interval segmentation
* Continuous geological interpretation
* Comparing predicted and reference intervals
---
# Recommended Loading Method
Because the repository contains **multiple heterogeneous Parquet tables**, the recommended approach is to load each Parquet file directly.
### Python
```python
import pandas as pd
BASE_URL = (
"https://huggingface.co/datasets/"
"NoraResearchLab/Lithology-Training-Dataset/"
"resolve/main/data"
)
# Logs
logs_train = pd.read_parquet(
f"{BASE_URL}/logs/train.parquet"
)
logs_validation = pd.read_parquet(
f"{BASE_URL}/logs/validation.parquet"
)
logs_test = pd.read_parquet(
f"{BASE_URL}/logs/test.parquet"
)
# Depthwise labels
depthwise_train = pd.read_parquet(
f"{BASE_URL}/depthwise/train.parquet"
)
depthwise_validation = pd.read_parquet(
f"{BASE_URL}/depthwise/validation.parquet"
)
depthwise_test = pd.read_parquet(
f"{BASE_URL}/depthwise/test.parquet"
)
# Lithological intervals
intervals_train = pd.read_parquet(
f"{BASE_URL}/intervals/train.parquet"
)
intervals_validation = pd.read_parquet(
f"{BASE_URL}/intervals/validation.parquet"
)
intervals_test = pd.read_parquet(
f"{BASE_URL}/intervals/test.parquet"
)
```
Install the required packages with:
```bash
pip install pandas pyarrow
```
This method reads the Parquet files directly from the Hugging Face repository without requiring the repository to be converted into a single Hugging Face `Dataset` object.
---
# Why `load_dataset()` Is Not Recommended
The repository contains different table types with different schemas.
For example, `logs` and `depthwise` are primarily **depthwise/pointwise data**, while `intervals` contains **range-based interval records**.
Their structures are therefore different.
Attempting:
```python
from datasets import load_dataset
dataset = load_dataset(
"NoraResearchLab/Lithology-Training-Dataset"
)
```
may cause Hugging Face Datasets to attempt to construct a unified schema across the repository's Parquet files.
This can result in errors such as:
```text
CastError:
Couldn't cast ...
because column names don't match
```
This is not an indication that the underlying Parquet files are invalid. The issue is that the repository contains multiple heterogeneous tabular structures.
**Load each table independently instead.**
---
# Loading Only One Configuration
If you only need the well-log features for model training, you do not need to download or load the other tables.
For example:
```python
import pandas as pd
url = (
"https://huggingface.co/datasets/"
"NoraResearchLab/Lithology-Training-Dataset/"
"resolve/main/data/logs/train.parquet"
)
logs_train = pd.read_parquet(url)
print(logs_train.shape)
print(logs_train.head())
```
For the depthwise labels:
```python
import pandas as pd
url = (
"https://huggingface.co/datasets/"
"NoraResearchLab/Lithology-Training-Dataset/"
"resolve/main/data/depthwise/train.parquet"
)
depthwise_train = pd.read_parquet(url)
print(depthwise_train.shape)
print(depthwise_train.head())
```
For lithological intervals:
```python
import pandas as pd
url = (
"https://huggingface.co/datasets/"
"NoraResearchLab/Lithology-Training-Dataset/"
"resolve/main/data/intervals/train.parquet"
)
intervals_train = pd.read_parquet(url)
print(intervals_train.shape)
print(intervals_train.head())
```
---
# Typical Training Workflow
A typical lithology-classification workflow can use the `logs` and `depthwise` tables together.
```python
import pandas as pd
BASE_URL = (
"https://huggingface.co/datasets/"
"NoraResearchLab/Lithology-Training-Dataset/"
"resolve/main/data"
)
logs = pd.read_parquet(
f"{BASE_URL}/logs/train.parquet"
)
labels = pd.read_parquet(
f"{BASE_URL}/depthwise/train.parquet"
)
```
The two tables can then be related using their common identifiers, typically:
```text
well_id
depth_ft
```
For example:
```python
training_data = logs.merge(
labels,
on=["well_id", "depth_ft"],
how="inner"
)
```
Before training, users should inspect the resulting schema and verify that the expected feature and target columns are present:
```python
print(training_data.shape)
print(training_data.columns.tolist())
print(training_data.head())
```
The exact columns should always be determined from the released Parquet files rather than assumed from this README.
---
# Working With Individual Wells
The dataset is organized around complete wells. A model can therefore be trained using individual depth sequences rather than treating every row as an independent observation.
Example:
```python
well_id = logs["well_id"].iloc[0]
well_logs = logs[
logs["well_id"] == well_id
].sort_values("depth_ft")
print(well_logs)
```
This is particularly important for sequence-based approaches such as:
* LSTM/GRU models
* Temporal convolutional networks
* Transformers
* Sequence-to-sequence models
* Depthwise segmentation models
---
# Train / Validation / Test Splits
The dataset provides separate splits where available:
```text
train
validation
test
```
Users should preserve these splits when developing models.
Do not randomly mix rows from the same well across training and test sets unless the experimental design explicitly requires this.
For geological sequence modelling, **well-level separation** is important because neighboring depth samples from the same well are highly correlated.
---
# Relationship to the Lithology Sequence Identification Benchmark
This training dataset is intended for **model development and training**.
It is separate from the:
**Lithology Sequence Identification Benchmark**
The benchmark is designed to evaluate whether a model can reconstruct the lithological sequence of a complete well from raw wireline measurements.
The intended workflow is:
```text
Lithology Training Dataset
│
▼
Model Training
│
▼
Model Development
│
▼
Lithology Sequence Identification
Benchmark
│
▼
Independent
Evaluation
```
Models should not use benchmark evaluation wells as training data.
---
# Data Loading Notes
### Remote Parquet
`pandas.read_parquet()` can read the Parquet files directly from their Hugging Face HTTPS URLs when the appropriate Parquet engine is installed.
Recommended dependencies:
```bash
pip install pandas pyarrow
```
### Hugging Face Resolve URLs
The general URL pattern is:
```text
https://huggingface.co/datasets/{USER}/{REPOSITORY}/resolve/{BRANCH}/{PATH}
```
For this dataset:
```text
https://huggingface.co/datasets/NoraResearchLab/Lithology-Training-Dataset/resolve/main/data/
```
Individual files can then be addressed directly:
```text
data/logs/train.parquet
data/depthwise/train.parquet
data/intervals/train.parquet
```
---
# Important Usage Recommendation
**Do not assume that every Parquet file in the repository has the same schema.**
Treat each configuration as a separate table:
```text
logs → depthwise wireline measurements
depthwise → pointwise labels / derived depthwise information
intervals → continuous lithological intervals
```
Load only the tables required for the task you are performing.
---
## License and Usage
This dataset is provided under the license specified in the repository metadata.
Users are responsible for reviewing the applicable dataset provenance, source-data licenses, and restrictions before redistribution or commercial use.
The dataset is intended for research, machine-learning development, and geoscience AI applications.
---
## Citation
If you use this dataset in research, benchmarking, or a software project, please cite the NORA Research Lab dataset repository:
**NORA Research Lab — Lithology Training Dataset**
Hugging Face:
https://huggingface.co/datasets/NoraResearchLab/Lithology-Training-Dataset
---
## Organization
**NORA Research Lab**
Building intelligence for the real world.
* GitHub: https://github.com/Nora-Research-Lab
* Hugging Face: https://huggingface.co/NoraResearchLab
* LinkedIn: https://www.linkedin.com/company/nora-research-lab
* X: https://x.com/noraresearchlab
* Website: https://noraresearchlab.site
|