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

Store data in giant records? #3052

Open
squaregoldfish opened this issue Jan 12, 2025 · 0 comments
Open

Store data in giant records? #3052

squaregoldfish opened this issue Jan 12, 2025 · 0 comments

Comments

@squaregoldfish
Copy link
Collaborator

squaregoldfish commented Jan 12, 2025

We can do this for data reduction because it's calculated in one go, and not edited piecemeal.

I'm also tempted to store it compressed, but that may be a step too far. Look into best practice.

In fact, we could do the sensor values too - in practice they're often dealt with en masse. The only exception is setting QC flags, which are done down to one at a time and should be written immediately. There's also the 'split' QC for positions and external standards.

@squaregoldfish squaregoldfish added this to the Short Term milestone Jan 12, 2025
@squaregoldfish squaregoldfish changed the title Store data reduction in one giant record? Store data in giant records? Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant