The dataset viewer is not available for this subset.
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/webdataset/webdataset.py", line 81, in _split_generators
first_examples = list(islice(pipeline, self.NUM_EXAMPLES_FOR_FEATURES_INFERENCE))
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/webdataset/webdataset.py", line 32, in _get_pipeline_from_tar
fs: fsspec.AbstractFileSystem = fsspec.filesystem("memory")
~~~~~~~~~~~~~~~~~^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 302, in filesystem
cls = get_filesystem_class(protocol)
File "/usr/local/lib/python3.14/site-packages/fsspec/registry.py", line 239, in get_filesystem_class
raise ValueError(f"Protocol not known: {protocol}")
ValueError: Protocol not known: memory
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 71, 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.
CESNET-TimeSeries24 — verbatim Zenodo archives
A faithful mirror of CESNET-TimeSeries24 (DOI 10.5281/zenodo.13382427): per-IP aggregate time series from 40 weeks of CESNET backbone monitoring — 275k+ IP addresses, 548 institution subnets, 283 institutions, at 10-minute / 1-hour / 1-day windows, derived from 66 billion flows.
These are the upstream tar.gz archives, byte-identical, not a conversion. Unlike the flow corpora published alongside this mirror, TimeSeries24 holds aggregates, not flow records — mapping it onto a flow schema would fabricate flows that were never measured. It is published here unmodified so the whole training corpus lives in one place; a dedicated time-series loader is the right way to consume it.
| file | GB |
|---|---|
| ip_addresses_full.tar.gz | 40.0 |
| institution_subnets.tar.gz | 0.77 |
| institutions.tar.gz | 0.48 |
| ip_addresses_sample.tar.gz | 0.17 |
| ids_relationship.csv / times.tar.gz / weekends_and_holidays.csv | <0.01 |
Archives contain one CSV per time-series ID (metrics: n_flows, n_packets, n_bytes, n_dest_ip, n_dest_asn, n_dest_ports, tcp_udp_ratio_*, dir_ratio_*, avg_duration, avg_ttl; the 1h/1d re-aggregations carry sum_/avg_/std_
variants). ts24-manifest.json records the download provenance.
Licensing & citation
Source dataset © CESNET, CC-BY-4.0; mirrored under the same license. Cite: Koumar, J. et al., CESNET-TimeSeries24: Time Series Dataset for Network Traffic Anomaly Detection and Forecasting, Scientific Data 12:338 (2025). https://doi.org/10.1038/s41597-025-04603-x
- Downloads last month
- 28