Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 9835
  • 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

dbCreatePath unexpected additional line

patschouly

Hi, I'm creating paths with dbCreatePath. The following command works as expected:

dbCreatePath(cv list("M1" "drawing") list(0:1 0:0 1:0 1:1) 0.1 )

whereas the following slight modification (notice the last point in the point list) does not. The path is created, but there is an extra line connecting two points. What am I missing here? Here is an image showing the problem alongside the command:

dbCreatePath(cv list("M2" "drawing") list(0:1 0:0 1:0 1:2) 0.1 )

  • I don't see that. Is that maybe a flight line in Virtuoso Layout Suite XL? Can you see if there's anything in the annotation browser?

    I can't see anything wrong with your point list in the second case.

    Andrew

  • in reply to Andrew Beckett

    No, the annotation browser is completely blank. This is also a layout-only cell, there is no connectivity reference.

    There is another thing that got obscured by the axis in my last picture:

    Notice the horizontal segment has no middle line.


    I'm using ICADVM20.1-64b, if that is of any help.

    Patrick

  • in reply to patschouly

    Hi Patrick,

    Can you let me know the precise sub-version you're using? getVersion(t) will report this. It probably won't matter, but what does geGetEditCellView()~>DBUPerUU return?

    Looks like a strange rendering problem, so I want to check in the same version you're using.

    Andrew

  • in reply to Andrew Beckett

    Hi Andrew,

    getVersion(t) says "sub-version  ICADVM20.1-64b.14", DBUperUU is 1000.0.

    Thank you for your help!

  • in reply to patschouly

    Patrick,

    I've reproduced the problem - as it turns out, it happens not only in the specific sub-version you're using, but also in the latest (ISR26, with .26 at the end). The cause is having "Merge Shapes" turned on in the Display Options form:

    If you turn that off (it's not the default), or set the scope to PCells (for example) then it works fine. It's a rendering problem by the Merge Shapes algorithm.

    I've filed a Change Request (CCR 2680783) to get this fixed. I also found a separate problem with exporting an image of the path (via File->Export Image) when Merge Shapes is turned on, and that's CCR 2680790 (the image was blank).

    You might want to contact customer support so that a duplicate can be filed to a) track the fix and b) increase the priority since it's coming from a customer rather than something I happened to report.

    Andrew 

  • in reply to Andrew Beckett

    Thanks Andrew, I can confirm this fixes my problem. Thank you for looking into this.

    Kind regards,

    Patrick

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.