-
Notifications
You must be signed in to change notification settings - Fork 28
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
It is impossible to see what device collected a measurement in the data stream #438
Comments
That's by design. To interpret the data, you need to look up the ids referenced (trigger ids) in the study protocol. |
Actually, deviceRoleName should be there. The above comment is only true to get the full context (as in, know what type of device that is). But, the data shown here is much different from e.g. a carp core data point: https://github.com/cph-cachet/carp.core-kotlin/blob/develop/carp.data.core%2Fsrc%2FcommonMain%2Fkotlin%2Fdk%2Fcachet%2Fcarp%2Fdata%2Fapplication%2FDataStreamPoint.kt What am I looking at here? The "snapshot" looks a bit like a DataStreamSequence. JSON schema: https://github.com/cph-cachet/carp.core-kotlin/blob/develop/rpc%2Fschemas%2Fdata%2FDataStreamSequence.json That should have a Data stream id being an integer is definitely not carp core defined infrastructure, and neither is the "snapshot" property. There's also minor things, like the start and end recording time of audio, which is a clear candidate to use the default timestamps for. And, as far as I know |
What is this
You are looking at a
Yes - this
Indeed - I will create and issue for CAWS for @yuanchen233 to look at - there is something very wrong here in the data export.
A lot of the data we collect on the phone gets its own timestamp in a UTC format which we save.
I hope not - the order of fields in JSON should hopefully not matter - I can't control this in Dart. |
Created an issue i CAWS to address these problems. |
Looking at the data stream, like:
there is no way to know what device collected the measurement or data item(s).
It is not part of the
Trigger
since in the protocol, this is stored in theTaskControl
.How should we store this?
Maybe @Whathecode has thought about this?
The text was updated successfully, but these errors were encountered: