HI John, I agree that I can specify an absolute value after defining my settling time. But the problem is when you have a ringing output, you will cross the desired absolute value specified multiple times before settling to the final output. In that case, I wont know which time to take as the settling time.
And like you said, I am creating a generic measurement and I expect it to work for multiple cases such as damped response, undamped response. Let me know if I misunderstood your suggestion :) Thanks Seshadri John Griessen-3 wrote: > > Seshadri V wrote: > the simulator identifies only the first rising edge of the >> output and the oscillations following the first overshoot are not >> identified >> by the simulator. > > I bet you can tell gnucap to stop at an output absolute value and be right > on the definition of settling > time though. Settling "time" would just be start to stop time. > > Are you wanting to automate thousands of such runs? It's easy to see > running sims one at a time... > > John > (Gnucap newbie) -- I bet Al will have a more specific suggestion for > settling time. > > > > _______________________________________________ > Help-gnucap mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/help-gnucap > > -- View this message in context: http://www.nabble.com/Settling-time-measurement-for-underdamped-systems-tp24506699p24510429.html Sent from the Gnucap - Help mailing list archive at Nabble.com. _______________________________________________ Help-gnucap mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gnucap
