Bradley Carman
Bradley Carman
`Plots` has a [bug](https://github.com/JuliaPlots/Plots.jl/issues/1074), you need to use PlotlyJS instead... 
To make my question more clear, I've added a MWE here: https://github.com/bradcarman/ExampleApp When attempting to run the `App/test/runtests.jl` as the `precompile_execution_file` I get the following error... ```julia julia> create_app("App", "AppCompiled";...
OK, I see what the problem/solution is. I've implemented the following on a fork... ```julia function run_precompilation_script(project::String, sysimg::String, precompile_file::Union{String, Nothing}, precompile_dir::String; extras_project::Union{String,Nothing}=nothing) tracefile, io = mktemp(precompile_dir; cleanup=false) close(io) arg =...
In general I think the show() function should work. However even though I include the semicolon ";" at the end, the result (14) is still displayed along with the table....
`step!` fails to build a solution sometimes (i.e. integrator and solution time can fall out of sync)
The bug is not about the resolution of the time. I understand that `25*dt != sdt`, but what is true is `25*dt ≈ sdt`. What I'm seeing is the solution...
`step!` fails to build a solution sometimes (i.e. integrator and solution time can fall out of sync)
`saveat=dt` is a requirement because I can't reset the integrator without it. ``` julia> SciMLBase.set_ut!(integrator, copy(integrator.sol(0)), 0) ERROR: Integrator state cannot be reset unless it is initialized with save_everystep=false ```
`step!` fails to build a solution sometimes (i.e. integrator and solution time can fall out of sync)
For my real system I'm attempting to run a step and extract the observables, therefore I need a solution object to do that. For the MWE of course the solution...
`step!` fails to build a solution sometimes (i.e. integrator and solution time can fall out of sync)
OK, that works, I'm able to do the following which allows me to get the solved variables (`integrator.u`) and observables from `integrator.f.observed()` like so... ``` step!(integrator, dt, true) integrator.f.observed(num, integrator.u,...
Hi, I'm reviewing the code and I noticed that the Flange connector uses absolute position for the state variable. Might I suggest changing this to velocity? The reason for this...
In this example the spring starts at it's natural length (i.e. uncompressed), therefore one should not need to specify `s_rel0`. By using position rather than velocity, this overcomplicates the model...