-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In 3a301edc first example solution does not match the pattern observed in the other examples #124
Comments
please consider boundary. :-) |
Shall the boundary in the input field influence the thickness of the generated boundary in the output? |
Even if the author has a god-level generation 'rule', it doesn't necessarily mean it is 'unique'. In fact, once given the correct answer, we can also 'reverse-construct several equally correct god-level generation 'rules', such as those that include or exclude 'boundary' factor. If I have time, I will post an issue to analysis to thin dataset, in deep, focus on AGI tasks design. Of course, it is useful and good, just not good enough. I really appreciate this direction of AI task design, and personally, I think it is far more meaningful than training large language models. |
Look. Try to do a simple exercise: We know the correct solution, right? Now, use it as one of the examples. Then, forget that the example 1 has its solution and try to solve it as the_task. Do you have any problems? I did. So there is definitely something off with the example 1. |
I think ARC is not about "good enough" but about the best fit. |
I think the first example is odd, since it just complicates matters for no reason, without it the puzzle seems perfectly solvable. |
In the first example (gray core 3x4, yellow border) the added gray border is 2 pixel thick, which does not match the relation between the core size to the added border thickness in the other examples, which is the equality relation.
Correction possibilities:
The text was updated successfully, but these errors were encountered: