Skip to content

Conversation

@hyunsooCHOI0215
Copy link
Contributor

No description provided.

@kbumsik kbumsik self-assigned this Apr 8, 2018
@kbumsik
Copy link
Owner

kbumsik commented Apr 11, 2018

screenshot from 2018-04-10 23-54-52
I added printing the path in a maze for more intuitive debugging. I also added a full path from the start to path.
The path from the maze is from 2015 competition maze

@hyunsooCHOI0215 , you can update your computer with git pull origin master :)

@kbumsik
Copy link
Owner

kbumsik commented Apr 11, 2018

image
Now it prints all three settings :)

@hyunsooCHOI0215
Copy link
Contributor Author

hyunsooCHOI0215 commented Apr 11, 2018 via email

@kbumsik
Copy link
Owner

kbumsik commented Apr 11, 2018 via email

@kbumsik
Copy link
Owner

kbumsik commented Apr 11, 2018

image
Since this commit, it prints repeated number of moves instead of printing them all. Now we can take a look if the algorithm is okay...

@kbumsik
Copy link
Owner

kbumsik commented Apr 11, 2018

Here is my thoughts:

  1. Non-smooth: Looks fine in this test case. Well done :)
  2. Smooth: It is wrong with repeated forward moving and the last h missing. Here is the correction:
    15F -> h -> R -> h -> 13F -> h -> R -> h -> 5F -> h -> R -> L -> R -> L -> R -> h -> 2F -> h -> R -> h -> 1F -> h -> R -> h -> F -> h -> 2L -> h -> 1F -> h -> R -> h -> F -> h -> ....... -> L -> h
    Other than that, looks OK.
  3. Diagonal: It is not yet fully developed I think.

I will analyze the algorithm in detail soon.

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

Successfully merging this pull request may close these issues.

2 participants