Update allowed size of acquisition database #323
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update allowed size of acquisition database.
Because I used h5 badly when making the database, it grows I think via a leak mechanism. So I've got the job set to ask me to repack it when it gets too big. We could also auto-repack it or fix the underlying problem, but for now, I think it makes sense to increase the size where I get a warning, because the database when compressed is getting closer to the limit (it was 44Mb repacked today).
Interface impacts
Testing
Unit tests
Independent check of unit tests by [REVIEWER NAME]
Functional tests
I just tested this with a local install and the current (just over 50MB database), showing that the flight code gives a warning and the new PR code does not.