Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 1743
  • 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

Relative Path to Device's Containing Folder

amaggs

I have been searching around trying to find a robust solution for this but have not found anything yet, I figured the best thing would be to see what others are doing.

We have a many libraries that store third-party components where we keep devices that are used on the evalution boards of our IC's, an example of a component that is kept in this library is a balun. This allows us to try to match up as best we can our measured results with what we are seeing in simulation.

All of our libraries are under subversion. Most of the devices in the components library have correponding S-Parameter files. If we choose to checkout one of our third-party components libraries from a released version the path will look something like this:

 /<server_name>/projects/<project_name>/<process_name>/shared1/<third-party_component_manufacturer_name>

But if we choose to check out the trunk version the path to device will look something like this:

 /<server_name>/projects/<project_name>/<process_name>/team/<user_name>/work1/<third-party_component_manufacturer_name>

You can see that the paths change quite a bit from checking out a release version versus checking out the trunk version. To make it even more complicated, if it is checked out as trunk, the path depends on what user has checked it out.

What I want to be able to do is put a path to the s-parameter file that can be used in the S-paramater data file field and somehow have it be releative to wherever the device is used. So whether the release or trunk version is checked out the link to the s-parameter won't be broken. It would be ideal if there is someway to have a relative path the points to a device's containing folder, or even the device's library folder, this way I could also keep the s-parameter file under subversion.

 Is there anyway to do this?  Thanks so much for any help

  • Hi amaggs,

    You cannot put in an s-parameter path inside the actual s-parameter file and expect ADE to use it (not supported).
     
    Assuming the s-parameter file name stays the same and only the path is changed, what you can do is use the include path.
     
    ADE->Setup Simulation Files->Include Paths
     
    You can specify the default include path in your .cdsenv or .cdsinit
     
    Then in the nport s-parameter file filed, you simply insert the name of the s-parameter file.
     
    Now, if you want to parameterize the s-parameter file name, I suggest looking at Cadence Online Support Solution
     
    11021266 (COS) Can you parameterize the filename for an nport in ADE/OCEAN?
     
    Not sure if this is exactly what you are looking for... but it's the closest thing I can think of at the moment.
     
    best regards,
    Tawna

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.