This table will be structured be similar to how pluto QAQC works, where each new version is appended as a new row to the existing table.
The question I have before I start writing code is whether to store the results for the previous versions or re-compute them each time. We could store the "correct" table with all versions so far in the main folder in DO that way we do for pluto. Alternatively we could just iterate through each previous version and sum each column each time the code is run. The query is simple enough that run-times should be fast. The question is just which design we feel is easiest to understand/extend
This table will be structured be similar to how pluto QAQC works, where each new version is appended as a new row to the existing table. The question I have before I start writing code is whether to store the results for the previous versions or re-compute them each time. We could store the "correct" table with all versions so far in the
main
folder in DO that way we do for pluto. Alternatively we could just iterate through each previous version and sum each column each time the code is run. The query is simple enough that run-times should be fast. The question is just which design we feel is easiest to understand/extend