General Discussions
Discuss any topics that are not product-specific here.
Easier than day 1 and I'm still in it...
Spoiler
A straightforward parsing process to begin with. I used text to columns to isolate the Game ID, then split to rows on the game phase. I then used a multi-row to assign a phase number, then I used text to columns and regex to strip out the bits I needed.
For part one, it was then a matter of cross-tabbing into an aggregate set by Game and phase, then stripping out the actual numeric value of the game. I then used a filter to isolate those that did not violate the limits, then used the join to join those game numbers that had a violation, so I took the ones on the left output, those being the ones that did not exceed the limits, then simply summed the game numbers.
Part two was a simple grouping, then applying the multi-row power calculation (grouped by game ID), then taking the max of those and summing the total.
A straightforward parsing process to begin with. I used text to columns to isolate the Game ID, then split to rows on the game phase. I then used a multi-row to assign a phase number, then I used text to columns and regex to strip out the bits I needed.
For part one, it was then a matter of cross-tabbing into an aggregate set by Game and phase, then stripping out the actual numeric value of the game. I then used a filter to isolate those that did not violate the limits, then used the join to join those game numbers that had a violation, so I took the ones on the left output, those being the ones that did not exceed the limits, then simply summed the game numbers.
Part two was a simple grouping, then applying the multi-row power calculation (grouped by game ID), then taking the max of those and summing the total.
Go #TeamMcEleavey!
I was looking for the sneaky trick in part 2 but was pleasantly surprised that there was none.
Today was a good day to get things like setting up a GIT repo; making a donation to AOC to get that ++ tag etc.
Spoiler
This solution is 2 parts:
- the parser (the brush icon) cleans up the data to the shape we need it to start doing the job
- then we can start doing the calc
- and on the end you'll see the test harness that keeps me honest as I try different things.
Here's the parser - super rudimentary:
This solution is 2 parts:
- the parser (the brush icon) cleans up the data to the shape we need it to start doing the job
- then we can start doing the calc
- and on the end you'll see the test harness that keeps me honest as I try different things.
Here's the parser - super rudimentary:
Oh my goodness part 1 was a bit of a head twister with everything you have to check. Loved that part two was an easier one to solve. Will have a go at removing all the unnecessary tools I used later. Busy day. But glad I solved another day. Whoop.
