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

Harmonize Constant/FixedParameter/ConstantParameter #975

Open
FFroehlich opened this issue Feb 22, 2020 · 3 comments
Open

Harmonize Constant/FixedParameter/ConstantParameter #975

FFroehlich opened this issue Feb 22, 2020 · 3 comments
Labels
breaking change Issue changes API in backwards-incompatible way refactoring

Comments

@FFroehlich
Copy link
Member

happy to discuss what they should be called.

condition
feature
constant

@FFroehlich FFroehlich added refactoring breaking change Issue changes API in backwards-incompatible way labels Feb 22, 2020
@dweindl
Copy link
Member

dweindl commented Feb 22, 2020

I am also in favor of finding more appropriate names, as it is often confusing. No good solution, just some thoughts:

What is different for those parameters and others? We don't compute sensitivities with respect to those. So they are generally not estimated, but known. Is "input parameter" appropriate? Somehow. But it may also include known output parameters, making it at least sound somewhat contradictory.

"Condition parameters": Often makes sense, as they are used to account for different conditions a model should represent. On the other hand, we may want to estimate condition parameters as well, and therefore they would be in the non-condition group.

"feature": Not very descriptive. Could be anything?

"constant": All model parameters are constant over time. These parameters are not constant over conditions. They are constant for one condition over the course of the optimization. Makes sense, but not sure if it is the first association, as AMICI itself does not care greatly about optimization.

Other "types" of parameters we may want to distinguish, orthogonal to the sensitivity thing, but maybe good to consider to avoid ambiguities: parameter influencing the dynamics of the system vs output-only parameters.

@dweindl
Copy link
Member

dweindl commented Mar 6, 2020

Any other opinions here?

@FFroehlich
Copy link
Member Author

The reason why I was thinking about feature is that those fixed parameters, as you say, really could be anything related to the experiment. If one would train a machine learning model, these quantities would be called features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Issue changes API in backwards-incompatible way refactoring
Projects
None yet
Development

No branches or pull requests

2 participants