Stats

  • Locked Locked
  • Replies 8
  • Subscribers 144
  • Views 15490
  • 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

Searching for the best way to rasterize layout data, i.e. generate a bitmap

caver456

We would like to generate a single-bit ('black-and-white') raster / bitmap from a certain cell in Virtuoso Layout for each of a set of layers.

The cell size / grid size / pixel size for us would be 2.625 x 2.625 microns, but that may change.  We would generate the raster over some area of our top level layout, so, we're looking at potentially low thousands of pixels in each dimension.

Criteria would probably be simple; maybe as simple as "if that cell contains any (>0%) of the layer in question, the pixel value will be 1, otherwise it will be 0".

We would like to create a separate raster for metal1, a raster for via1, a raster for metal2, a raster for via2, and a raster for metal3... the point being, we have a small fixed set of layers and we'd like one raster per layer.

SKILL might not be the best fit... maybe Diva or Dracula or Assura or Calibre, or an external program looking directly at the GDS data?  An idea or solution in SKILL or any one of those other tools would be very helpful.  This forum seemed like the best venue for the question

Parents
  • We do use the abe functions for some other tasks not related to this one. They work great on small data; it's interesting to hear of the stumbling points on larger data. The bigger limitation of the abe functions that we've run across is the fact that they operate on fractured tiles, which can lead to unexpected results for certain drawn shapes. The results make sense when you re-read the description of the tiling. Sounds like an AND in each area would likely be immune to unexpected tile-related behavior?
    Anyway, the goal is basically to feed a layout representation into an external spreadsheet program that does a whole truckload of number crunching. Maybe there's a different way to accomplish that entire end goal? Probably writing something in C to chug directly on the gds or oa data would be 'optimal' but for the scope of this question I'm treating the spreadsheet task as a black box that needs its csv 'bitmap' per layer. However if you've got any ideas for how to work the entire task more intelligently that would be great.
Reply
  • We do use the abe functions for some other tasks not related to this one. They work great on small data; it's interesting to hear of the stumbling points on larger data. The bigger limitation of the abe functions that we've run across is the fact that they operate on fractured tiles, which can lead to unexpected results for certain drawn shapes. The results make sense when you re-read the description of the tiling. Sounds like an AND in each area would likely be immune to unexpected tile-related behavior?
    Anyway, the goal is basically to feed a layout representation into an external spreadsheet program that does a whole truckload of number crunching. Maybe there's a different way to accomplish that entire end goal? Probably writing something in C to chug directly on the gds or oa data would be 'optimal' but for the scope of this question I'm treating the spreadsheet task as a black box that needs its csv 'bitmap' per layer. However if you've got any ideas for how to work the entire task more intelligently that would be great.
Children
No Data

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.