Advent of Code 2023 Day 2 (BaseA Style)

AlteryxCommunityTeam

Spoiler

Discussion thread for day 2 of the Advent of Code - https://adventofcode.com/2023/day/2

Advent of Code

Accepted answers

All comments

Gawa

It was moderate one, and manageable.

Spoiler

kelsey_kincaid

This was a nice change for Day 2 after a rough Day 1!

Spoiler

Part 1: Mostly just a parsing exercise. Probably could have done this in fewer tools with RegEx, but it was faster to use Text to Columns repeatedly since RegEx makes my head hurt.

Part 2: Just had to take the max number of cubes for each color used in each game and multiply them together. No big twists made me paranoid I was missing something, but I guess Eric decided to give us a nice Part 2 after yesterday. I'm guessing this just means tomorrow will be even trickier!

DaisukeTsuchiya

Easier then yesterday's one.

Spoiler

caltang

Much better than yesterday!

Spoiler

AOC23_Day2_caltang.yxzp

Qiu

Cost me time since did not read the instruction carefully ennough. 😁

Spoiler

Tokimatsu

Done.

Spoiler

joshbennett

Nice to have part 2 be easier than part 1 once in a while.

Spoiler

aoc_2023_02_joshbennett.yxzp

Watermark

Not elegant, but got the job done.

Spoiler

AOC 2023 Day2.yxmd

NicoleJ

It's been a good, good day... because I got to use a new feature from 23.2 Designer release (with the Custom Workflow Template I saved earlier today to use as my quick starting point every day for Advent of Code with a data download macro & input switcher)... AND then I also found a way to use not one, not two, but THREE new functions available in the 23.2 release as well! It feels like Christmas already!! 😁

Spoiler

Annotated the cleaned up/tool golf version with notes. I went for speed, not beauty, for the stars... and then went back to clean it up because 4 Text to Columns tools just felt a little ridiculous. 🤣

Day2.yxzp

AkimasaKajitani

My solution.

Spoiler

I used the RegEx tool to be easier for after part.

スクリーンショット 2023-12-02 151837.png

Designer Cloud version

Spoiler

Designer Cloud sampled the data, so I need to run the workflow to know the complete result. But I could make this workflow by the same approach of Designer Desktop.

Day02.yxzp

CoG

Not my first draft, but probably one of the simplest forms the solution can take:

Part 1:

Spoiler

Part 2:

Spoiler

Solution.yxmd

phottovy

How dare they let me regain a tiny bit of confidence!

Spoiler

aoc_ph_2023_02.yxmd

Yoshiro_Fujimori

My solution.

Spoiler

Workflow

AoC02.yxmd

Ladarthure

A lot easier today, no head banging on a saturday morning is appreciable

02.yxmd

Carlithian

Silly mistake on my part made this take way longer than it should have, but learnt something new with Regex, so happy with that

Spoiler

Carlithian - 231202.yxmd

cgoodman

Spoiler

A nice simple part 2. I felt like this one was a perfect showcase for Alteryx on splitting data and then aggregating.

AkimasaKajitani

Tool Golf

Spoiler

Day02_2.yxzp

Kenda

Spoiler

yay for the new product function in the Summarize tool!!

2.yxmd

FrederikE

Spoiler

02.yxmd

patrick_digan

Very similar to others

Spoiler

Day 2.yxmd

Gawa

Tool golf version. 9 tools excluding input tool.

Spoiler

AoC2023_Day2_golf_gawa.yxmd

mceleavey

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.

Go #TeamMcEleavey!

Day 2.yxmd

SeanAdams

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:
Screenshot 2023-12-02 075116.png

2023_Day02-Part2.yxzp

SeanAdams

thank you for continuing to point out where we can experiment with new features @NicoleJ - it really does help to highlight these new capabilities and give folk muscle-memory to try them.

I'm sure you're looking out for opportunities for the Control Containers to shine!

rachel_k

Similar approach to others. After yesterday, I felt like I had to check for any unexpected colors

Spoiler

day2.png

mmontgomery

W00t on the problem being very procedural!

Spoiler

2023_Day2.yxzp

Samantha_Jayne

Spoiler

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.

AoC_2023_SamiJayne_Day2.yxmd

IraWatt

Day 2 was a lot nicer then day 1 😅

Spoiler

Day 2.PNG

Two more stars done!

Decided to put a little bit more work into this one (while the challenge's are a bit easier) and got part one down to a single tool (not including the text input. quite happy with it

Spoiler

The multi row is configured basically the same as the formula, except it adds the game id as it goes down through the rows, so the value in the end row is the answer