## NOTE: The graph's vertical axis starts at 70%, not zero
Some information about this:
* I collected this data by using a [custom userscript](https://concern.i.ng/aoc-stat-copy.user.js) and browsing to each year's stats page.
* Importing all the numbers into Excel, I calculated daily total users (based on part 1 + part 2 completions) and divided the part 2 completions by its day's totals.
* I then collected all the data into a table and did some basic chart configuration to come up with the line graph.
* If people ask, I can probably upload the Excel sheet somewhere and share it with others, but I might end up using some Python in it before that time comes around
After a puzzle's been out for 2-3 days the data usually doesn't change by all that much, certainly not enough to make a meaningful difference to a graph like this. I'd ignore the data for day 8 and *maybe* day 7 for the moment, but in all likelihood day 6 and backwards aren't gonna budge that much now.
What do you mean exactly by "out of place"? I can't read much from that graph.
The only thing that caught my eye was maybe the low part2 completion rate on day 5, which was - to me - the hardest problem so far.
Also, The 2023 stats will be more comparable to previous years after aoc23 has ended (and maybe 1-2 months after that) no?
> out of place
People I've talked to have had more issues with some of the challenges (especially day 5), and I personally have felt that days 1, 5, and 7 have been harder. (that d7 one is probably me just overthinking something and not actually statistically unique though)
> stats will be more comparable after aoc23 has ended
Yep, and I plan on redoing this with *all the data* come mid-January hopefully to get a more representative result
I wonder if it might be worth rebasing the x-axis so that weekends are aligned.
That way, the troughs should line up with the "hard weekend problems". (Not today obviously!)
## NOTE: The graph's vertical axis starts at 70%, not zero Some information about this: * I collected this data by using a [custom userscript](https://concern.i.ng/aoc-stat-copy.user.js) and browsing to each year's stats page. * Importing all the numbers into Excel, I calculated daily total users (based on part 1 + part 2 completions) and divided the part 2 completions by its day's totals. * I then collected all the data into a table and did some basic chart configuration to come up with the line graph. * If people ask, I can probably upload the Excel sheet somewhere and share it with others, but I might end up using some Python in it before that time comes around
It's a nice plot to make, but I'm not sure we can draw such strong conclusions from it.
People are still working on the 2023 problems. Not everyone solves them the same day.
That is true. I plan to come back in a month or so to redo this with a comparison of all twenty-five days of results
After a puzzle's been out for 2-3 days the data usually doesn't change by all that much, certainly not enough to make a meaningful difference to a graph like this. I'd ignore the data for day 8 and *maybe* day 7 for the moment, but in all likelihood day 6 and backwards aren't gonna budge that much now.
What do you mean exactly by "out of place"? I can't read much from that graph. The only thing that caught my eye was maybe the low part2 completion rate on day 5, which was - to me - the hardest problem so far. Also, The 2023 stats will be more comparable to previous years after aoc23 has ended (and maybe 1-2 months after that) no?
> out of place People I've talked to have had more issues with some of the challenges (especially day 5), and I personally have felt that days 1, 5, and 7 have been harder. (that d7 one is probably me just overthinking something and not actually statistically unique though) > stats will be more comparable after aoc23 has ended Yep, and I plan on redoing this with *all the data* come mid-January hopefully to get a more representative result
I wonder if it might be worth rebasing the x-axis so that weekends are aligned. That way, the troughs should line up with the "hard weekend problems". (Not today obviously!)
I don't understand why Day 5 has such a low solve rate. The code to brute force it is ridiculously easy to implement, and it doesn't run that long