Stats

  • Locked Locked
  • Replies 8
  • Subscribers 126
  • Views 15891
  • 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

function call is some how retaining previous call values in SKILL

RFStuff

 Dear All,

I am calling function as below:-

       guardring(L_cell W_cell clearance W_guard Space_NTAP_PATAP First_type_tap).

      When I call second time this function in CIW, it some how retaining the previous call vlaues. So the outcome result is wrong.

       However when I call it 2nd time it gives me dsired result. It looks like the variable is NOT prempted after function call is over.

   Can anybody please tell why it happening. It looks like to me a file open/close problem.

My code is as below:

procedure( guardring(L_cell W_cell clearance W_guard Space_NTAP_PATAP First_type_tap)
xPitch=0.16+0.2
yPitch=0.16+0.2
;row=5
;column=20

    if( (First_type_tap=="N") then

        ; For Creating  NTAP
         
            NTAP_CONT_NO_IN_THICKNESS=car(guardtapsize( (W_guard+0.64) "NTAP" ))
                printf("NTAP_CONT_NO_IN_THICKNESS=%d",NTAP_CONT_NO_IN_THICKNESS)
            NTAP_THICKNESS= (NTAP_CONT_NO_IN_THICKNESS*0.36) +0.56
            printf("NTAP_THICKNESS=%f\n",NTAP_THICKNESS)
            NTAP_LENGTH=(2*(NTAP_THICKNESS+clearance))+L_cell
            NTAP_CONT_NO_IN_LENGTH=car(guardtapsize( NTAP_LENGTH "NTAP" ))
            NTAP_LENGTH= (NTAP_CONT_NO_IN_LENGTH*0.36) +0.56
            printf("NTAP_LENGTH=%f",NTAP_LENGTH)
            row=NTAP_CONT_NO_IN_THICKNESS
            column=NTAP_CONT_NO_IN_LENGTH
            xOffset=0
            yOffset=0
        guardlayercreate( "NTAP" xPitch yPitch row column xOffset yOffset "Y" )
           ...................................................................



 ....................................................................

) /*End of procedure*/  

procedure( guardtapsize( width type )
             ;declare(a[2])
             if( (type=="NTAP") then

               
             N_width=  ceiling(((width-0.56)/0.36))
             ;actual_width=( (N_width*0.36) +0.56)
                 printf("N_width=%d\n",N_width)
                     ;printf("actual_width=%f\n",actual_width)
                     ;a[0]=N_width
                     ;a[1]=actual_width
            else
                     
              N_width=  ceiling(((width-0.24)/0.36))
              ;actual_width=( (N_width*0.36) +0.24)
                      printf("N_width=%d\n",N_width)
                  ;printf("actual_width=%f\n",actual_width)
                      ;a[0]=N_width
                      ;a[1]=actual_width
             )
               list(N_width)    
          )

Parents
  • Andrew Beckett

    Your code above seems to have changed since the email you sent - but either way it's hard to tell because the code is not complete, nor did you give an example of what actually happens that is wrong.

    Your code is full of global variables - maybe you're using a global variable before it is defined (in some cases?) - nothing leaps out from the segment of the code you posted.  You should really use let() within the procedures to define local variables. I'd suggest running your code through SKILL Lint in the SKILL Development Tools (from the CIW Tools menu).

    Andrew.

Reply
  • Andrew Beckett

    Your code above seems to have changed since the email you sent - but either way it's hard to tell because the code is not complete, nor did you give an example of what actually happens that is wrong.

    Your code is full of global variables - maybe you're using a global variable before it is defined (in some cases?) - nothing leaps out from the segment of the code you posted.  You should really use let() within the procedures to define local variables. I'd suggest running your code through SKILL Lint in the SKILL Development Tools (from the CIW Tools menu).

    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.