SimValueContext
SimValueContext holds context information for a trace, and describes how data for a trace should be extracted from the simulation. SimValueContext contains a list of 14 required initial values:
SimValueContext (
Domain ID, Calculation Type, Number of Cycles, Rise Time,
Step, Impulse, Context ID, Window Width,
Window Type, TDR Kaiser Parameter, Hold Time, DeviceName,
TDR Step Time, DR Maximum Time )
For example, the following indicates a trace in the Time Domain, Standard Calculation with the number of cycles being 2:
"SimValueContext:=", Array(1, 0, 2, 0, false, false, -1, 1, 0, 1, 1, "", 0, 0)
Additional, context-specific values may follow the required values, as described in subsection 15 below.
1. Domain ID
|
No Domain |
0 |
|
Time Domain |
1 |
|
Spectrum Domain |
2 |
|
Sweep Domain |
3 |
|
Device Domain |
4 |
|
SinglePt Domain |
5 |
|
LoadPull Domain |
6 |
|
Transient Domain |
7 |
|
Budget Domain |
8 |
|
NetworkFunction Domain |
9 |
|
Oscillator Domain |
55802 |
|
Noise Domain |
55803 |
|
Transfer Function Domain |
55807 |
|
Time Frequency Domain |
55808 |
|
Transient Time Domain |
55809 |
|
Periodic AC Domain |
55818 |
|
UI Domain |
55819 |
|
Eye Measurement Domain |
55823 |
|
Initial Response Domain |
55824 |
|
Peak Distortion Domain |
55825 |
2. Calculation Type
|
Standard Calculation |
0 |
|
Device2_DCIV |
1 |
|
Device3_DCIV_Output |
2 |
|
Device3_DCIV_Input |
3 |
|
Device3_DCIV_Transfer |
4 |
|
Device3_DCIV_Reverse |
5 |
|
Device2_ACLoad |
6 |
|
Device3_ACLoad_Output |
7 |
|
Device3_ACLoad_Input |
8 |
|
Device3_ACLoad_Transfer |
9 |
|
Device3_ACLoad_Reverse |
10 |
|
Constellation |
11 |
|
EyeDiagram |
12 |
|
FreeX ( Statistic Report ) |
13 |
3. Number of Cycles — Used in Time Domain in HarmonicBalance analysis.
4. Rise Time — Not used by Designer/Nexxim.
5. Step — Not used by Designer/Nexxim.
6. Impulse — Not used by Designer/Nexxim.
7. Context ID — Not used by Designer/Nexxim.
8. Window Width — Not used by Designer/Nexxim.
9. Window Type — Not used by Designer/Nexxim.
10. TDR Kaiser Parameter — Not used by Designer/Nexxim.
11. Hold Time — Not used by Designer/Nexxim.
12. DeviceName — Not used by Designer/Nexxim.
13. TDR Step Time — Not used by Designer/Nexxim.
14. TDR Maximum Time — Not used by Designer/Nexxim.
15. Context-specific values — Used in Time Domain in HarmonicBalance analysis.
Context-specific values are entered in the format "key, true/false, keyvalue", where:
— "key" is the name of the key being set.
— "true/false" indicates whether the key is a string value.
— "keyvalue" is the value of the key.
— The order of the context keys is not significant.
— Context keys have software defaults that will be used if not provided in the script.
a. Plotting Range for Time domain in Transient and QuickEye analysis:
|
Description |
Key Name |
Is a string? |
Key Value |
|
Start Time |
WS |
False |
0ns |
|
Stop Time |
WE |
False |
10ns |
|
Minimum Time |
WM |
False |
0ns |
|
Maximum Time |
WN |
False |
10ns |
|
Is Thinning Enabled? |
DE |
False |
0 |
|
Dy/dx Tolerance |
DT |
False |
0.001 |
|
Number of points |
DP |
False |
20000000 |
b.Transient report context for Spectral domain in Transient analysis:
|
Description |
Key Name |
Is a string? |
Key Value |
|
Start Time |
TS |
False |
0ns |
|
Stop Time |
TE |
False |
10ns |
|
Max Harmonics |
MH |
False |
100 |
| Max Frequency | MF | False | * |
|
Window type |
WT |
False |
0 |
|
Width Percentage |
WW |
False |
100 |
|
Kaiser Parameter |
KP |
False |
0 |
|
Adjust Coherent Gain |
CG |
False |
0 |
* Script can specify either MH or MF. If neither is specified, Max Harmonics is set to 100. If both are specified, MF is used.
|
Window Type |
ID |
|
Rectangular |
0 |
|
Bartlett |
1 |
|
Blackman |
2 |
|
Hamming |
3 |
|
Hanning |
4 |
|
Kaiser |
5 |
|
Welch |
6 |
|
Weber |
7 |
|
Lanzcos |
8 |
c. Eyeprobe index context for UI domain, Time domain, Eye Measuremant domain in VerifEye and QuickEye analysis:
|
Description |
Key Name |
Is a string? |
Key Value |
|
Eyeprobe compinst ID |
PCID |
False |
0 |
d. Eyesource index context for Initial Response domain and Peak Distortion domain in VerifEye and QuickEye analysis:
|
Description |
Key Name |
Is a string? |
Key Value |
|
Eyesource compinst ID |
SCID |
False |
0 |
e. UI domain context in VerifEye and QuickEye analysis:
|
Description |
Key Name |
Is a string? |
Key Value |
|
Use midpoint? |
MIDPOINT |
False |
0 - Don't use midpoint. 1 - Use midpoint of amplitude. 2 - Use midpoint of UI. |
|
Minimum latch overdrive |
MLO |
False |
0 |
f. Distribution Context for UI Domain in VerifEye and QuickEye analysis:
|
Description |
Key Name |
Is a string? |
Key Value |
|
Use distribution? |
USE_DIST |
False |
0 - No 1 - Yes |
|
Distribution type |
DIST |
False |
0 - Receiver Jitter 1 - Receiver Noise 2 - User Defined |
Receiver Jitter Parameters
|
Description |
Key Name |
Is a string? |
Key Value |
|
DLL standard deviation |
DSD |
False |
0 |
|
Distribution type |
DIST |
False |
0 |
|
DLL taps |
DMN |
False |
0 |
|
Static Offset |
SOFF |
False |
0 |
|
Number of Gaussian data sets |
NUMG |
False |
0 |
|
Gaussian std deviation |
GS0,GS1... |
False |
0 |
|
Offset mean |
GM1,GM1... |
False |
0 |
|
Number of Uniform data sets |
NUMU |
False |
0 |
|
Uniform width |
UW0,UW1... |
False |
0 |
|
Uniform mean |
UM1,UM1... |
False |
0 |
Receiver Noise Parameters
|
Description |
Key Name |
Is a string? |
Key Value |
|
Number of Gaussian data sets |
NUMG |
False |
0 |
|
Gaussian std deviation |
GS0,GS1... |
False |
0 |
|
Number of Uniform data sets |
NUMU |
False |
0 |
|
Uniform width |
UW0,UW1... |
False |
0 |
User Defined Parameters
|
Description |
Key Name |
Is a string? |
Key Value |
|
Number of XY data pairs |
NUMG |
False |
0 |
|
X data |
X0,X1,X2... |
False |
0 |
|
Y data |
Y0,Y1,Y2... |
False |
0 |
|
Cutoff probability |
CP |
False |
0 |