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.

Sign up for GitHub

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

Jump to bottom

Allow Freq (but not temporally) Bounded Annotations #128

Merged
merged 1 commit into from
Jun 11, 2021
Merged

Allow Freq (but not temporally) Bounded Annotations #128

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 4 additions & 2 deletions sigmf-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -399,7 +399,7 @@ annotation segment objects:
|name|required|type|description|
|----|--------------|-------|-----------|
|`sample_start`|true|uint|The sample index at which this segment takes effect.|
|`sample_count`|true|uint|The number of samples that this segment applies to. |
|`sample_count`|false|uint|The number of samples that this segment applies to. |
|`generator`|false|string|Human-readable name of the entity that created this annotation.|
|`comment`|false|string|A human-readable comment.|
|`freq_lower_edge`|false|double|The frequency (Hz) of the lower edge of the feature described by this annotation.|
Expand All @@ -409,7 +409,9 @@ annotation segment objects:

There is no limit to the number of annotations that can apply to the same group
of samples. If two annotations have the same `sample_start`, there is no
defined ordering between them.
defined ordering between them. If `sample_count` is not provided, it should
be assumed that the annotation applies from `sample_start` through the end of
the dataset, in all other cases `sample_count` should be provided.

The `freq_lower_edge` and `freq_upper_edge` fields should be at RF if the
feature is at a known RF frequency. If there is no known center frequency (as
Expand Down