Stats

  • Locked Locked
  • Replies 38
  • Subscribers 127
  • Views 26314
  • 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

skill to detect ADEXL options

ejm20

Im trying to create a skill script that will look at the ADEXL HPO options to calculate the required tokens.  Ive been able to read the options on the HPO panel but need some help with the rest.   Heres the beginning of the code:


;; defining the PreRun function
(define (PreRun session_name sdb_highandle mode_string test_name)
        (printf "Launching a new run %L %L %L %L\n" session_name sdb_highandle mode_string test_name)
       

       tests=axlGetTests(sdb_highandle)
            
    jobPolicyName=axlGetAttachedJobPolicy()->name
    distmethod=axlGetAttachedJobPolicy()->distributionmethod

         ;; traversing all the tests and changing the mt option as per the requirement

   foreach(  test_name cadr(tests)
      if(  axlGetEnabled(axlGetTest(sdb_highandle test_name)) then
          printf("test %s is enabled\n" test_name)
          testSession=axlGetToolSession(session_name test_name)
        
    println( "check MT options")        
    
          mt_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>mtOption~>value
          if(eq(strcmp(mt_opt "Manual")  0) printf("  Manual MT will be disabled!!! \n"))
          if(eq(strcmp(mt_opt "Disable")    0) printf("Disabled MT \n"))
          if(eq(strcmp(mt_opt "Auto")     0) printf(" Auto MT will be disabled!!! \n"))
          if(eq(strcmp(distmethod "Local") 0) then printf(" Turning off the MT options for this test \n")
            testSession~>simID~>data~>env~>data~>turboOpts~>data~>mtOption~>value="Disable" )

    println( "check tool options")        

      tool_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>uniMode~>value
       if(eq(strcmp(tool_opt "Spectre")  0) printf(" This is a Spectre run \n"))
       if(eq(strcmp(tool_opt "Turbo")  0) printf(" This is a Turbo run    \n"))
       if(eq(strcmp(tool_opt "APS")  0) printf(" This is an APS  run \n"))
       
    println( "check parasitic reduction option")        
 
       paraRed_opt=testSession~>simID~>data~>env~>data~>turboOpts~>data~>psrSwitch~>value
       if(eq(strcmp(paraRed_opt t )  0) printf(" parasitic reduction enabled \n"))
       if(eq(strcmp(paraRed_opt nil )  0) printf(" parasitic reduction disabled \n")

 The first issue is that paraRed_opt is either a nil or t  so strcmp wont work, is a simular command for t/nil ?

 Once I have the options gathered, I can use a series of if/thens but is there a more elegant way to handle this like with a truth table or increment command?

 Thanks

 

Parents

  • What I'm saying is that you should not use ADE L->Setup->Simulator/Dir/Host and set the simulator to "aps", nor should you do ADE XL->test->simulator and set that to "aps". The reason being that this interface was added initially to avoid breaking anything in spectre, but it does not support anything other than DC or transient analyses. It will be removed at some point in the future.

    The way to do it is to set the simulator to "spectre", and then set the "high performance options" form to "aps". The APS option on this form is definitely worth using - you'll get good speed improvement. Since APS (this way) supports all spectre analyses, having it as a separate simulator choice made no sense - better to be an option to spectre - hence the "High Performance Options" form.

    The plan is also to drop "Turbo" ultimately. With MMSIM101, APS on a single core takes the same number of tokens as "Turbo".

    The "aps" executable is essentially equivalent  to "spectre +aps" from the command line - it's kept for legacy for anyone with existing scripts.

    So given this, asiGetSimName() should never return "aps" unless you've used obsolete settings in ADE L or XL.

    Regards,

    Andrew.

Reply

  • What I'm saying is that you should not use ADE L->Setup->Simulator/Dir/Host and set the simulator to "aps", nor should you do ADE XL->test->simulator and set that to "aps". The reason being that this interface was added initially to avoid breaking anything in spectre, but it does not support anything other than DC or transient analyses. It will be removed at some point in the future.

    The way to do it is to set the simulator to "spectre", and then set the "high performance options" form to "aps". The APS option on this form is definitely worth using - you'll get good speed improvement. Since APS (this way) supports all spectre analyses, having it as a separate simulator choice made no sense - better to be an option to spectre - hence the "High Performance Options" form.

    The plan is also to drop "Turbo" ultimately. With MMSIM101, APS on a single core takes the same number of tokens as "Turbo".

    The "aps" executable is essentially equivalent  to "spectre +aps" from the command line - it's kept for legacy for anyone with existing scripts.

    So given this, asiGetSimName() should never return "aps" unless you've used obsolete settings in ADE L or XL.

    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.