Use of compare_model_timing in SoC Encounter

Discussion in 'Cadence' started by Hannes, Aug 10, 2011.

  1. Hannes

    Hannes Guest

    Hello,

    does somebody know how to use the compare_model_timing command in SoC
    Encounter?

    in the documentation I found the following description:

    compare_model_timing

    Compares two reports that contain interface timing characteristics
    generated by the
    write_model_timing command.

    This command compares the interface timing characteristics report
    generated by using
    the write_model_timing command on the original netlist with the report
    generated
    by using the write_model_timing command on the model extracted by the
    do_extract_model command for the same design.


    My problem is, that I find no description how to tell the
    write_model_timing command that it has to run on the original netlist or
    the extracted model, respectively.

    I get the following options, when I type only the command:

    Usage : write_model_timing -type {arc | slack} -slew_propagation {worst
    | path_based} -verbose <model_timing_report_file> -view <view_name>
    [-inputs <input_port_list>]: Restrict report to input ports
    specified in the list.
    [-outputs <output_port_list>]: Restrict report to output ports
    specified in the list.
    [-type {arc | slack}]: Switch to specify either arc-delays or
    worst-slack values are to be reported.
    [-slew_propagation {worst | path_based}]: Switch to specify the
    slew propagation mode.
    [-view <view_name>]: Report from the user specified view_name.
    [-verbose]: Prints command progress details.
    <model_timing_report_file>: User-specified output file.



    Does anybody have an idea?

    Best Regards


    Hannes
     
    Hannes, Aug 10, 2011
    #1
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. what must be associated in verilog file with LEF when imported in the SOC ENCOUNTER?

  2. SoC Encounter

  3. SoC Encounter via array.

  4. About floorplan and route using SOC Encounter

  5. problem about timing analysis in soc encounter

  6. How to use a DEF in SoC Encounter

  7. What do these two tools used in?? (1st Encounter / Soc Encounter)

Loading...