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.12/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
                  for split_generator in builder._split_generators(
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/packaged_modules/json/json.py", line 91, in _split_generators
                  pa_table = next(iter(self._generate_tables(**splits[0].gen_kwargs, allow_full_read=False)))[1]
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/packaged_modules/json/json.py", line 193, in _generate_tables
                  examples = [ujson_loads(line) for line in batch.splitlines()]
                              ^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/utils/json.py", line 20, in ujson_loads
                  return pd.io.json.ujson_loads(*args, **kwargs)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
              ValueError: Expected object or value
              
              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 65, in compute_split_names_from_streaming_response
                  for split in get_dataset_split_names(
                               ^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
                  info = get_dataset_config_info(
                         ^^^^^^^^^^^^^^^^^^^^^^^^
                File "/usr/local/lib/python3.12/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.

4CZNZ Vintage Electronics Reasoning Dataset (Sample v1)

Overview

4CZNZ Vintage Electronics Reasoning Dataset (Sample v1)

High-signal reasoning dataset derived from real-world electronics troubleshooting discussions (pre-2010).

4CZNZ Reasoning Corpus Library

Current domains:

  • Vintage electronics
  • PLC / industrial control systems (in development)

Each dataset captures structured, multi-step reasoning from real-world problem-solving environments.

This dataset contains structured discussions from pre-2010 legacy electronics forums (primarily diyaudio), focused on real-world engineering troubleshooting and circuit-level reasoning.

The dataset has been curated and filtered using a reasoning-density scoring framework, prioritising threads with explicit problem-solving and technical decision-making.


Key Characteristics

  • Source: legacy electronics forums (pre-social media era)
  • Format: JSONL
  • Records: 176
  • Estimated tokens: ~241,048
  • Average reasoning density: 0.6959

What Makes This Dataset Different

Unlike generic web corpora, this dataset:

  • captures step-by-step engineering reasoning
  • contains constraint-based troubleshooting
  • reflects real practitioner decision-making

Each record is part of a corpus that has been:

  • scored for reasoning density
  • filtered toward high-signal technical dialogue
  • structured for downstream ML use
  • This dataset explicitly surfaces reasoning as a measurable property, rather than treating it as an emergent byproduct of generic text corpora.
  • not synthetic data
  • not shallow web scraping
  • multi-participant reasoning chains
  • real-world engineering problem solving under constraints

This dataset captures how humans actually solve technical problems across multiple participants: problem → hypothesis → test → resolution

Relevance to robotics and autonomous systems:

Although sourced from electronics forums, this dataset is highly relevant to robotics and autonomy, where systems must reason through failures, constraints, and real-world uncertainty.


Reasoning Density Profile

  • very_high: 79
  • high: 37
  • medium: 21
  • low: 19
  • very_low: 20

Top batches exceed reasoning-density averages of 0.90.


Example Record

{ "collection": "vintage_electronics_forums_v0", "forum": "diyaudio", "thread_title": "Amplifier hum issue when grounding chassis", "post_text": "I'm getting a low-frequency hum after connecting the chassis ground. Could this be a grounding loop issue or something related to the power supply filtering?" }


Use Cases

  • training reasoning-focused language models
  • evaluation of technical problem-solving
  • fine-tuning engineering assistants

Structure of reasoning:

Each thread typically follows:

problem → hypothesis → test → iteration → resolution

This structure is preserved across participants, enabling models to learn real-world reasoning progression.


About 4CZNZ

4CZNZ builds structured datasets from legacy technical sources, focusing on high-signal reasoning content not present in modern web corpora.


Notes

This is a sample release. Full corpus not included.

Commercial Access

This dataset is a sample from a larger structured corpus.

4CZNZ provides high-signal reasoning datasets for AI, robotics, and autonomous systems.

Available:

  • Pilot datasets (domain-specific)
  • Expanded corpora
  • Licensing options

Contact: contact@4cznz.tech

Downloads last month
18