Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clarify language around empty cptures segments #293

Merged
merged 1 commit into from
Aug 29, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion sigmf-spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -475,10 +475,15 @@ field to associate up to the relevant `sigmf-collection` file.

#### Captures Array

The `captures` value is an array of `capture segment` Objects that describe the
The `captures` field is an array of `capture segment` Objects that describe the
parameters of the signal capture. It MUST be sorted by the value of each
capture segment's `core:sample_start` key, ascending.

All samples in a dataset are contained in exactly one capture segment. While
there SHOULD be at least one segment defined, there are no items in the captures
array it is implied that a single capture with the `core:sample_start` field
equal to zero; no other metadata is implied.

##### Capture Segment Objects

Capture Segment Objects are composed of key/value pairs, and each Segment describes
Expand Down