Global observations: avoid time/duration
See original GitHub issueIs there any way I could add an observation without the fields time
and duration
, such that it becomes a track-level observation (e.g., track-level tag)?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Accuracy measurement by RTK method under varied time ...
Global Navigation Satellite System (GNSS), an advance surveying system, is used to determine three-dimension points with high accuracy.
Read more >Guidelines for classroom observations
Time/duration of behavior? Time between direction to student & initiation of response. Length of time behavior lasts. Specific beginning & end or continuous....
Read more >Filter dataset for duration of time since first observation R
In this above example, I would want to filter out any observations (i.e., rows) after 7 minutes and 15 seconds (from the first...
Read more >Publishing and Using Earth Observation Data with the RDF ...
This document illustrates that approach showing how Earth Observation imagery can be published as Linked Data using the RDF Data Cube vocabulary ...
Read more >Climatic Data Elements
It is important that thermometers be shaded from sunlight to avoid an erroneously ... Recording gages have instrumentation which records the time, duration, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, the schema is written such that all observations have a time and duration (non-negative float) to validate properly.
I think the correct thing to do here is as @justinsalamon says: make the implicit quantities explicit by documenting the length of the track in the observation fields. Of course, nobody forces you to use that information, but it needs to be there to validate in the schema.
I agree it’s cumbersome, but time/duration are baked into the definition of an observation: https://github.com/marl/jams/blob/255a5ee860b03cec8f889c9986e734a6393a0dbc/jams/core.py#L597-L599 I may be wrong but I believe that supporting observations both with and without time/duration would require a major overhaul that would impact a significant number of lines (apart from the core structure, think validation and every operation currently supported on annotations), if it’s even feasible under the current design.
Since @bmcfee was the main architect behind the observation tuple, he should probably chime in here.