• 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. skill - write a file with skill variables

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 125
  • Views 6072
  • 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

skill - write a file with skill variables

ejm20
ejm20 over 14 years ago

 

In skill, how do you create a file and overwrite if its present with the contents that are skill variables?  Heres a snipet of the the code to get produce the variables:

      tool_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>uniMode~>value
         println( tool_opt )

      rcReduction_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>psrSwitch~>value
         println( rcReduction_opt )

      println( mt_opt )    

 The evaluated variables will then be written into a file named "myFile"  .   As an example:

tool_opt   =  spectre

rcReduction = nil

mt_opt  =  Disable

 so......

 

spectre nil Disable

 

Thanks 
  • Cancel
Parents
  • skillUser
    skillUser over 14 years ago

    Hi,

    One thing that I would add is that this is fine if you are sure that the variables are all strings, but if not then it may be better to use "%L" for each of the format specifiers - if the variable was not a string then the %s format would cause fprintf (or sprintf or printf) to choke and fail, but %L can be used for any value, 'nil', a list, an integer, a floating point number etc.  You can use the "type" function to obtain the type of a variable, or individual predicate functions like "stringp", "listp" etc. to programmatically test and avoid such an issue also.  E.g.

    if(forall(var list(tool_opt multiThread paraReduction) stringp(var)) then
      ;; print variables out nicely if they are all strings
      fprintf(myPort "%s %s %s\n" tool_opt  multiThread  paraReduction )
    else
      ;; print values out using default %L format if they are not all strings
      fprintf(myPort "%L %L %L\n" tool_opt  multiThread  paraReduction )
    )
    

    You could even build the format string based on the variable data type (that seems overkill here).

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 14 years ago

    Hi,

    One thing that I would add is that this is fine if you are sure that the variables are all strings, but if not then it may be better to use "%L" for each of the format specifiers - if the variable was not a string then the %s format would cause fprintf (or sprintf or printf) to choke and fail, but %L can be used for any value, 'nil', a list, an integer, a floating point number etc.  You can use the "type" function to obtain the type of a variable, or individual predicate functions like "stringp", "listp" etc. to programmatically test and avoid such an issue also.  E.g.

    if(forall(var list(tool_opt multiThread paraReduction) stringp(var)) then
      ;; print variables out nicely if they are all strings
      fprintf(myPort "%s %s %s\n" tool_opt  multiThread  paraReduction )
    else
      ;; print values out using default %L format if they are not all strings
      fprintf(myPort "%L %L %L\n" tool_opt  multiThread  paraReduction )
    )
    

    You could even build the format string based on the variable data type (that seems overkill here).

    Regards,

    Lawrence.

    • 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.

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

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