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

params.mat mixes up variables of different mechanisms #37

Open
kupiqu opened this issue Feb 24, 2015 · 2 comments
Open

params.mat mixes up variables of different mechanisms #37

kupiqu opened this issue Feb 24, 2015 · 2 comments
Assignees

Comments

@kupiqu
Copy link
Collaborator

kupiqu commented Feb 24, 2015

Examples given:

External Poisson has variables from elsewhere:
MSN_extPoissonInputCoderEnabled_cm
MSN_extPoissonInputCoderEnabled_g_m

All other mechanisms also have external Poisson variables:
MSN_kCurrentMSN_g_ext
MSN_kCurrentMSN_rate_ext
MSN_kCurrentMSN_tau_ext

This seems to happen for the parameters which value is replaced in the main script.

@jsherfey
Copy link
Owner

This may not be an error --

Parameters that are specified by the user are considered global parameters in that they override any default values given in any of the mechanisms. They are defined for each mechanism so that they will be used if (and only if) they appear in any mechanism.

However, if this occurs for parameters that were not specified by the user, then this would be an error.

@kupiqu
Copy link
Collaborator Author

kupiqu commented Feb 24, 2015

Ok, but that is weird (confusing behavior, i.e. unexpected). How difficult would be to check whether the parameter exist and if not, do not process it further?

@kupiqu kupiqu added enhancement and removed bug labels Feb 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants