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

Control variables are clasified in a module when they appear in a view as a model variable #357

Closed
enekomartinmartinez opened this issue Aug 24, 2022 · 1 comment

Comments

@enekomartinmartinez
Copy link
Collaborator

The control variables (TIME STEP, INITIAL TIME, FINAL TIME, SAVEPER) are classified in a module when they appear in that view as a model variable and the model translation is split by views. This provokes a crash during model loading.

We should define their values always in the main file filtering the variables.

We should also include a warning for control variables when they are defined in a view or for those regular variables that are defined in more than one view.

@enekomartinmartinez
Copy link
Collaborator Author

Solved in branch views. I will open a PR soon.

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

1 participant