Fix typo in training/d22278a0.json task #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There seems to be a typo in the test output grid at (zero-based) index (x=8, y=7), where it should be yellow (color 4) rather than empty (color 0).
|
@fchollet can I suggest that a formatter is applied to the JSON files. That way, with multiline files, diffs in a PR will more easily show and be understood. |
fchollet
approved these changes
Nov 17, 2019
|
@leapingllamas: formatted or not, the contents are impossible to interpret without a visualizer. |
nesco
pushed a commit
to nesco/ARC-AGI
that referenced
this pull request
Jul 24, 2024
Fix typo in training/d22278a0.json task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There seems to be a typo in this task's test output grid at (zero-based) index (x=8, y=7), where it should be yellow (color 4) rather than empty (color 0).
Note that both me and my wife solved the problem separately and arrived at the same answer, which only differs from the current answer by this one pixel (although, we arrived at the same conclusion through different thought processes!). That said, it's certainly possible that we're both mistaken, of course, in which case feel free to close this PR.
Thanks!