Datasets:

---

hasilm1

/

Earthquake_PredictNextDate

like 0

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 33 new columns ({'grid_id', 'magType', 'lat_grid', 'gap', 'days_until_next_local', 'global_30_day_count', 'last_mag', 'nst', 'depth', 'tsunami', 'next_quake_time', 'mag', 'prev_days_since_last', 'lon_grid', 'day_of_year', 'rolling_avg_mag', 'gap_to_avg_ratio', 'time', 'dmin', 'year', 'place', 'type', 'lat_bin', 'hour', 'net', 'lon_bin', 'month', 'rms', 'updated', 'status', 'depth_category', 'id', 'mag_category'})

This happened while the csv dataset builder was generating data using

hf://datasets/hasilm1/Earthquake_PredictNextDate/df.csv (at revision b9f81d2e65d4b6054bde74949d8f2431df43ee5a), ['hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/X_spatial.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/Xtest.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/Xtrain.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/df.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/earthquake.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/earthquakes.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/earthquakes1.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/y_days.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/ymag.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/ytest.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/ytrain.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.14/site-packages/datasets/builder.py", line 1837, in _prepare_split_single
                  writer.write_table(table)
                  ~~~~~~~~~~~~~~~~~~^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 765, in write_table
                  self._write_table(pa_table, writer_batch_size=writer_batch_size)
                  ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/arrow_writer.py", line 773, in _write_table
                  pa_table = table_cast(pa_table, self._schema)
                File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2369, in table_cast
                  return cast_table_to_schema(table, schema)
                File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2297, in cast_table_to_schema
                  raise CastError(
                  ...<3 lines>...
                  )
              datasets.table.CastError: Couldn't cast
              id: string
              time: string
              year: int64
              month: int64
              day_of_year: int64
              hour: int64
              latitude: double
              longitude: double
              depth: double
              mag: double
              magType: string
              place: string
              type: string
              tsunami: int64
              mag_category: string
              depth_category: string
              nst: double
              gap: double
              dmin: double
              rms: double
              net: string
              updated: string
              status: string
              lat_bin: double
              lon_bin: double
              next_quake_time: string
              lat_grid: double
              lon_grid: double
              grid_id: string
              days_since_last_local: double
              avg_local_gap: double
              days_until_next_local: double
              last_mag: double
              rolling_avg_mag: double
              prev_days_since_last: double
              gap_acceleration: double
              global_30_day_count: double
              gap_to_avg_ratio: double
              spatial_cluster_id: int64
              distance_to_center: double
              spatial_cluster_density: int64
              -- schema metadata --
              pandas: '{"index_columns": [{"kind": "range", "name": null, "start": 0, "' + 5168
              to
              {'latitude': Value('float64'), 'longitude': Value('float64'), 'spatial_cluster_id': Value('int64'), 'distance_to_center': Value('float64'), 'spatial_cluster_density': Value('int64'), 'days_since_last_local': Value('float64'), 'avg_local_gap': Value('float64'), 'gap_acceleration': Value('float64')}
              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 1369, in compute_config_parquet_and_info_response
                  parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
                                                                        ~~~~~~~~~~~~~~~~~~~~~~~~~^
                      builder, max_dataset_size_bytes=max_dataset_size_bytes
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
                  builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
                  ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1683, in _prepare_split
                  for job_id, done, content in self._prepare_split_single(
                                               ~~~~~~~~~~~~~~~~~~~~~~~~~~^
                      gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  ):
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1839, in _prepare_split_single
                  raise DatasetGenerationCastError.from_cast_error(
                  ...<4 lines>...
                  )
              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 33 new columns ({'grid_id', 'magType', 'lat_grid', 'gap', 'days_until_next_local', 'global_30_day_count', 'last_mag', 'nst', 'depth', 'tsunami', 'next_quake_time', 'mag', 'prev_days_since_last', 'lon_grid', 'day_of_year', 'rolling_avg_mag', 'gap_to_avg_ratio', 'time', 'dmin', 'year', 'place', 'type', 'lat_bin', 'hour', 'net', 'lon_bin', 'month', 'rms', 'updated', 'status', 'depth_category', 'id', 'mag_category'})
              
              This happened while the csv dataset builder was generating data using
              
              hf://datasets/hasilm1/Earthquake_PredictNextDate/df.csv (at revision b9f81d2e65d4b6054bde74949d8f2431df43ee5a), ['hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/X_spatial.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/Xtest.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/Xtrain.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/df.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/earthquake.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/earthquakes.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/earthquakes1.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/y_days.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/ymag.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/ytest.csv', 'hf://datasets/hasilm1/Earthquake_PredictNextDate@b9f81d2e65d4b6054bde74949d8f2431df43ee5a/ytrain.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)