Stats

  • Locked Locked
  • Replies 6
  • Subscribers 165
  • Views 14298
  • Members are here 0
More Content
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

How to create a report for PACKAGE_HEIGHT_MAX

Lock2002

I'm trying to create a custom report that will generate max component heights, ref designators and whether they are mirrored or not. It will report the designators and mirror status, but not the package height. 

  • Does the report shown below solve your issue?

    D:\SPB_Data\intel\ionize>cat test.txt
    COMPONENT
    REFDES_SORT
    REFDES
    COMP_HEIGHT
    SYM_MIRROR

    D:\SPB_Data\intel\ionize>grep test allegro.jrl | tail -1
    \i (00:07:39) reports "./test.txt" nographic write test.dat

    D:\SPB_Data\intel\ionize>head test.dat
    Allegro Report
    D:/SPB_Data/intel/ionize/Ionize_HP_Mezz_ElliottKey_0809.brd
    Tue Sep 03 08:38:09 2019

    REFDES,COMP_HEIGHT,SYM_MIRROR
    C1,.024 IN,YES
    C6,.024 IN,YES
    C7,.034 IN,YES
    C10,.057 IN,YES
    C11,.057 IN,YES

    D:\SPB_Data\intel\ionize>

  • in reply to DavidJHutchins

    unfortunately, no. Our package heights are defined by a property attached to the place boundary (PACKAGE_HEIGHT_MAX). 

  • Then try this one...

    D:\SPB_Data\intel\ionize>type test2.txt
    GEOMETRY
    CLASS = PACKAGE GEOMETRY
    SUBCLASS = 'PLACE_BOUND_TOP'
    SYM_TYPE = PACKAGE
    OR
    CLASS = PACKAGE GEOMETRY
    SUBCLASS = 'PLACE_BOUND_BOTTOM'
    SYM_TYPE = PACKAGE
    REFDES
    SYM_MIRROR
    PACKAGE_HEIGHT_MAX
    END

    D:\SPB_Data\intel\ionize>grep test2 allegro.jrl
    \i (00:00:21) reports "./test2.txt" nographic write test2.dat

    D:\SPB_Data\intel\ionize>head test2.dat
    Allegro Report
    D:/SPB_Data/intel/ionize/Ionize_HP_Mezz_ElliottKey_0809.brd
    Tue Sep 03 09:42:56 2019

    REFDES,SYM_MIRROR,PACKAGE_HEIGHT_MAX
    EU2100,NO,58 MIL
    EU2100,NO,58 MIL
    EU2100,NO,58 MIL
    EU2100,NO,58 MIL
    F1,NO,18 MIL

    D:\SPB_Data\intel\ionize>

  • in reply to DavidJHutchins

    Almost there. Can you do this without duplicates? I'm getting between 4 and 8 duplicates per designator. Thanks for your help!

  • I can't see any options in the extracta command file format to remove the duplicate entries ( I'm guessing it's reporting for every vertex in the place_bound shapes )

    I think the simplest solution would be to use the unix/linux 'uniq' command to remove the duplicate entries: 

    D:\SPB_Data\intel\ionize>wc test2.dat
    2245 4486 37453 test2.dat

    D:\SPB_Data\intel\ionize>uniq test2.dat > test2a.dat

    D:\SPB_Data\intel\ionize>wc test2a.dat
    619 1235 10368 test2a.dat

    D:\SPB_Data\intel\ionize>head test2a.dat
    Allegro Report
    D:/SPB_Data/intel/ionize/Ionize_HP_Mezz_ElliottKey_0809.brd
    Tue Sep 03 09:42:56 2019

    REFDES,SYM_MIRROR,PACKAGE_HEIGHT_MAX
    EU2100,NO,58 MIL
    F1,NO,18 MIL
    F2,NO,18 MIL
    FB20,NO,55 MIL
    FB11,NO,55 MIL

    D:\SPB_Data\intel\ionize>

Cadence Guidelines

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.