Do not convert more data than the next step needs

Large measurement files often contain much more data than the immediate analysis requires. If the interesting event is already known to be near a particular sample range, converting an entire Channel to CSV may only create a larger intermediate file and a longer wait.

A range-based export keeps the operation aligned with the real question: which Channel and which samples are needed next?

Use the original Channel sample index as the reference

TdmsSlice range selection uses Start index and Count. The exported Index column preserves the original Channel sample index rather than renumbering the selected range from zero.

That is useful when someone gives you a known range, when you need to compare the CSV with another tool, or when you want to keep a clear connection between the exported rows and their location in the source Channel.

  1. Open the TDMS file and select the required Channel.
  2. Use Quick Preview when available to orient yourself in the Channel.
  3. Enter the Start index and Count for the range you want.
  4. Confirm the calculated End index.
  5. Choose Export CSV and save the result.
  6. Keep the companion metadata JSON with the CSV when provenance matters.

Time columns are added only when they can be derived safely

The CSV always keeps the sample Index. When the selected Channel has valid waveform timing information that TdmsSlice can interpret safely, the CSV can also include a relative-time or absolute-UTC time column.

A separate Channel merely named time or Timestamp is not automatically joined to another Channel. This avoids inventing a relationship that the source file may not actually define.

Keep the sidecar metadata JSON

CSV is convenient for downstream tools, but it does not naturally preserve all of the context carried by TDMS. TdmsSlice therefore writes a companion metadata JSON alongside a CSV export.

That sidecar records information about the source selection, data type, export range, timing interpretation, and related metadata so the extracted table is easier to trace back to its origin.

Evaluation and Standard use the same core workflow

The Evaluation edition is intended to test this workflow with real files. Its CSV export is limited to 100 samples per export. Standard removes that practical sample-count limit while keeping the same core file-reading and range-selection workflow.