Stats

Locked Locked
Replies 2
Subscribers 143
Views 1817
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

Virtuoso deleting points when setting new path points (Bug)

Betoo 7 months ago

Hi everyone,

In one of my scripts I have a path, path = car(geGetSelSet())

width = 0.6um

points = ((-20000.0 132.5) (-21082.29 132.5) (-23107.27 136.35) (-23272.27 132.5) (-23279.18 132.5))

Now I calculate new points and set those new points using path~>points = newpts. The last point calculated happens to be the same as the second to last

newpts = '((-20001.87 132.5) (-21082.29 132.5) (-23107.27 136.35) (-23272.27 132.5) (-23272.27 132.5))

path~>points = newpts

Now when I query the points of this path with path~>points, it returns:

((-21082.29 132.5)
(-23107.27 136.35)
(-23272.27 132.5)
)

It looks like virtuoso is incorrectly deleting the first point along with one of the duplicate points. My version number is: IC6.1.8-64b.500.26 . Is there any way around this besides deleting the original path and then creating a new path using dbCreatePath? This is the workaround I am currently doing when these points are not set correctly.

Thanks,

Beto

Parents

Andrew Beckett 7 months ago

Beto,

You're right - this does seem strange. I filed Change Request #3105980 to see what's going on. As a workaround, you can use this:

path~>points=dbCompressPointArray(newpts nil cv~>DBUPerUU)

Andrew
Cancel
Vote Up +1 Vote Down

Cancel
Betoo 7 months ago in reply to Andrew Beckett

Hi Andrew,

Thanks for this! This is working perfectly and is much more elegant than the way I was doing it.

Cheers,

Beto
Cancel
Vote Up 0 Vote Down

Cancel

Reply

Betoo 7 months ago in reply to Andrew Beckett

Hi Andrew,

Thanks for this! This is working perfectly and is much more elegant than the way I was doing it.

Cheers,

Beto
Cancel
Vote Up 0 Vote Down

Cancel

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.