10.06.2016 Views

eldo_user

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Speed and Accuracy<br />

Time Step Control<br />

Usage of a Fixed Time Step<br />

More About Time Step Control<br />

Eldo can also ‘clamp’ the time step to both a minimum value and a maximum value.<br />

To clamp the maximum time step you want to allow, use the HMAX option. Eldo will perform<br />

all of its normal time step control as explained in “Overview of Time Step Control Algorithms”<br />

on page 1248, but still not take any step larger than HMAX. Use this option carefully, as setting<br />

HMAX to a smaller value than required may force long simulation times. Unless very clear<br />

suspicion exists that the result is corrupted due to the selected time steps being too large, this<br />

option should not be used.<br />

To clamp the time step to a minimum value, use the HMIN or ABSOLUTE_HMIN options.<br />

These are potentially dangerous options: if HMIN/ABSOLUTE_HMIN is set to too large<br />

values, it prevents Eldo from using the time step it should use to maintain the accuracy within<br />

the specified tolerances. Unexpected results or failures are possible if using an inappropriate<br />

HMIN/ABSOLUTE_HMIN value. The default value for HMIN/ABSOLUTE_HMIN is 1ps.<br />

Unless speed improvements are a necessity, it is best not to increase HMIN/<br />

ABSOLUTE_HMIN. Setting HMIN/ABSOLUTE_HMIN to lower values can be useful for<br />

designs with very fast transitions.<br />

To control the ‘acceleration’ of the time step when convergence is easily obtained, use the<br />

HACC option. The overall goal of Eldo is to take the largest time step possible, while still<br />

providing results that are within the requested tolerances (typically specified with EPS,<br />

RELTOL, etc.). Every time a time point has been computed and accepted, Eldo will perform<br />

some analysis and computations to determine what the next optimal time step should be for the<br />

next time point. If convergence is easily obtained (that is, with very few iterations) and if the<br />

LTE constraints are verified with a large margin, Eldo will attempt to take a larger time step for<br />

the next time point by multiplying the current time step by a certain acceleration factor, as<br />

specified by HACC. The default value for HACC is 2, which means that Eldo will attempt to<br />

multiply the current time step by 2 at most.<br />

Specifying a value with option HACC overrides the default value of 2. This time step<br />

acceleration strategy is a compromise; choosing a conservative value (1.1x for example) would<br />

provide very little speedup, but the next time point would most likely easily converge.<br />

Alternatively, choosing a large factor (10x for example) when convergence is easily obtained is<br />

tempting, and would in theory provide a significant speedup. However, chances are high that<br />

the time point computed with the new (too) large time step will either not converge because of<br />

non-linearity, or will have to be rejected because the LTE constraints will be violated. In these<br />

cases, Eldo would then step back and recompute a new time point with a smaller time step (see<br />

the option FT). Therefore, an aggressive value might be a worse choice than a conservative one.<br />

The default value, 2, reflects this compromise and is a robust choice providing, on average, the<br />

best results. Unless you have very good reasons to do so, you are advised against changing the<br />

value of HACC.<br />

Eldo® User's Manual, 15.3 1251

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!