I agree with @Cryptocorn , this pre-proposal should be voted as a single proposal with ACCURATE if it is the wish of both proposers. The idea of changing the trailing average to a value that is best suited for the update period and traffic randomness (relay changes) is good.
Meanwhile I wanted to ask for more information. The provided spreadsheet does not show how the values were calculated. Also, it shows only a 30 day period, this means that there is a single point of data (one update of the 30 days case).
-
Can you provide the formulas that you are using? (the spreadsheet shows only values, the operations are hidden)
-
Is it possible to compare the deviations on more points? (there is at least one year of data available)
-
style comment, please use ISO date format.
I think that a series of curves showing the expected and total minting using different trailing averages (30-day, 7-days, 15-days, etc) over larger periods of time will provide more insight on what is the best value for the trailing averages. The curve with less deviation from the expected value should be used.
A comment that is more related to ACCURATE: The provided spreadsheet shows how using two different trailing averages affects the over-minting in monthly, weekly and daily updates. This analysis can be used to justify the selected update cadence, using the same reasoning as proposed above.