How to increase X axis and Y axis limit in layout

Hi Lakshmisha,

Why would you want to increase the limit of the coordinates? If you have a technology database with a "DBUperUU" (database unit per user unit) of 1000 (fairly standard for small geometry designs), that gives a database resolution of 1nm, and a maximum coordinate of +/-2.147 metres. Is that not big enough?

That environment variable is specifically to do with the copy command - even then, the database cannot possibly place an instance beyond 2**31 (plus and minus) times the database resolution because the coordinates are stored as a pair of 32 bit integers in the database.

I don't understand why you'd need to place a instance at such a large coordinate. The only thing I can think of is if you are creating something such as large panel displays, in which case it makes no sense to have 1nm resolution in the database (so you should be having a smaller DBUperUU; if DBUperUU was 10, then that would allow up to 200 metres or so as the maximum coordinate in each direction). I know of no manufacturing process that has a range of dimensions with a scale of 1 billion between the smallest dimension and the largest dimension.

Regards,

Andrew.

HI Andrew ,

      Thanks for the quick reply . I was trying to create an abutment for standard cell layouts . So while instantiating cells it was going beyond 2.147 meters. I have updated my script to limit the placement within 2.147 meters.

Regards

Lakshmisha KC

We have seen the same message. However we are only trying to open to view a layout. The whole virtuoso session hangs and the log file shows the following,

\# Memory report: using       5,758 MB, process size 6,761 MB at UTC 2019.06.18 20:13:06.424
\# Memory report: using       5,858 MB, process size 6,861 MB at UTC 2019.06.18 20:13:37.241
\# Memory report: using       5,959 MB, process size 6,962 MB at UTC 2019.06.18 20:14:03.356
\# Memory report: using       6,071 MB, process size 7,074 MB at UTC 2019.06.18 20:14:30.331
\# Memory report: using       6,184 MB, process size 7,187 MB at UTC 2019.06.18 20:14:57.366

And it keeps increasing.

Other layout in the same library opens fine.

I'm not sure the message is related to the memory growth. Without seeing the data (e.g. via customer support) it's rather hard to tell. I suggest you do that (contact customer support)

In the meantime, you could check your data using:

oaScan -lib libName -cell cellName -view viewName

It turns out, one of the cell 6 levels down in hierarchy is somehow corrupted. oaScan says ArrayInst has inverted bBox. I used osScan to repair the cellview and the problem went away.

Thanks, Andrew.