You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've attempted this before but stopped due to how much time it can take to run.
Because the table tool already filters after time and geography steps, we want to get every option under every filter and then make a big cube of all the possible combinations.
We then want to check if all of those combinations exist in the data file.
Filter groups will need to be handled as a special case, potentially by smushing into a single string that covers both cols?
Then likely need to present back to the users in a way that is helpful, ideally some kind of visual table where they can see (or download) to understand what is missing.
Once the multi-layer hierarchies work is in EES, we could enforce this more strongly and then anyone who needs to will use the breakdown / breakdown topic approach.
This will need some heavy performance testing, and use of the most efficient functions possible given the potential size of what needs to happen here as files get bigger.
Worth looking at something like Git LFS to hold some larger test files we can use in performance testing.
The text was updated successfully, but these errors were encountered:
We've attempted this before but stopped due to how much time it can take to run.
Because the table tool already filters after time and geography steps, we want to get every option under every filter and then make a big cube of all the possible combinations.
We then want to check if all of those combinations exist in the data file.
Filter groups will need to be handled as a special case, potentially by smushing into a single string that covers both cols?
Then likely need to present back to the users in a way that is helpful, ideally some kind of visual table where they can see (or download) to understand what is missing.
Once the multi-layer hierarchies work is in EES, we could enforce this more strongly and then anyone who needs to will use the breakdown / breakdown topic approach.
This will need some heavy performance testing, and use of the most efficient functions possible given the potential size of what needs to happen here as files get bigger.
Worth looking at something like Git LFS to hold some larger test files we can use in performance testing.
The text was updated successfully, but these errors were encountered: