A new Just KNIME It! challenge has just been released!
This week we have a relatively easy challenge focusing on data preprocessing. A great opportunity for those who are new-ish to KNIME to learn how powerful it can be. And for the veterans… We want to see how creative you can get here! hehe
This challenge was basically proposed by @HansS and @bruno29a, and we’d like to use it as an opportunity to remind you that you too can suggest challenges for us here. We’d love to hear it!
Here is the challenge. Let’s use this thread to post our solutions to it, which should be uploaded to your public KNIME Hub spaces with tag JKISeason2-4 .
Need help with tags? To add tag JKISeason2-3 to your workflow, go to the description panel on the right in KNIME Analytics Platform, click the pencil to edit it, and you will see the option for adding tags right there. Let us know if you have any problems!
here’s my take on the challenge:
I made a small edit on the data, introducing new levels of aggregation.
Have a nice evening,
Hi all, here is my solution but too many nodes…
This is my solution for the @bruno29a and @HansS 's proposed challenge 04. I think (no tested yet) that it can scale for inter year project expenditures.
I’ve also deployed a component, where front user can select the time frame for the desired output table by area.
I hope all this makes some sense
Here is mine
Divide area A and area B first, then processed according to different time requirements through the Python node.
You can see the python code here
For the natural communication purpose of “Just KNIME It”, the default notify setting(In the Just KNIME it Categories) should be “Watching”
Here’s my solution. More brute force than elegance, but it works.
Hello, here is my solution, this time is not complicated and with several steps like my previous challenges but is simple and covers the instructions listed in this challenge.
This is the flow, very simple:
This is the final result:
and can see and download in the following URL: JKISeason2-4 – KNIME Community Hub
Very nice and simple, with the use of Python, thanks for teaching us other ways.
Here is my solution to this challenge:
This was interesting, as I tried to create a component and also make this configurable (aka choose less than 12 months or less than 4 quarters) - great learning from @tobias.koetter and @Martyna at the KNIME Summit on how to make your workflows more flexible
Attn: If someone downloads my workflow, make sure to delete the big yellow annotation and all the nodes in it, as it is only to showcase on the Community Hub what is inside the component.
ps: if you want to discuss the current challenge in German, I host tomorrows DACH study group for it, make sure to sign up here (official KNIME link ): Just KNIME It - Lerngruppe - Herausforderung #4, Fri, Apr 21, 2023, 3:00 PM | Meetup
My Submission for challenge -4 .Tried the joiner node with sets /lists/ concatenate of months / quarter while figured out that sets/ list are not supported in joiner node for matching string column.
RECORDAD que cada viernes charlamos sobre las soluciones propuestas, grupo de ESPAÑA
Here my solution:
Found a simple path to this week’s challenge
@josedesouza - Good one while Larger and complex period manipulation may have issue as we are incorporating input table data as reference too here in lookup table.
while working on challenge 4- i was trying to use a output of group by node with values as ( Sets/list/concatenate ) for matching.The joiner table doesnt accept the set/ list column or even if its string output as in concatenate. Adding the workflow for reference and advice for work around /approach
Justknimeit -S2C4.knwf (27.2 KB)
here’s my take on the challenge:
here is my solution.
Hello KNIMErs, Here is my Solutions for “Just KNIME It!” Challenge 04 – Season 2