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

Think about the "ops" handling #105

Open
TristanHehnen opened this issue Dec 2, 2021 · 1 comment
Open

Think about the "ops" handling #105

TristanHehnen opened this issue Dec 2, 2021 · 1 comment

Comments

@TristanHehnen
Copy link
Contributor

if ops is None:

Is it a good idea to have the ops decoupled from everything? Wouldn't it be better to have it connected to something, like maybe the simulation setup or the optimiser properties or something? Otherwise it is lying around somewhat on its own and is likely confusing to others.

@TristanHehnen
Copy link
Contributor Author

Provide a convenient way to define basic optimisation setups. For example we could provide a further argument to the parameter class that determines if it is optimised or not. Then PROPTI can decide internally to sort the different parameters and users do not need to define different lists for parameter handling.

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