-
Notifications
You must be signed in to change notification settings - Fork 20
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
Different way of defining convolutional structure #19
Labels
Comments
schrum2
added a commit
that referenced
this issue
Sep 8, 2017
I added the command line parameter for #19 but before I could do any further work with it, I noticed an error that affects how zero padding is applied. My previous test of zero padding had terrible results, but fixing this error should change that. It may not be significantly better than not using zero padding, but it should at least work. I also added a batch file for testing ... though I'm surprised I didn't already have one.
schrum2
added a commit
that referenced
this issue
Sep 8, 2017
Turning this on should define the CPPN inputs for creating the convolutional network in the same manner as Verbancsics. This seems to work fine for networks using separate outputs for each layer pairing, but actually does not work well (in Tetris) when using substrate coordinate inputs ... but this is exactly what Verbancsics did! The only difference I can think of that might be having an impact is the use of the substrateMapping. Verbancsics used center scaling in all experiments, but my Tetris substrateMapping goes from top to bottom. Worth checking.
schrum2
added a commit
that referenced
this issue
Sep 8, 2017
Commented section shows how to force center scaling when using Verbancsics' method, but it didn't really help, so I'll just leave it the way it was before.
Completed. This alternate approach performs fine with separate outputs for each linked substrate pair, but not so well when the substrate location coordinates are input, which is actually what Verbancsics did. this is a little odd. Despite this oddity, I'm closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From MM-NEATv2: schrum2/MM-NEATv2#460
The text was updated successfully, but these errors were encountered: