• 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 SKILL
  3. Checking against text from a file

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 13112
  • 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

Checking against text from a file

climbnc
climbnc over 8 years ago

Hi All,

I have a file i want to read.  This file consists of lines like

RUN DRC YES

RUN LVS YES

POWER NAMES VCC VCCA

i have some outputs of Buttons and stringFields from a GUI that i set to a string like

setPowerNames = sprintf(str "POWER NAMES %s" powerStringField~>value)

if(drcBooleanButton = t

then

setDrcSwitch = "RUN DRC YES"

else

setDRCSwitch = "RUN DRC NO"

)

I want to then compare all the lines from the file against setPowerNames,setDrcSwitch, etc.  Then i would ouput the lines that are different from the file to an output file(compare.results.text)

What would be the most efficient way to do this?

Thank you in advance for your help. 

  • Cancel
  • climbnc
    climbnc over 8 years ago
    i want to clarify that i would be checking setPowerNames to then line
    POWER NAMES VCC VCCA

    compare setDrcSwtich to the line
    RUN DRC YES

    and so on.

    So that if setDrcswitch = "RUN DRC NO" and then line from the file is RUN DRC YES
    then it would output RUN DRC YES to the compare.results.text
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    It probably depends on how many of these switches you have, but I'd think you'd want to do something like this:

    linePrefixes=list("POWER NAMES" "RUN DRC" "RUN LVS")
    patterns=makeTable('patterns nil)
    foreach(linePrefix linePrefixes
      patterns[linePrefix]=pcreCompile(strcat("^\\s*" linePrefix "\\s*"))
    )

    trailingSpaces=pcreCompile("\\s*$")

    settingsFromFile=makeTable('settingsFromFile nil)
    inp=infile("settings.txt")
    while(gets(line inp)
      line=pcreReplace(trailingSpaces line "" 1)
      forall(linePrefix patterns
        if(pcreExecute(patterns[linePrefix] line) then
          settingsFromFile[linePrefix]=pcreReplace(patterns[linePrefix] line "" 1)
          nil
        else
          t
        )
      )
    )
    close(inp)

    This will give  you a hash table with settingsFromFile["RUN DRC"] and settingsFromFile["POWER NAMES"] etc.

    Then, in your code above, rather than setting individual variables such as setDrcSwitch, I'd suggest you do:

    settingsFromForm=makeTable('settingsFromForm nil)

    and then in the code:

    if(drcBooleanButton = t then
      settingsFromForm["RUN DRC"]="YES"
    else
      settingsFromForm["RUN DRC']="NO"
    )

    (actually I'd probably write it this way):

    settingsFromForm["RUN DRC"]=if(drcBooleanButton then "YES" else "NO")

    Having done that you could then look for the differences (and write to file, or whatever you want):

    foreach(setting settingsFromForm
      when(settingsFromForm[setting]!=settingsFromFile[setting]
        printf("Setting %s doesn't match\n" setting)
      )
    )

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • climbnc
    climbnc over 8 years ago
    Thank you very much Andrew. This helps a lot.
    • 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