Opened 8 years ago
Last modified 8 years ago
#4014 assigned defect
Unexpected behavior of Start Time
Reported by: | Jan Kokert | Owned by: | Willi Braun |
---|---|---|---|
Priority: | normal | Milestone: | Future |
Component: | Interactive Environment | Version: | v1.11.0 |
Keywords: | Cc: |
Description
I have a simple RC circuit model and I want to simulate (output) only the results for times greater than a certain time (=10s), like in LTSpice.
So I put 10 in the Start Time field. But what actually happens now is that the whole simulation has a time offset of 10s and initializes at 10s.
Sure, the time from 0s..10s needs to be simulated internally, but I don't want so see it (see next ticket).
Is the expected behavior wrong or is there a bug in OM?
Thank you for revising!
Change History (4)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Ok I see, a time offset can be useful indeed.
Actually I didn't suggest to change the behavior, I just wanted to know if "cutting" simulation results at the beginning (as in LTSpice) is possible. I didn't find any setting for this.
comment:3 by , 8 years ago
Component: | OMEdit → Run-time |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:4 by , 8 years ago
Component: | Run-time → Interactive Environment |
---|
It is possible to add such a function to the scripting api. But I'm not sure if this is really needed. However, there is already an option to resample simulation results, so maybe we could just add this as well.
For me setting t= 10s as start time does that simulation has to start at t=10s.
For instance if I have a step function with step at 11s In this case the step will be after 1s of simulation. Without using start time=10s it would have been after 11s of simulation.
So I think the present way OM behaves has good logic and I'm not sure that changing it would be better.