• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Gmindc different than the value set in the Options/anal...

Stats

  • Replies 4
  • Subscribers 132
  • Views 671
  • Members are here 0

Gmindc different than the value set in the Options/analog

JG20240913167
JG20240913167 2 months ago

Dear community,

When doing DC sweeps or stability analysis I have the issue that, the Gmindc used by the tool is 100 uS or even 1 mS. However, in the simulations options gmin and gmindc have been set to 1e-12.
Any idea what can I do to avoid the tool from using any other value than the specified?

I am using Cadence IC23.10.160, Spectre23.10.802.

The log looks like this

Global user options:
psfversion = 1.4.0
vabstol = 1e-06
iabstol = 1e-12
temp = -40
try_fast_op = no
gmin = 1e-12
gmin_check = all
gmindc = 1e-12
rforce = 1
maxnotes = 5
maxwarns = 5
digits = 5
cols = 80
dc_pivot_check = yes
pivrel = 0.001
sensfile = ../psf/sens.output
checklimitdest = sqldb
save = selected
currents = selected
reltol = 0.0001
tnom = 27
scalem = 1
scale = 1

Scoped user options:

Circuit inventory:
nodes 5481
bsim4 916
bsource_2ab5b1 258
bsource_09f256 2800
bsource_79a729 416
bsource_7533b7 426
bsource_bd39ed 1400
bsource_c39284 1613
bsource_rpldd_50k_noi_225128 60
bsource_rpposab_8ef6d6 48
capacitor 460
dac_8bit_ideal 1
diode 1933
iprobe 6
isource 1
resistor 1613
vccs 1
vdc8bit 1
vsource 15

Analysis and control statement inventory:
info 6
stb 1

Output statements:
.probe 0
.measure 0
save 0

Design checks inventory:
paramtest 1
assert 176


Notice from spectre during initial setup.
Protected devices exist and are not included in the circuit inventory.
365 warnings suppressed.

Time for parsing: CPU = 204.564 ms, elapsed = 510.794 ms.
Time accumulated: CPU = 718.18 ms, elapsed = 1.57563 s.
Peak resident memory used = 181 Mbytes.

~~~~~~~~~~~~~~~~~~~~~~
Pre-Simulation Summary
~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~

**************************************************
Stability Analysis `stb': freq = (1 Hz -> 100 MHz)
**************************************************
Matrix is singular (detected at `I_DUT.I_MIRR_2_2.I_OPAs.D16.d0:int_c').

Warning from spectre during DC analysis, during STB analysis `stb'.
WARNING (SPECTRE-16085): Circuit has no unique solution.
A resistance of 10 kOhm (1/GminDC) was added across each nonlinear device.
Notice from spectre during DC analysis, during STB analysis `stb'.
GminDC = 100 uS is large enough to noticeably affect the DC solution.

  • Cancel
  • Sign in to reply
Parents
  • Andrew Beckett
    Andrew Beckett 2 months ago

    This is explained by Spectre can now adjust gmin value over a range automatically to resolve convergence issues . If you set gmindcmax you can limit the upper limit that gmindc will be adjust to in the case of "no unique solution".

    You can also just make the "Circuit has no unique solution" an error, following How to change spectre warning messages into error messages when Spectre determines that the circuit has no unique solution

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • JG20240913167
    JG20240913167 2 months ago in reply to Andrew Beckett

    Dear Andrew,

    Thanks a lot for your explanation and help. Unfortunately, the issue is still present. I set gmin=1e-14, gmindc=1e-14 and gmindcmax=1e-12.
    However, the simulator still uses Gmindc=100 uS. Any other idea?

    *****************************************************************

    Global user options:
    psfversion = 1.4.0
    vabstol = 1e-06
    iabstol = 1e-12
    temp = -40
    try_fast_op = no
    gmin = 1e-14
    gmin_check = all
    gmindc = 1e-14
    rforce = 1
    maxnotes = 5
    maxwarns = 5
    digits = 5
    cols = 80
    dc_pivot_check = yes
    pivrel = 0.001
    sensfile = ../psf/sens.output
    checklimitdest = sqldb
    gmindcmax = 1e-12
    save = selected
    currents = selected
    reltol = 0.0001
    tnom = 27
    scalem = 1
    scale = 1

    Scoped user options:

    Circuit inventory:
    nodes 5481
    bsim4 916
    bsource_2ab5b1 258
    bsource_09f256 2800
    bsource_79a729 416
    bsource_7533b7 426
    bsource_bd39ed 1400
    bsource_c39284 1613
    bsource_rpldd_50k_noi_225128 60
    bsource_rpposab_8ef6d6 48
    capacitor 460
    dac_8bit_ideal 1
    diode 1933
    iprobe 6
    isource 1
    resistor 1613
    vccs 1
    vdc8bit 1
    vsource 15

    Analysis and control statement inventory:
    info 6
    stb 1

    Output statements:
    .probe 0
    .measure 0
    save 0

    Design checks inventory:
    paramtest 1
    assert 176


    Notice from spectre during initial setup.
    Protected devices exist and are not included in the circuit inventory.
    365 warnings suppressed.

    Time for parsing: CPU = 205.993 ms, elapsed = 491.271 ms.
    Time accumulated: CPU = 709.027 ms, elapsed = 1.08937 s.
    Peak resident memory used = 181 Mbytes.

    ~~~~~~~~~~~~~~~~~~~~~~
    Pre-Simulation Summary
    ~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~

    **************************************************
    Stability Analysis `stb': freq = (1 Hz -> 100 MHz)
    **************************************************
    Matrix is singular (detected at `I_DUT.I_MIRR_2_2.I_OPAs.D4.d0:int_c').

    Warning from spectre during DC analysis, during STB analysis `stb'.
    WARNING (SPECTRE-16085): Circuit has no unique solution.
    A resistance of 10 kOhm (1/GminDC) was added across each nonlinear device.
    Notice from spectre during DC analysis, during STB analysis `stb'.
    GminDC = 100 uS is large enough to noticeably affect the DC solution.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 2 months ago in reply to JG20240913167

    First I would suggest checking with the latest SPECTRE25.1 ISR and if the issue persists, then please contact customer support (after logging in, use the case menu to submit a support case). We'll probably need your example netlist that shows the problem.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett 2 months ago in reply to JG20240913167

    First I would suggest checking with the latest SPECTRE25.1 ISR and if the issue persists, then please contact customer support (after logging in, use the case menu to submit a support case). We'll probably need your example netlist that shows the problem.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • JG20240913167
    JG20240913167 2 months ago in reply to Andrew Beckett

    Understood. Thanks for your support

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2026 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information