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

Reconcile sensor and level between Kvalobs and LARD #41

Open
Tracked by #56
Lun4m opened this issue Dec 11, 2024 · 2 comments
Open
Tracked by #56

Reconcile sensor and level between Kvalobs and LARD #41

Lun4m opened this issue Dec 11, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Lun4m
Copy link
Collaborator

Lun4m commented Dec 11, 2024

A missing (sensor, level) pair in the Obsinn message format is treated differently by Kvalobs and LARD.

Obsinn param code Kvalobs Sensor Level LARD Sensor Level
TA ('0', 0) (NULL, NULL)
TA(0,0) ('0', 0) (0, 0)

While migrating from Kvalobs, it's impossible to tell the difference between the two cases, unless the timeseries is already present in LARD. And after the migration, we might end up with timeseries data split between two labels.

@ketilt
Copy link
Collaborator

ketilt commented Dec 11, 2024

Will it help to have a tool that dedupes cases of suspected duplication? That is, if similar timeseries are checked to be fully identical, then the "least preferred" one will be removed and archived?

@Lun4m
Copy link
Collaborator Author

Lun4m commented Dec 11, 2024

Yes, that's the idea, unless we decide to change how LARD works in this regard

@Lun4m Lun4m added the bug Something isn't working label Dec 14, 2024
@intarga intarga mentioned this issue Jan 7, 2025
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants