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

Add diagnostics and data products. Specify sigan settings and cal info captures. JSON Schema 2020-12. #42

Merged
merged 188 commits into from
Jun 6, 2023

Conversation

dboulware
Copy link
Contributor

This PR:

  • Adds a new diagnostics extension to provide diagnostic information on common sensing system components.
  • The algorithms extension has undergone a major change that migrates the old annotation based approach to using a list of data products. Currently, the only supported data product is a graph. Graphs provide a general way to describe data and should support a single data reader.
  • Calibration and signal analyzer settings are provided in captures.
  • Introduces a small ntia-nasctn-sea extension for metadata specific to the NASCTN SEA project.
  • Removes the Location extension in favor of using the SigMF Global geolocation element. As a result, the emitter extension was updated to use a geolocation GeoJSON Point element to specify the location of the emitter.
  • JSON Schema was manually created to update it to the current 2020-12 specification.
  • Java code was refactored to consolidate extensions into their own packages regardless of whether it is a global, annotation, or captures object.

dboulware and others added 30 commits April 7, 2023 15:01
…aproducts, removed location extension, added nasctn-sea extension.
* Point to v1.x (current default) branch of SigMF. Changes made in v1.x should remain backwards-compatible with v1.0.0.
* Also includes a minor change to the datetime type listing for some objects, since the previously linked section can no longer be linked.
ntia-emitter.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-emitter.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
ntia-sensor.sigmf-ext.md Outdated Show resolved Hide resolved
Copy link
Member

@jhazentia jhazentia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above comments

…Correct xunits and yunits to x_units and y_units. Fix CPU type to Computer. Fix rfpaths link. Remove duplicate waveform extension listing. Remove setCoordinates in GeoJsonPoint. Update javadocs.
@dboulware dboulware requested a review from jhazentia June 5, 2023 19:14
* Get the action that produced the Acquisition, or unknown if it is not in the metadata.
* @return The name of the action that produced the Acquisition.
*/
public String getActionName() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please confirm that removal of getActionName is intended

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was, but I think it makes sense to add back in.

@@ -1,34 +0,0 @@
package gov.doc.ntia.sigmf;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was SchemaGenerator removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It didn't handle some annotations properly and wasn't generating the schema in the latest version of the JSON Schema spec (2020-12)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants