-
-
Notifications
You must be signed in to change notification settings - Fork 554
Saddle Point: Uses y, x coordinate values, rather than x, y #313
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
Comments
I think this is my fault. I tend to get the order wrong when listing points in a Matrix. (I also have trouble with left and right, which is troubling in a completely different way). |
It is at least noted that https://en.wikipedia.org/wiki/File:Matrix.svg uses the same ordering of coordinates (although 1-based rather than 0-based). Also see that if the matrix is stored as The opposition is that (x, y) is conventional in other applications with grids. Whatever choice we make, we can certainly clarify it in the README. Finally, surely there are some expected coordinates in tracks' test suites. What do they say about which coordinate should come first? |
I'll try to summarize what I think to make things clearer in my head:
|
Thanks, I agree, the numbering is correct, and definitely appropriate for the exercise. The change, then, is to note the matrix ordering, which is down -> right. |
If we use matrix indexing, we should probably start indexing at (1,1) to avoid creating a non-standard indexing that will confuse users. Edit: I don't think it would be problematic to use "Computer" Cartesian in this exercise, if you think it would be easier for users to write the solution. I'm against just mixing the systems. Your original idea seems good. |
Putting it in examples, I think we should choose between these two options: Matrix indexing
"Computer Cartesian" indexing
|
Should we then provide the value at that point, either way?
|
That would help a lot! 😄 |
Also address the removal of the messages that were in the test data, but are no longer there. Clean up the template for skips. fixes #313
It appears that the saddle point at 1, 0 is 8 (though the arrow distracts from this coordinates given) which goes against the "unambiguous definition above" as stated in the readme, though 8 is not following the rules of what it means to be a saddle by the definition given.
The point at (0, 1) however, which is 5 does fulfil this definition. And matches the grid "pointer".
Edit: The change, then, may be to change the coordinate shown as (1,0) to (0,1).
The text was updated successfully, but these errors were encountered: