Stats

  • Locked Locked
  • Replies 7
  • Subscribers 127
  • Views 15769
  • 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

Symbol view information in text format

AnnaS

Hi All,

Can you please help me find out:

Is it possible to get symbol view information in text format (like a coordinates list).

PS: To be more clear I would like to bring this example:

Using Design->Plot we can get *.ps file. Then convert it to pdf format and see symbol's graphical view.

Thanks in advance.

Best Regards,

Anna 

 

  • Why do you need this? (it might help provide a more focussed answer).

    Otherwise you can write out EDIF (File->Export->EDIF) or you could use the dbWriteSkill() function. Alternatively it would be straightforward enough to traverse the database using SKILL and write out the graphical information in whatever form you want.

    Regards,

    Andrew.

  • Hi Andrew,

    Thank you for quick response.

    What we need is to get all shapes and pins in symbol view and print their types+coordinates into a text file.

    It's like:

    line(x1,y1,x2,y2)

    circle(x,y,R)

    pin(....)

    Looking forward.

    Thanks and Regards,

    Anna

     

  • Hi Anna

    I am also not too clear on the purpose of this but if shape info is what you want, hope that the following can help you. Load the file, open a symbol and press F10. Look for the file "symbolinfo.txt". : )

    Best regards
    Quek

    procedure( CCSsymbolInfo()
       let( (cv outPort sType sBbox pinName)
          cv=geGetWindowCellView()
          outPort=outfile("symbolinfo.txt")
          fprintf(outPort "Type\tbBox\tPin Name\n")
          fprintf(outPort "====\t====\t========\n")
          foreach(shape cv~>shapes
             sType=shape~>objType
             sBbox=shape~>bBox
             pinName=""
             if( shape~>pin~>name then
                pinName=shape~>pin~>name
             ) ;if
             fprintf(outPort "%s\t%L\t%s\n" sType sBbox pinName)
          ) ;foreach

          close(outPort)
          outPort=nil
          printf("Symbol info has been sent to file symbolinfo.txt")
       ) ;let
    ) ;procedure

    hiSetBindKey("Symbol" "F10" "CCSsymbolInfo()")



    === Sample output ===
    Type    bBox    Pin Name
    ====    ====    ========
    rect    ((-0.025 -0.025) (0.025 0.025)) IN
    line    ((0.0 0.0) (0.25 0.0))
    label   ((0.2875 -0.03125) (0.38125 0.03125))
    rect    ((1.85 -0.025) (1.9 0.025))     OUT
    line    ((1.625 0.0) (1.875 0.0))
    symbolinfo.il

  • Hi Quek,

    Thanks a lot for the code.

    Best Regards,

    Anna

  • Hi Quek,

    Could you please help me to change the code in this way:

    I am trying to get+print all attributes of all shapes and pin instead of bBox coordinates.

    Thanks in advance.

    Best Regards,

    Anna

     

  • Have you tried Andrew's suggestions earlier? The dbWriteSkill command will dump all of the info you need, but you would probably need to parse the data using Perl or Python to get it in the format you want. It might be a good start for you to see what kind of data is in your cell.

    dbWriteSkill(geGetEditCellView() "/tmp/dumpFile.il" "w" "4.4")

    You could certainly write all of the attributes out to a file in whatever format you want using Skill code. However, none of us have the time to exhaustively list all of the attributes for all of the object types that you might be interested in.

    For any object, you can see all of its attributes by doing this:

    objId = car(selectedSet()) ; Select the item in your schematic first

    objId~>?    ;This will show you the attribute names

    objId~>??  ;This will show you the attributes names and values

    Now follow Quek's example and write out exactly those attributes you care about in the format you need.

    I hope that helps.

    Derek

  • Hi Derek,

    Thank you for your suggestion. I'll try.

    Best Regards,

    Anna

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.