Datasets:

Dataset Viewer
The dataset viewer is not available for this subset.
Cannot get the split names for the config 'default' of the dataset.
Exception:    SplitsNotFoundError
Message:      The split names could not be parsed from the dataset config.
Traceback:    Traceback (most recent call last):
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
                  for split_generator in builder._split_generators(
                                         ~~~~~~~~~~~~~~~~~~~~~~~~~^
                      StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/tsfile/tsfile.py", line 271, in _split_generators
                  scan = self._scan_metadata(all_files)
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/tsfile/tsfile.py", line 318, in _scan_metadata
                  with self._open_reader(file) as reader:
                       ~~~~~~~~~~~~~~~~~^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/tsfile/tsfile.py", line 742, in _open_reader
                  return TsFileReader(file)
                File "tsfile/tsfile_reader.pyx", line 364, in tsfile.tsfile_reader.TsFileReaderPy.__init__
                File "tsfile/tsfile_reader.pyx", line 367, in tsfile.tsfile_reader.TsFileReaderPy.init_reader
                File "tsfile/tsfile_py_cpp.pyx", line 789, in tsfile.tsfile_py_cpp.tsfile_reader_new_c
                File "tsfile/tsfile_py_cpp.pyx", line 55, in tsfile.tsfile_py_cpp.check_error
              tsfile.exceptions.FileOpenError: 28: Failed to open file
              
              The above exception was the direct cause of the following exception:
              
              Traceback (most recent call last):
                File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 68, in compute_split_names_from_streaming_response
                  for split in get_dataset_split_names(
                               ~~~~~~~~~~~~~~~~~~~~~~~^
                      path=dataset,
                      ^^^^^^^^^^^^^
                      config_name=config,
                      ^^^^^^^^^^^^^^^^^^^
                      token=hf_token,
                      ^^^^^^^^^^^^^^^
                  )
                  ^
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
                  info = get_dataset_config_info(
                      path,
                  ...<6 lines>...
                      **config_kwargs,
                  )
                File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
                  raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
              datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.

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.

Crypto Trading Bot Data (TsFile)

Apache TsFile version of jponfiru/crypto-trading-bot-data.

Overview

OHLCV market data and derived features for a Binance spot trading bot: 1-minute klines for the top-20 USDT pairs (2024 onward), 5-minute klines for 2026, 1-hour klines, funding rates, open interest, macro indicators, the Fear & Greed index, BTC dominance, and a labelled feature table for the project's Model D.

  • TsFile shards: 37 (1054.2 MB total, 29,706,465 rows across 9 table(s)).
    • btc_dominance β€” 6 rows in 1 shard(s), 2026-05-18 01:06:09.359000 β†’ 2026-05-21 12:34:43.211000 (UTC)
    • fear_greed β€” 3,028 rows in 1 shard(s), 2018-02-01 00:00:00 β†’ 2026-05-21 00:00:00 (UTC)
    • features_d β€” 219,043 rows in 1 shard(s), 2024-01-09 08:00:00 β†’ 2026-05-10 14:00:00 (UTC)
    • funding_rates β€” 57,360 rows in 1 shard(s), 2024-01-01 00:00:00 β†’ 2026-05-21 12:00:00 (UTC)
    • klines_1h β€” 383,190 rows in 1 shard(s), 2024-01-01 00:00:00 β†’ 2026-05-11 15:00:00 (UTC)
    • macro_indicators β€” 54 rows in 1 shard(s), 2026-05-11 04:00:00 β†’ 2026-05-21 07:00:00 (UTC)
    • ohlcv β€” 4,610,042 rows in 5 shard(s), 2024-01-01 00:00:00 β†’ 2026-05-14 03:00:00 (UTC)
    • ohlcv_1m β€” 24,432,100 rows in 25 shard(s), 2024-01-01 00:00:00 β†’ 2026-05-21 12:34:00 (UTC)
    • open_interest β€” 1,642 rows in 1 shard(s), 2026-05-18 02:00:00 β†’ 2026-05-21 12:00:00 (UTC)

Conversion notes

  • The source stores its series inside two SQLite databases; TsFile cannot read SQLite, so every table is streamed out of its database into a TsFile table of its own. Table list, row counts and skipped tables are recorded in conversion_summary.json.
  • Tables with a pair (or symbol) column β€” ohlcv_1m, ohlcv, klines_1h, funding_rates, open_interest, macro_indicators and features_d β€” declare it as the TAG, so each instrument is one TsFile device with its own timeline; fear_greed and btc_dominance are single-device tables.
  • Time = the source timestamp column at millisecond precision: ts_ms is already epoch milliseconds, ts is epoch seconds, and ohlcv.timestamp is an ISO-8601 string.
  • No column and no row is dropped. ohlcv_1m (2024 onward) and ohlcv (2026) overlap; both are kept as separate tables rather than merged, and no duplicate key is removed because the two tables cover different timeframes.
  • Not converted: download_state (data_2026.db), download_progress (data_extended.db) β€” bookkeeping tables recording the crawler's own progress, not time series.
  • Not converted: features_extended.csv β€” 2.1 GB CSV of event features that was not downloaded for this conversion; the compact features_d.csv subset (219,043 rows) is included instead.
  • The TsFiles are written with the zstd compressor. The Apache TsFile Java SDK reads every compressor, but the Python SDK (pip install tsfile) implements only UNCOMPRESSED, SNAPPY, GZIP and LZ4; opening these files with it returns no rows. Read them with the Java SDK, as shown below.

Usage

Read this dataset with the Java SDK. It is written with the zstd compressor. The Apache TsFile Java SDK reads every compressor, but the Python SDK (pip install tsfile) implements only UNCOMPRESSED, SNAPPY, GZIP and LZ4; opening this file with it yields no rows.

Read a converted file with the Apache TsFile Java SDK (org.apache.tsfile:tsfile):

import org.apache.tsfile.file.metadata.IDeviceID;
import org.apache.tsfile.read.TsFileReader;
import org.apache.tsfile.read.TsFileSequenceReader;
import org.apache.tsfile.read.common.Path;
import org.apache.tsfile.read.expression.QueryExpression;
import org.apache.tsfile.read.query.dataset.QueryDataSet;
import org.apache.tsfile.write.schema.MeasurementSchema;

import java.util.ArrayList;
import java.util.List;

String path = "btc_dominance.tsfile";
try (TsFileReader reader = new TsFileReader(new TsFileSequenceReader(path))) {
    for (String deviceId : reader.getAllDeviceIds()) {
        IDeviceID device = IDeviceID.Factory.DEFAULT_FACTORY.create(deviceId);
        List<Path> paths = new ArrayList<>();
        for (MeasurementSchema schema : reader.getMeasurement(device)) {
            String name = schema.getMeasurementName();
            if (name != null && !name.isEmpty() && !name.equalsIgnoreCase("Time")) {
                paths.add(new Path(device, name, true));
            }
        }
        QueryDataSet dataSet = reader.query(QueryExpression.create(paths, null));
        while (dataSet.hasNext()) {
            System.out.println(dataSet.next());
        }
    }
}

Source & license

Downloads last month
9