Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 13416
  • 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

Can I convert ocean to statement?

bobbygang

Hello,

In recently work I have found some new questions.

The first question perhaps is simple but I can't achieve it. In some case I may assign some variables. Then I want to know the command which can converts the variable to string.

For example I define  an array its first element is variable A

then I want to use string "A" in the code later.

but if I change the first element to B, I also want to get string "B" How can I do this?

Conversely  how to convert string to variable?

The second question, how can I change the plot curve color?

Now default curve color order of my plot is "red" "blue" "magenta " "black" "orange".......

How can I set the color order?

The third question, after an ocean run, is there anyway to store last analysis statement ?

 

 

 

 

Parents

  • If you have the name of a variable stored somewhere, you can then manipulate it. For example:

    A=23
    theVar='A  ; use a quote (normal quote) to prevent evaluation and thus theVar contains the symbol A
    symeval(theVar) => 23
    printf("The variable name is %s\n" theVar)
    set(theVar 56)
    A => 56
    theVarAsString=symbolToString(theVar) => "A"

    To find out colours, look in Tools->Display Resource Manager->Edit . Then look for the y0 to y9 layers (probably need to use "All" to see all layers). This will then (when you select it) show you the colour, and also the name of the "packet" used. You can also find the packet names by dumping the tech file from Tools->Technology File Manager. Once you have the packet name, you can look it up in the display.drf file (this may be in your PDK, or you may have it somewhere else) which defines the mapping of packet name to colour/line style etc. The idea is that the tech file merely says what packet name is used for each layer-purpose-pair, and the display.drf defines the meaning of that packet - so each user could have different colours if they wanted without needing to modify the tech fle.

    I don't really understand your last sentence. Do you mean an ADE "state" (i.e. what you save with Session->Save State)? If so, you cannot produce one of these from OCEAN (and I'm not sure why you would want to) - but this is based on a guess of what you really mean by your last sentence.

    Best Regards,

    Andrew.

Reply

  • If you have the name of a variable stored somewhere, you can then manipulate it. For example:

    A=23
    theVar='A  ; use a quote (normal quote) to prevent evaluation and thus theVar contains the symbol A
    symeval(theVar) => 23
    printf("The variable name is %s\n" theVar)
    set(theVar 56)
    A => 56
    theVarAsString=symbolToString(theVar) => "A"

    To find out colours, look in Tools->Display Resource Manager->Edit . Then look for the y0 to y9 layers (probably need to use "All" to see all layers). This will then (when you select it) show you the colour, and also the name of the "packet" used. You can also find the packet names by dumping the tech file from Tools->Technology File Manager. Once you have the packet name, you can look it up in the display.drf file (this may be in your PDK, or you may have it somewhere else) which defines the mapping of packet name to colour/line style etc. The idea is that the tech file merely says what packet name is used for each layer-purpose-pair, and the display.drf defines the meaning of that packet - so each user could have different colours if they wanted without needing to modify the tech fle.

    I don't really understand your last sentence. Do you mean an ADE "state" (i.e. what you save with Session->Save State)? If so, you cannot produce one of these from OCEAN (and I'm not sure why you would want to) - but this is based on a guess of what you really mean by your last sentence.

    Best Regards,

    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.