Stats

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

Assura variable for runset name

Leonid Y

 Hi,

I want to include another Assura rulefile  with skill load() command.

When I use absolute path it works well, but I would like to define a relative one, to make it more flexible.

Is there a special variable  in Assura which contains a full path of currently running rule file?

Mybe there is also some other work around which could help including sub-rulefile which is stored in the same directory as a main rulefile.

  • Andrew Beckett

    I've never tried this with Assura, but in SKILL you can get the filename (it's not the full path necessarily, but what was requested to be loaded, so should be OK) by using get_filename(piport) .

    I'd be interested to know if this works. I've just not got time to try it myself right now.

    Andrew.

  • Leonid Y

    Thanks Andrew for the hint. The function returned a strange relative path with many ../../../.. but still correct. So I was able to convert it to a normal look with simplifyFilename() and then got directory name from the path.

    I wonder if there is a simple way to get a directory name from full path? I used

    parseString(path "/") ~> remd(car(last(.... ~> buildString( "/" ....)

  • Andrew Beckett

    Unfortunately there's no built-in dirname() function in SKILL (it would be useful if there was), so the way you've done it is as good as any other, probably. You could also use:

    pattern=pcreCompile("/[^/]*$")
    dirName=pcreReplace(pattern path "" 0)

    That's probably the way I'd do it. You could omit the "/" at the beginning of the pattern if you want to keep the trailing "/" in the dirName.

    Regards,

    Andrew.

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.