• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Issue with importing csv file to the ADEXL outputs

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 125
  • Views 12605
  • 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

Issue with importing csv file to the ADEXL outputs

greywanderer
greywanderer over 3 years ago

Hi,

I have transistors in the schematic named Mxx<5:0> and want to observe the "gm" of Mxx<5>. After accessing this in the results browser and storing in the outputs and then exporting it as a csv file, the transistor appears as "Mxx\\<5\\>". But when I make similar modifications to the rest of the occurrences in the csv file and import it to the output of the adexl, I get the following error,

"

value(pv("Mxx\<
                        ^^
PARSER WARNING at line 1 column 28 of file *string*
*WARNING* (Parser): character found after backslash is not meaningful - '\<'

"

What am I doing wrong? Any suggestions on managing such name formats in the csv files for the ADEXL outputs?

Thanks!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 3 years ago in reply to greywanderer

    The challenge appears to be if the expression is in quotes (and you have the "escaped" quotes embedded within). If it's like this:

    library:cell:test,Ids0p5u_Mnb5,expr,value(pv("ux1.ux2.Mnb\\<5\\>" "ids" ?result "tranOpTimed") 5e-07),t,,

    then it works with no problems.

    If you have the surrounding quotes in place, there's an extra layer of parsing, so that means you need to double-up the backslashes to (yes) four!

    library:cell:test,Ids0p5u_Mnb5,expr,"value(pv(""ux1.ux2.Mnb\\\\<5\\\\>"" ""ids"" ?result ""tranOpTimed"") 5e-07)",t,,

    The joys of escape characters!

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • greywanderer
    greywanderer over 3 years ago in reply to Andrew Beckett

    I see. The double quotes were placed there when I exported to a csv file and I assumed they needed to be so.

    Thanks much!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
<

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information