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

Neat's input and output parameters are useless if a network is provided #144

Open
flesler opened this issue Nov 7, 2018 · 1 comment
Open

Comments

@flesler
Copy link

flesler commented Nov 7, 2018

So I checked the code, at least within the neat module, the first 2 arguments (inputs and outputs) are only use to create the random network if none is provided.

This means that if one is, those 2 are useless and hence the calling code looks awkward. I think it should make more sense to make inputs and outputs also options (heck, make it accept just a single options object) and hence they are optional and only used (and required) if no template network is provided.

@flesler
Copy link
Author

flesler commented Nov 7, 2018

An extra comment, I notice that when a network is provided, it is used as a template as is. That means that either passing a random network or any other, means the first generation is all equal and does the same thing (AFAIU). Maybe it'd make sense to randomly mutate each template the first time?

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

1 participant