Stats

  • Replies 3
  • Subscribers 148
  • Views 720
  • Members are here 0

skill code for maestro

AS202509094448

I want to use skill code in non gui method to save maestro history. Like manually it is in toolbar options-> save->hisotry

envSetVal("adexl.simulation" "saveLastNHistoryEntries" 'int 200)

Above command is working in CIW but it is limited to this icfb session. And gets reset at new icfb launch.

I want to use it for particular maestro in all icfb session. If I will edit cds.env file, it will set for all maestros. 

Parents
  • Andrew Beckett

    The setting is not per-maestro view. If you set the number of histories to save from Options->Save, all it does is set the environment variable you have mentioned above. So the SKILL you already have is the only way to do this - you cannot have one setting for one maestro view and a different setting for another.

    Andrew

  • AS202509094448
    in reply to Andrew Beckett

    Thanks Andrew. But why can't we use skill for all the manual setting? Is there any plan in future to do something like this? Like manually we can set it using options->save for separate maestro. But there is no function for maestro right now to access this option/variable.

  • Andrew Beckett
    in reply to AS202509094448

    You can use SKILL for doing this setting. It's the envSetVal() call you mentioned before. 

    To illustrate this - if you have two maestro sessions open, and then do Options->Save in one of them and change the number of history points saved and OK the form. Then in the second maestro session bring up Options->Save and you'll see that the number of history points to be saved is as it was in the other session. In other words, this is not a session-specific setting. It's a global setting, and is just setting the environment variable from a common form.

    Unless we changed this to be a per-maestro-session setting (which there is no plan to do), there would be no point having a different API to set it because it just sets the environment variable.

    Andrew

Reply
  • Andrew Beckett
    in reply to AS202509094448

    You can use SKILL for doing this setting. It's the envSetVal() call you mentioned before. 

    To illustrate this - if you have two maestro sessions open, and then do Options->Save in one of them and change the number of history points saved and OK the form. Then in the second maestro session bring up Options->Save and you'll see that the number of history points to be saved is as it was in the other session. In other words, this is not a session-specific setting. It's a global setting, and is just setting the environment variable from a common form.

    Unless we changed this to be a per-maestro-session setting (which there is no plan to do), there would be no point having a different API to set it because it just sets the environment variable.

    Andrew

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.