Question: Sparse heterogenous data
- Langage dominant
- Rust
- Étoiles
- 42
- Forks
- 6
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hi, Rudiger, et al,
David Phelan has asked me to look at using this library for dClimate, and I was hoping you could help answer a question for me.
We have weather station telemetry data that has the general form:
| timestamp | var1 | var2 | var3 |
-------------|------|------|------|
| 2023-05-18 | 2.1 | | 6.5 |
| 2023-05-19 | 2.1 | | 6.5 |
| 2023-05-20 | | | |
| 2023-05-21 | 2.1 | 4.2 | |
| 2023-05-22 | 2.1 | 4.2 | |
| 2023-05-23 | 2.1 | 4.2 | 6.5 |
In plain English, for a specific index, we have several variables, any of which may or may not have a value.
David did point me to this [older work](https://rklaehn.github.io/2018/06/10/efficient-telemetry-storage-on-ipfs/) where it's clear you were thinking about heterogenous data and missing values, but looking at the Banyan repository, it's not obvious to me how these are handled. Is this use case accounted for with Banyan, or should we be looking elsewhere?
If this is an accounted for use case, what's the best way to go about it? Use a separate tree for each variable, using Option\ for the value, or use a single tree with a tuple value?
I'm not sure if this is related or not, but I don't have a good handle on what the "Forest" abstraction is or does. Is there any information you could provide about that?
Thank you!
Chris
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
This is an unanswered usage question rather than a scoped change; no files, tests, or entry points are named. Start by reading the Banyan repository's treatment of Forest, heterogeneous values, and missing data, then establish whether the requested telemetry model is supported and document the recommended approach. Done means the use case, Forest abstraction, and choice between separate trees and tuple values are clearly answered.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- rust
- Domaine
- documentation
- Type d'issue
- Documentation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 20/100