Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 15288
  • 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

Help on using rodCreatePath

Renee

In the rodCreatePath function, it contains subrectangle arguments. I tried to write a program to make a path with variable-number of subrectangles shown as below:

?subRect list(

 for(i 0 cnt_num-1
list(
?layer buildCnts_info->layer3
?width buildCnts_info->width3
?length          buildCnts_info->length3
?endOffset       buildCnts_info->offset
?sep  buildCnts_info->sep+(buildCnts_info->width3)*i
?justification  "center"
?space  buildCnts_info->sp
) ; end list
);end for

) ;end of subRect lists

But when I run the procedure ,there is always error "The last argument of subrectangle can only be a list".

 I don't know how to solve this problem, or maybe I should try to use rodCreateRect instead.

 I'd really appreciated if someone could help me on this problem.

Lei

Parents

  • Since you didn't send any code, I can only comment on what the error messages mean.

    The warning about the nestability limit of 5 is related to doing interactive functions in your layout window. For example, if you begin creating a rectangle in Virtuoso and have started the command but not finished it, you are in the middle of an "enterFunction". If, before you finish the rectangle, you start a ruler, then you have just "nested" two enter functions. Cadence has a setting where you can change the number of levels of nestability to be greater than five, but this is probably not what you need (it is on the CIW->Options->User Preferences form). What I suspect is happening is that you are creating an enterFunction to call your code for drawing your path with your variable number of sub rectangles. My guess is that your "enterPath" (or some enterFunction) is in the middle of a loop and thus causing your nesting problem. Move it out of the loop to solve the problem.

    I can't explain why you have an fprintf/sprintf error when you claim that line is commented out. However, if you are using one of the printf commands and you want to print out a list, you need to use the format spec %L rather than %s. This will allow you to print out a list. If it is for debugging purposes, you can always just use println(myvar).

    I don't know why you are getting the loadstring error either. It is likely that there is a syntax error in the skill code that you are loading that is causing this. What you should do is turn on some debugging features that will allow you to get more details about your errors. You can enable a deeper stack trace that shows you where your failure was and you can also see the values of variables when the failure happens.

    sstatus(stacktraceDump  t)
    sstatus(stacktrace  10)

    I hope this helps.

    Derek

Reply

  • Since you didn't send any code, I can only comment on what the error messages mean.

    The warning about the nestability limit of 5 is related to doing interactive functions in your layout window. For example, if you begin creating a rectangle in Virtuoso and have started the command but not finished it, you are in the middle of an "enterFunction". If, before you finish the rectangle, you start a ruler, then you have just "nested" two enter functions. Cadence has a setting where you can change the number of levels of nestability to be greater than five, but this is probably not what you need (it is on the CIW->Options->User Preferences form). What I suspect is happening is that you are creating an enterFunction to call your code for drawing your path with your variable number of sub rectangles. My guess is that your "enterPath" (or some enterFunction) is in the middle of a loop and thus causing your nesting problem. Move it out of the loop to solve the problem.

    I can't explain why you have an fprintf/sprintf error when you claim that line is commented out. However, if you are using one of the printf commands and you want to print out a list, you need to use the format spec %L rather than %s. This will allow you to print out a list. If it is for debugging purposes, you can always just use println(myvar).

    I don't know why you are getting the loadstring error either. It is likely that there is a syntax error in the skill code that you are loading that is causing this. What you should do is turn on some debugging features that will allow you to get more details about your errors. You can enable a deeper stack trace that shows you where your failure was and you can also see the values of variables when the failure happens.

    sstatus(stacktraceDump  t)
    sstatus(stacktrace  10)

    I hope this helps.

    Derek

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.