Error messages #467
Replies: 3 comments 2 replies
-
|
@moorepants : Since you may be getting closer to releasing the next opty, I'd like to raise this again. My feel is that such error messages may prevent an inexperienced uses to go on a wild goose chase. |
Beta Was this translation helpful? Give feedback.
-
|
I see your point - but I am putting myself into the shoes of an opty user - which I am. It is probably a rare thing to happen: You'd have to declare a state variable, which does not appear in the eoms and then bound it. |
Beta Was this translation helpful? Give feedback.
-
|
Clear. So if I think, it is fast and worthwhile, I can push and you will merge or close as you see it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Today, by accident, I had an instance_constraint for a state variable, which I had replaced with an eom_bound, so it no longer existed.
I got some error message which did not point to this problem at all.
My question: If I come across something like this, is it o.k. to suggest a way to raise an error which points the user to the problem?
Beta Was this translation helpful? Give feedback.
All reactions