Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 15113
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

trouble enabling MPT coloring in IC18

Stevemc12

I'm having trouble getting the MPT Coloring to work. I'm sure I'm just missing something simple. 

I have run (mptActivate t) but in the Properties window for my rectangle the MPT section remains grayed out. I am using the same techlib, which includes colorMap, and same oalibs as other colleagues who can use the properties but were unfortunately unable to tell me how to fix mine. Are there other settings I need to enable?

Parents
  • rudyc

    You may want to crosscheck the MPT settings by running the following command:

    mptReportCurrentSettings(geGetEditCellView())

    Then check that the v1 drawing is part of the Colorable LPP section

  • Stevemc12
    in reply to rudyc

    I'm not sure, but apparently not. Does this indicate that the Colorable section is empty?

    mptReportCurrentSettings(geGetEditCellView())
    ------------------------------------------------------
    MPT flow report for scratch/g1mnand02ab3d36x5/oa
    @(#)$CDS: virtuoso version ICADVM18.1-64b 05/28/2019 19:28 (cpgbld01) $
    Dec 18 10:32:45 2019
    ------------------------------------------------------

    Technology file:
    Colorable layer(s):

    MPT constraintGroup: default
    Available MPT constraintGroup(s) in the tech file:
    virtuosoDefaultMPTSetup

    Colorable LPPs:

    Default Colors:
    none

    Coloring Methods:
    Session coloring method : colorSpacing
    Design coloring method : colorSpacing

    Main MPT cdsenv:
    Dynamic Coloring/Coloring Engine: t (mpt.coloringEngineEnabled)
    Default shape assignment: "asIs" (mpt.unclusteredShapeColor)
    ReColor read-only cellViews: nil (mpt.reColorReadOnlyCellView)
    Copy color(makeCell & flatten): nil (cdba.copyMPAttributes)
    Lock propagation: nil (mpt.propagateLocksToConnectedShapes)
    HCL creation during LockAll: "noHCL" (mpt.lockAllHCLPolicy)

    Policy for CELL:
    Instance Color Shifting: "none" (mpt.globalColorShiftingPolicy)
    Hierarchical Color Locking: "all" (mpt.enableHCLCreation)

    Policy for PCELL:
    Coloring: t (Opposite of mpt.dontColorPCells)
    Recoloring On Evaluation: nil (mpt.forcePcellRecolorOnEval)
    Instance Color Shifting: "cluster" (mpt.globalColorShiftingPolicyForPcells)
    Hierarchical Color Locking: "all" (mpt.enableHCLCreationOnPcells)

    Cdsenv with current value different than default:
    mpt coloringEngineEnabled boolean t (default: nil)
    mpt defaultColoringMethod cyclic "colorSpacing" (default: "connectedShapes")


    INFO: Report saved to 'mptFlow.rpt'
    t

Reply
  • Stevemc12
    in reply to rudyc

    I'm not sure, but apparently not. Does this indicate that the Colorable section is empty?

    mptReportCurrentSettings(geGetEditCellView())
    ------------------------------------------------------
    MPT flow report for scratch/g1mnand02ab3d36x5/oa
    @(#)$CDS: virtuoso version ICADVM18.1-64b 05/28/2019 19:28 (cpgbld01) $
    Dec 18 10:32:45 2019
    ------------------------------------------------------

    Technology file:
    Colorable layer(s):

    MPT constraintGroup: default
    Available MPT constraintGroup(s) in the tech file:
    virtuosoDefaultMPTSetup

    Colorable LPPs:

    Default Colors:
    none

    Coloring Methods:
    Session coloring method : colorSpacing
    Design coloring method : colorSpacing

    Main MPT cdsenv:
    Dynamic Coloring/Coloring Engine: t (mpt.coloringEngineEnabled)
    Default shape assignment: "asIs" (mpt.unclusteredShapeColor)
    ReColor read-only cellViews: nil (mpt.reColorReadOnlyCellView)
    Copy color(makeCell & flatten): nil (cdba.copyMPAttributes)
    Lock propagation: nil (mpt.propagateLocksToConnectedShapes)
    HCL creation during LockAll: "noHCL" (mpt.lockAllHCLPolicy)

    Policy for CELL:
    Instance Color Shifting: "none" (mpt.globalColorShiftingPolicy)
    Hierarchical Color Locking: "all" (mpt.enableHCLCreation)

    Policy for PCELL:
    Coloring: t (Opposite of mpt.dontColorPCells)
    Recoloring On Evaluation: nil (mpt.forcePcellRecolorOnEval)
    Instance Color Shifting: "cluster" (mpt.globalColorShiftingPolicyForPcells)
    Hierarchical Color Locking: "all" (mpt.enableHCLCreationOnPcells)

    Cdsenv with current value different than default:
    mpt coloringEngineEnabled boolean t (default: nil)
    mpt defaultColoringMethod cyclic "colorSpacing" (default: "connectedShapes")


    INFO: Report saved to 'mptFlow.rpt'
    t

Children
  • rudyc
    in reply to Stevemc12

    It looks like there's no colorable layer defined in the techFile which would explain why the color field is grayed out in the property editor.

    You can run the same command on the environment of your colleagues to see if the section is empty.

    Then you can compare the tech graphs (Tools -> Technology File Manager -> Graph) to detect a potential problem in the ITDB.

    The colorable layers are defined by the #Masks field in the techLayers section of the techFile.

    You can dump also the techFile(s) using Tools -> Technology File Manager -> Dump to confirm the mask number is set to 2 or above.

    techLayers(
    ;( LayerName     Layer# Abbreviation [#Masks] )
    ;( --------- ------ ------------ -------- )
    ;User-Defined Layers:
    ( NWell                5         NW )

    .....
    ( v1                      10       V1                 2       )

  • Stevemc12
    in reply to rudyc

    My techfile has this for the techLayers

    ( v1 13 v1 3 )

    ( m2 14 m2 2 )

    The via1 layer does have 3 colors in our technology, and metal2 2 colors. Is there anything that needs to be done during the compilation of the text file into the TechLib?

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.