Skip to content
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

Open
petkish opened this issue Jul 4, 2024 · 7 comments

Comments

@petkish
Copy link

petkish commented Jul 4, 2024

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:

  1. Either, correct the core to be 2x2, 3x3 or 4x4 and the added border thickness accordingly to 2, 3 or 4
  2. Or, leave the core 3x4, set the added border to changing thickness 3 in vertical parts but 4 in horizontal parts.
@petkish
Copy link
Author

petkish commented Jul 4, 2024

Screenshot_2024-07-03-15-01-27-072_com android chrome~2

@yuedajiong
Copy link

please consider boundary. :-)

@petkish
Copy link
Author

petkish commented Jul 5, 2024

yuedajiong: please consider boundary. :-)

Shall the boundary in the input field influence the thickness of the generated boundary in the output?
If yes, I believe there are too few examples for this pattern.

@yuedajiong
Copy link

yuedajiong commented Jul 5, 2024

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.
That is, this is NOT a good (enough) AGI task design, it just focus on a small block (just part of abstraction and reasoning) of all necessary abilities. If no priori, STILL no algorithm(answer); please notice the word STILL.
e.g: strong-priori-needed, no-random-factor, no-representation-requirement, iteration-in-algorihtm-is-not-necessary, ...

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.

@petkish
Copy link
Author

petkish commented Aug 20, 2024

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.

@lenyabloko
Copy link

I think ARC is not about "good enough" but about the best fit.

@MischaMegens2
Copy link

I think the first example is odd, since it just complicates matters for no reason, without it the puzzle seems perfectly solvable.
Of course I can come up with additional rules to 'fix' the first example to force it to fit in ('...but if the added border touches the edge then that limits its width', à la yuedajiong) but to me this is artificial.
Now if there would have been an additional example showing what happens with a non-square central part when there is a sufficiently large border (A different thickness on the top/bottom vs left/right? Or a uniform thickness somehow related to the dimensions of the center?) then I would be more willing to accept example 1. But currently, it leaves me wondering what an asymmetric central part would normally do, yet brings no benefit towards solving the test. So I'm with petkish, this one is not so pretty.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants