Datasets:
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
Error code: DatasetGenerationCastError
Exception: DatasetGenerationCastError
Message: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 1 new columns ({'constraints'})
This happened while the csv dataset builder was generating data using
hf://datasets/ClarusC64/euv-banding-failure-horizon-and-sync-routing-v0.1/data/test.csv (at revision dd9f4a41e56a758a3ff56fb7b6e6414e992d4ef8), [/tmp/hf-datasets-cache/medium/datasets/13988846957052-config-parquet-and-info-ClarusC64-euv-banding-fai-619fab25/hub/datasets--ClarusC64--euv-banding-failure-horizon-and-sync-routing-v0.1/snapshots/dd9f4a41e56a758a3ff56fb7b6e6414e992d4ef8/data/test.csv (origin=hf://datasets/ClarusC64/euv-banding-failure-horizon-and-sync-routing-v0.1@dd9f4a41e56a758a3ff56fb7b6e6414e992d4ef8/data/test.csv)]
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1887, in _prepare_split_single
writer.write_table(table)
File "/usr/local/lib/python3.12/site-packages/datasets/arrow_writer.py", line 675, in write_table
pa_table = table_cast(pa_table, self._schema)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/table.py", line 2272, in table_cast
return cast_table_to_schema(table, schema)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/table.py", line 2218, in cast_table_to_schema
raise CastError(
datasets.table.CastError: Couldn't cast
id: string
case_title: string
pulse_time_jitter_ns: int64
phase_alignment_error_ns: int64
stage_pos_error_nm: double
exposure_window_ns: int64
drift_rate_ns_per_min: double
residual_banding_metric: double
banding_risk_score: string
time_to_visible_banding_min: string
yield_risk: string
recommended_sync_action: string
minimal_fix_set: string
notes: string
constraints: string
-- schema metadata --
pandas: '{"index_columns": [{"kind": "range", "name": null, "start": 0, "' + 2243
to
{'id': Value('string'), 'case_title': Value('string'), 'pulse_time_jitter_ns': Value('int64'), 'phase_alignment_error_ns': Value('int64'), 'stage_pos_error_nm': Value('float64'), 'exposure_window_ns': Value('int64'), 'drift_rate_ns_per_min': Value('float64'), 'residual_banding_metric': Value('float64'), 'banding_risk_score': Value('float64'), 'time_to_visible_banding_min': Value('int64'), 'yield_risk': Value('float64'), 'recommended_sync_action': Value('string'), 'minimal_fix_set': Value('string'), 'notes': Value('string')}
because column names don't match
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1347, in compute_config_parquet_and_info_response
parquet_operations = convert_to_parquet(builder)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 980, in convert_to_parquet
builder.download_and_prepare(
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 884, in download_and_prepare
self._download_and_prepare(
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 947, in _download_and_prepare
self._prepare_split(split_generator, **prepare_split_kwargs)
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1736, in _prepare_split
for job_id, done, content in self._prepare_split_single(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1889, in _prepare_split_single
raise DatasetGenerationCastError.from_cast_error(
datasets.exceptions.DatasetGenerationCastError: An error occurred while generating the dataset
All the data files must have the same columns, but at some point there are 1 new columns ({'constraints'})
This happened while the csv dataset builder was generating data using
hf://datasets/ClarusC64/euv-banding-failure-horizon-and-sync-routing-v0.1/data/test.csv (at revision dd9f4a41e56a758a3ff56fb7b6e6414e992d4ef8), [/tmp/hf-datasets-cache/medium/datasets/13988846957052-config-parquet-and-info-ClarusC64-euv-banding-fai-619fab25/hub/datasets--ClarusC64--euv-banding-failure-horizon-and-sync-routing-v0.1/snapshots/dd9f4a41e56a758a3ff56fb7b6e6414e992d4ef8/data/test.csv (origin=hf://datasets/ClarusC64/euv-banding-failure-horizon-and-sync-routing-v0.1@dd9f4a41e56a758a3ff56fb7b6e6414e992d4ef8/data/test.csv)]
Please either edit the data files to have matching columns, or separate them into different configurations (see docs at https://hf.co/docs/hub/datasets-manual-configuration#multiple-configurations)Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
id string | case_title string | pulse_time_jitter_ns int64 | phase_alignment_error_ns int64 | stage_pos_error_nm float64 | exposure_window_ns int64 | drift_rate_ns_per_min float64 | residual_banding_metric float64 | banding_risk_score float64 | time_to_visible_banding_min int64 | yield_risk float64 | recommended_sync_action string | minimal_fix_set string | notes string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
EUV-BAND-001 | Stable | 8 | 6 | 1.2 | 120 | 0.1 | 0.03 | 0.08 | 999 | 0.05 | monitor | none | Healthy |
EUV-BAND-002 | Low risk drift | 12 | 10 | 1.6 | 115 | 0.4 | 0.05 | 0.18 | 180 | 0.12 | monitor | tighten timing QA | Watch |
EUV-BAND-003 | Early banding risk | 16 | 14 | 1.9 | 115 | 0.8 | 0.07 | 0.32 | 90 | 0.22 | pulse_retime | pulse timing retime; jitter clamp | Retiming helps |
EUV-BAND-004 | Phase drift | 18 | 18 | 2 | 110 | 1 | 0.09 | 0.4 | 70 | 0.3 | stage_phase_correction | stage phase offset; latency trim | Phase correction |
EUV-BAND-005 | Margin collapse | 20 | 22 | 2.2 | 105 | 1.4 | 0.12 | 0.52 | 45 | 0.4 | servo_rebalance | servo gain rebalance; latency reduction | Control fix |
EUV-BAND-006 | Pre-banding | 24 | 28 | 2.5 | 100 | 1.8 | 0.18 | 0.66 | 25 | 0.55 | source_recalibrate | source timing recal; jitter reduction | Source drift |
EUV-BAND-007 | Banding visible | 28 | 34 | 2.9 | 95 | 2.2 | 0.26 | 0.78 | 12 | 0.68 | halt_and_recalibrate | halt exposure; full sync recal; verify pupil | Stop |
EUV-BAND-008 | Severe banding | 32 | 40 | 3.3 | 90 | 2.8 | 0.36 | 0.86 | 6 | 0.78 | halt_and_recalibrate | halt; isolate jitter source; recalibrate sync | Imminent |
EUV-BAND-009 | Latency dominated | 26 | 30 | 2.7 | 100 | 2 | 0.22 | 0.72 | 18 | 0.62 | latency_trim | reduce loop latency; retime pulse trigger | Latency |
EUV-BAND-010 | Jitter dominated | 30 | 36 | 3 | 95 | 2.4 | 0.3 | 0.82 | 9 | 0.72 | jitter_clamp | stabilize droplet trigger; pulse shaping; jitter clamp | Jitter |
What this dataset tests
Forecast when banding becomes visible on wafer.
Route the minimal sync intervention.
Banding emerges when:
pulse timing jitter rises
phase alignment error grows
exposure window shrinks
drift rate accelerates
Task
Given telemetry, output JSON:
- horizon_min
- action
- fix_set
Example {"horizon_min":25,"action":"pulse_retime","fix_set":"pulse timing retime; jitter clamp"}
Inputs
pulse_time_jitter_ns
phase_alignment_error_ns
stage_pos_error_nm
exposure_window_ns
drift_rate_ns_per_min
Context
residual_banding_metric
banding_risk_score
yield_risk
Allowed actions
monitor
pulse_retime
stage_phase_correction
servo_rebalance
source_recalibrate
latency_trim
jitter_clamp
halt_and_recalibrate
Evaluation
Checks:
valid JSON
has horizon and action
action is in allowed set
Version
v0.1
- Downloads last month
- 16