Stats

  • Locked Locked
  • Replies 4
  • Subscribers 91
  • Views 1311
  • 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

rda_Input(ui_captbl_file) array variable

tiEngr

Hi All,

Im writing a script to save encounter DB for export. The directory will contain all the lefs, libs, sdc, and cap table files. 

In order to do this I  have to update "rda_Input" array elements and save using saveDesign or saveConfig. Which was no problem updated except for rda_Input(ui_captbl_file)  element.  Seems like what ever is in the gui form that will be saved using saveDesign or saveConfig. Even if I update this variable.  For example:

 

encounter 6> set rda_Input(ui_captbl_file) "someFileName"
someFileName
encounter 7>  puts $rda_Input(ui_captbl_file)
someFileName
encounter 8> saveConfig some.conf
encounter 9> grep ui_captbl_file some.conf
set rda_Input(ui_captbl_file) ""

 

 encounter 14> set rda_Input(ui_leffile) "./lef/msl200_50hpa07_tech_4layer.lef"
./lef/msl200_50hpa07_tech_4layer.lef
encounter 15> saveConfig some.conf
encounter 16> grep ui_leffile some.conf
set rda_Input(ui_leffile) "./lef/msl200_50hpa07_tech_4layer.lef"

 In this case, Im using empty encounter shell. No design/lib loaded. 

 

Thanks

Irfan

Parents
  • tiEngr

    Thanks Bob, for checking into it.  Just wanted to point out odd behavior of TCL variable inside the shell. I do have one core dump scenerio.  I will post in a different thread. 

     

    Irfan

     

     

Reply
  • tiEngr

    Thanks Bob, for checking into it.  Just wanted to point out odd behavior of TCL variable inside the shell. I do have one core dump scenerio.  I will post in a different thread. 

     

    Irfan

     

     

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.