-
Notifications
You must be signed in to change notification settings - Fork 36
Version 0.9.0 #148
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
Merged
Merged
Version 0.9.0 #148
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tates_in_model_functions
…raic variables) as hidden state, and do no longer generate code for it. - Added function removeHiddenStates(equationInfo). - Remove hidden states, before parameters are evaluated with propagateEvaluateAndInstantiate!(..). - Rename function addOrUpdateStateInfo(..) to addState(..). - Remove not used vector x_infoByIndex from EquationInfo.
…ed by function derivatives!(..))
…deepCopy is performed now on all arguments of addToResult(..)
…ove "nominal" column from logStates output, since nominal has no effect currently.
…instantiated SimulationModel is generated that is passed to propagateEvaluateAndInstantiate!(..) for _instantiateFunction(..).
…, since x_hidden an derx_hidden have the same element indices.
… message, if core.eval(..) fails, e.g. due to a wrong user input.
…result; better error messages in propagateEvaluateAndInstantiate!(..)
- The initial state vector was not always correctly filled with start/init values of the model (is now fixed). - signalNames(..) did sometimes not show the correct signal names available in the result (is now fixed). - Parameters are no longer seen as part of the result (e.g. signalNames(..) does not return parameters). - Parameters can be accessed with new functions: hasParameter, getParameter, getEvaluatedParameter, showParameter, showEvaluatedParameter - More tests in Modia/test/TestLinearSystems.jl - Replacing "using Test" by "using Modia.Test" in the test models. - @showModel: Number arrays are printed in a nicer way. - Docu Modia/Functions improved
…er(a.b.c)`, has now the correct name `a.b.der(c)` in the result. For example, the plot command needs to be changed to `plot(..., "a.b.der(c)")` instead of the previous command `plot(..., "der(a.b.c)")`.
… visible in the generated code.
- newExtraResult!(..., defaultExtraResult): Add argument defaultExtraResult and push! it on result_extra_temp - Rename addZeroCrossings to newZeroCrossing (for consistent naming convention) - New function getStateStartIndexFromHiddenStateStartIndex(..)
…ement that is printed in case of an error, since printing with units is nearly unreadable.
…mum absolute value of the difference
…(instantiatedModel)
to get rid of the potential StackOverflowError (SciML/DiffEqBase.jl#784)
…in TestFirstOrder2.jl (especially, writing signals to file)
…iaSim/Modia.jl into mo_states_in_model_functions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.