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

debugging asserts #901

Closed
Mathadon opened this issue Mar 29, 2018 · 2 comments
Closed

debugging asserts #901

Mathadon opened this issue Mar 29, 2018 · 2 comments

Comments

@Mathadon
Copy link
Member

I'm getting following error message in Dymola

4166.666666666667 < 836800.0*max(8.333333333333334E-07, 0.0008333333333333334)
The following error was detected at time: 0
Energy may not be conserved for small mass flow rates. The implementation may require prescribedHeatFlowRate = false.

this gives zero indication as to what component is causing the problem, which is annoying when debugging a full building model. Is there any way that we can include a variable or model name in the assert message?

@Mathadon
Copy link
Member Author

In this case it was a heaterCooler_T with fixed flow rate and fixed heat injection, which is likely the reason why the variable names are not mentioned (since their values are fixed).

@mwetter
Copy link
Contributor

mwetter commented Mar 29, 2018

You can use the getInstanceName() function of Modelica. This would be good to add.

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

2 participants