Innovus App Options ← Home
⚠ Educational Reference Only. This content is an independent study reference. App option names, descriptions and examples are provided for learning purposes. Always verify against official Cadence / Synopsys documentation. This site is not affiliated with or endorsed by Cadence Design Systems or Synopsys Inc.
12
INNOVUS APP OPTIONS

CTS Naming and Timing Drive

S.NoApp OptionDescriptionExample
1cts.multisource.subtree_split_cell _name_suffixSpecifies name suffix to use when splitting clock cells during multisource clock tap assignmentset_app_options -name cts.multisource.subtree_split_cell_name_suffix -value
2route.global.timing_drivenControls whether the route_eco command considers timing during global routing. Disable to prevent extraction and timing update during ECO routingfc_shell> set_app_options -name route.global.timing_driven -value true
3cts.multisource.subtree_split_net _name_prefixSpecifies name prefix to use for split nets during multisource clock tap assignmentset_app_options -name cts.multisource.subtree_split_net_name_prefix -value
4route.global.crosstalk_drivenControls whether the route_eco command considers crosstalk during global routing. Disable to prevent extraction and timing update, which can be time consuming for ECO routingfc_shell> set_app_options -name route.global.crosstalk_driven -value true
5cts.multisource.subtree_split_net _name_suffixSpecifies name suffix to use for split nets during multisource clock tap assignmentset_app_options -name cts.multisource.subtree_split_net_name_suffix -value
6em.net_violation_rule_typesSets the type of constraint rules to use during signal electromigration analysis
7cts.multisource.enable_multi_cor ner_supportEnables multicorner optimization during multisource clock tree synthesis. When enabled, the tool considers all corners associated with the mode in which the subtree options are defined. By default, the tool uses only the worst corner associated with the mode
8em.net_use_waveform_durationWhen false, the signal EM analysis command uses current integral based duration. When true, it uses current waveform based duration
9cts.multisource.ignore_drc_on_s ubtree_driverSpecifies which DRC constraints (maximum capacitance, maximum fanout, or both) of the clock drivers to ignore during multisource clock tree synthesis. By default, the tool considers max transition, capacitance, and fanout constraints of clock drivers. Relaxed or absent constraints on clock drivers can affect multisource clock tree QoRfc_shell> set_app_options -name cts.multisource.ignore_drc_on_subtree_driver -value "max_fanout max_capacitance"
10em.net_min_duty_ratioSets the minimum duty ratio for computing the peak current during signal electromigration analysis
11cts.multisource.subtree_routing_ modeEnables fishbone routing for the subtree clock nets during multisource clock tree synthesis
12em.net_metal_line_numberSets the metal line number used to look up the relaxation factor in the RMS constraint factor table provided in the constraints file
13power.clock_network_include_cl ock_sink_pin_powerControls whether sink power is included in the clock tree power report generated by report_clock_qor -type power. When set to off, sink power is not reported
14em.net_global_rms_relaxation_fa ctorSets the global relaxation factor for the RMS limit specified in the electromigration constraints file
15design.enable_via_ladder_protec tionPrevents via ladders from being edited. When true, the remove_shapes and remove_vias commands process only objects that do not belong to via laddersset_app_options -name design.enable_via_ladder_protection -value true
16em.net_duration_condition_for_p eakSets the duration value for peak current checking during signal electromigration analysis
17route.common.global_min_layer_ modeDetermines whether the global minimum routing layer constraint (set by -min_routing_layer of set_ignored_layers) is treated as a hard or soft constraint. Constraints can cause blocked ports only when defined as hard constraints
18em.net_delta_temperatureSets the delta temperature used for RMS limit lookup during signal electromigration analysis
19route.common.global_max_layer _modeDetermines whether the global maximum routing layer constraint (set by -max_routing_layer of set_ignored_layers) is treated as a hard or soft constraint. Constraints can cause blocked ports only when defined as hard constraints
20route.common.eco_fix_drc_in_ch anged_area_onlyWhen using optimize_routability -route, fixes DRC violations only in areas that have changes rather than the entire designset_app_options -name route.common.eco_fix_drc_in_changed_area_only -value on
21route.common.net_min_layer_m odeDetermines whether the net-specific and clock minimum routing layer constraints (set by -min_routing_layer of set_routing_rule and set_clock_routing_rules) are treated as hard or soft constraints. Constraints can cause blocked ports only when defined as hard constraints
22route_opt.flow.size_only_modeEnables size-only mode for route_opt to close final setup, hold, or logical DRC violations with minimal disturbance to the block. Values: true_footprint (exact physical match), footprint (same footprint attribute), equal (equal size), equal_or_smaller (equal or smaller size), none/empty to disable
23route.common.net_max_layer_m odeDetermines whether the net-specific and clock maximum routing layer constraints (set by -max_routing_layer of set_routing_rule and set_clock_routing_rules) are treated as hard or soft constraints. Constraints can cause blocked ports only when defined as hard constraints
24route_opt.eco_route.modeControls whether route_opt performs ECO routing using detail routing iterations or track assignment. Set to 'track' to perform track assignment instead of detail routing
25route.common.freeze_layer_by_l ayer_nameSpecifies freeze layer constraints by layer name, which are considered when checking for blocked ports
26route.detail.eco_max_number_of _iterationsControls the number of detail routing iterations performed during the ECO routing phase of route_opt. By default, five detail routing iterations are performed
27route.common.freeze_via_to_fro zen_layer_by_layer_nameSpecifies freeze-via-to-frozen-layer constraints by layer name, which are considered when checking for blocked ports
28ccd.ccd_opt_voltage_drop_enabl e_ml_predictorEnables machine learning predictor for CCD voltage drop optimization flowfc_shell> set_app_options -name ccd.ccd_opt_voltage_drop_enable_ml_predictor -value true
29route.common.extra_via_off_grid _cost_multiplier_by_layer_nameDiscourages off-grid routing for vias by increasing the cost of routing the via enclosure metal shapes off the wire track grid. Sets the extra cost multiplier for the metal layers on which the via enclosures are routed. The effective cost is the base cost times (1+multiplier)fc_shell> set_app_options \ -name route.common.ex tra_via_off_grid_cost_multiplier_by_layer_name \ -value {{M2 0\.6}}
30route_opt.flow.enable_irdrivenoptEnables IR-driven optimization (IRDOPT) during route_opt using dynamic voltage drop analysisfc_shell> set_app_options -name route_opt.flow.enable_irdrivenopt -value true
31route.common.connect_within_pi ns_by_layer_nameSpecifies, per layer, the mode that restricts how the router connects to pins. With via_all_pins, the via enclosures must be inside the pin shape. With via_wire_standard_cell_pins, both the via enclosures and wires must be inside the pin shapefc_shell> set_app_options \ -name route.common.connect_within_pins_by_layer_name \ -value {{M1 via_all_pins}}
32time.pba_optimization_modeSets the path-based analysis (PBA) optimization mode during route_opt ML optimizationfc_shell> set_app_options -name time.pba_optimization_mode -value path
33route.global.timing_drivenEnables timing-driven global routing. By default the route_global command is not timing-driven. When enabled, the global router considers the impact of layer resistance by minimizing the usage of pin access layers, even if this increases wire lengthset_app_options -name route.global.timing_driven -value true
34route_opt.flow.enable_ml_optoEnables path-based optimization with machine learning during route_optfc_shell> set_app_options -name route_opt.flow.enable_ml_opto -value true
35route.detail.drc_convergence_eff ort_levelChanges the effort that the detail router uses for fixing the remaining DRC violations before it gives up (when it cannot fix any of the remaining violations)fc_shell> set_app_options \ -name route.detail.drc_convergence_effort_level -value maximum
36route_opt.flow.enable_powerEnables power optimization during route_opt; type depends on scenario (total or leakage)fc_shell> set_app_options -name route_opt.flow.enable_power -value true
37route.detail.force_max_number_i terationsForces the detail router to complete the maximum number of iterations, regardless of the DRC convergence statusfc_shell> set_app_options \ -name route.detail.force_max_number_iterations -value true
38route_opt.flow.enable_clock_pow er_recoveryEnables clock tree area recovery or clock tree power recovery during route_optfc_shell> set_app_options -name route_opt.flow.enable_clock_power_recovery -value area
39route.detail.timing_drivenEnables timing-driven detail routing. By default detail routing is not timing-driven. When enabled, Zroute uses medium effort to assign timing-critical nets to low-resistance metal layersfc_shell> set_app_options \ -name route.detail.timing_driven -value true
40route_opt.flow.enable_ctoEnables clock logical DRC fixing during route_opt; only supported when CCD is not enabledfc_shell> set_app_options -name route_opt.flow.enable_cto -value true
41route.common.rc_driven_setup_ effort_levelChanges the extent to which timing-driven detail routing prefers lower-resistance metal layers when routing timing-critical nets. Set to high to use more low-resistance metal layers, low to reduce the effort, or off to disable resistance-based routing layer preferencesset_app_options -name route.common.rc_driven_setup_effort_level -value maximum
42route_opt.flow.enable_ccdEnables concurrent clock and data (CCD) optimization and timing-driven clock logical DRC fixing during route_optfc_shell> set_app_options -name route_opt.flow.enable_ccd -value true
43route.global.crosstalk_drivenEnables crosstalk-driven global routing. Set to true (along with route.track.crosstalk_driven and time.si_enable_analysis) to enable crosstalk-driven modeset_app_options -name route.global.crosstalk_driven -value true
44time.pba_optimization_modeControls path-based analysis (PBA) mode used by the route_opt command during postroute optimization. 'path' uses PBA for the worst path of each endpoint identified by graph-based analysis (recommended). 'exhaustive' uses exhaustive path-based search for each endpoint, increasing runtimefc_shell> set_app_options -name time.pba_optimization_mode -value path
45route.track.crosstalk_drivenEnables crosstalk-driven track assignment. Set to true (along with route.global.crosstalk_driven and time.si_enable_analysis) to enable crosstalk-driven modeset_app_options -name route.track.crosstalk_driven -value true
46route.common.check_shieldEnables shielding checks during routing. Detects issues such as signal nets with shield_route shape_use, PG net shapes with detail_route use, and nets with shielding NDR but no associated shield shapesfc_shell> set_app_options -name route.common.check_shield -value true
47time.si_enable_analysisEnables signal integrity (crosstalk) analysis. Set to true (along with route.global.crosstalk_driven and route.track.crosstalk_driven) to enable crosstalk-driven modeset_app_options -name time.si_enable_analysis -value true
48route.common.reshield_modified _netsControls incremental shielding behavior for nets modified after initial shielding. Set to 'unshield' to remove existing shielding only from modified nets, or 'reshield' to remove existing shielding and reshield the modified nets with new topology
49route.common.post_detail_route _fix_soft_violationsEnables the fixing of soft DRC violations after the final detail routing iterationfc_shell> set_app_options \ -name route.common.post_detail_route_fix_soft_violations \ -value true
50route.common.allow_pg_as_shie ldIf you want to use power and ground nets for shielding and do not want Zroute to reserve space for the shielding when power and ground nets are available, set The option to true before running signal routing
51route.common.pg_shield_distanc e_thresholdSets the distance threshold, in microns, within which the power and ground structure is included in the shielding ratio calculation. By default, the power and ground structure is not included in the shielding ratio calculationfc_shell> set_app_options -name route.common.pg_shield_distance_threshold -value distance
52route.common.pg_shield_distanc e_thresholdSets the distance threshold in microns for including power and ground structure within a threshold distance in the shielding ratio calculationfc_shell> set_app_options -name route.common.pg_shield_distance_threshold -value distance
53time.pba_optimization_modeSets the path-based analysis (PBA) mode for postroute optimization
54route.common.shielding_netsSets the power or ground nets to which shielding wires are tied when the block contains multiple ground nets or when shielding wires should be tied to the power net. Must be set before running the create_shields command
55route_opt.flow.enable_ccdEnables concurrent clock and data optimization during postroute optimization
56route.common.min_shield_length _by_layer_nameSets the minimum wire length in microns on which to perform shielding for each routing layer. Takes {layer wire_length} pairs. Wires shorter than this length are not shieldedset_app_options -name route.common.min_shield_length_by_layer_name -value {{M1 0\.6} {M2 0\.6}}
57route_opt.flow.enable_powerEnables power optimization during postroute optimization
58route.common.rc_driven_setup_ effort_levelControls the effort level for using low-resistance metal layers when routing timing-critical nets in timing-driven mode. Setting to high increases use of low-resistance layers; low reduces it; off disables resistance-based preferencesfc_shell> set_app_options -name route.common.rc_driven_setup_effort_level -value maximum
59route_opt.flow.enable_multibit_d ebankingEnables the hyper_route_opt command to debank sequential multibit registers to improve timing QoR
60route.detail.timing_drivenEnables timing-driven mode for detail routing. When enabled, the router considers timing criticality during detail routefc_shell> set_app_options -name route.detail.timing_driven -value true
61design.enable_via_ladder_protec tionEnables protection of via ladder objects from editing. When enabled, commands such as remove_objects, set_attribute, set_via_def, and add_to_edit_group will issue a warning and not process objects that are part of a via ladderfc_shell> set_app_options -name design.enable_via_ladder_protection -value true
62route.track.timing_drivenEnables timing-driven mode for track assignment. When enabled, the router considers timing criticality during track assignmentfc_shell> set_app_options -name route.track.timing_driven -value true
63route.auto_via_ladder.update_du ring_routeEnables automatic via ladder updates during route_group, route_auto, and route_eco commands; verifies existing ladders, removes invalid ones, and inserts new onesfc_shell> set_app_options -name route.auto_via_ladder.update_during_route -value true
64route.global.timing_drivenEnables timing-driven mode for global routing. When enabled, the router considers timing criticality during global routefc_shell> set_app_options -name route.global.timing_driven -value true
65route.auto_via_ladder.update_on _route_group_nets_onlyDuring the route_group command, restricts via ladder updates to only the nets specified in the route_group commandfc_shell> set_app_options -name route.auto_via_lad der.update_on_route_group_nets_only -value true
66route.detail.report_ignore_drcSpecifies DRC rule names to exclude from the routing violations summary report, filtering out violations not of interestset_app_options -name route.detail.report_ignore_drc -value list_of_drcs
67route.auto_via_ladder.connect_w ithin_metalControls via enclosures for all types of via ladders (performance, electromigration, pattern-must-join); set to true to prevent changes to pin shape boundaryset_app_options -name route.auto_via_ladder.connect_within_metal -value true
68route.detail.save_cell_prefixSets the prefix string for block names saved after routing iterations. Default prefix is 'DR'- (referenced by name only)
69route.auto_via_ladder.connect_w ithin_metal_for_via_ladderControls via enclosures specifically for performance and electromigration via ladders; overrides the global setting for these typesset_app_options -name route.auto_via_ladder.conne ct_within_metal_for_via_ladder -value true
70route.detail.save_after_iterationsSaves the design block after a specified number of detail routing iterations so DRC violations can be viewed before postroute optimization. Saved block is named DR_itrn- (referenced by name only)
71route.auto_via_ladder.auto_stag gerAllows via ladder staggering when the maximum number of stagger tracks is not defined in the via ladder ruleset_app_options -name route.auto_via_ladder.auto_stagger -value true
72route.common.post_incremental _detail_route_fix_soft_violationsEnables fixing of soft DRC violations (such as bridge rule violations) after the final incremental detail routing iterationfc_shell> set_app_options -name route.common.pos t_incremental_detail_route_fix_soft_violations -value true
73route.auto_via_ladder.report_all_ via_laddersControls the number of via ladders reported per category; when false, limits report to 40 entries per categoryset_app_options -name route.auto_via_ladder.report_all_via_ladders -value true
74route.common.post_detail_route _fix_soft_violationsEnables fixing of soft DRC violations (such as bridge rule violations) after the final detail routing iterationfc_shell> set_app_options -name route.common.post_detail_route_fix_soft_violations -value true
75route.detail.var_spacing_to_sam e_netControls whether nondefault spacing rules are honored between shapes of the same signal net during detail routingset_app_options -name route.detail.var_spacing_to_same_net -value true
76route.detail.repair_shorts_over_ macros_effort_levelEnables and controls the effort level for fixing shorted nets over macro cells by automatically ripping up and rerouting them during incremental detail routing. Higher effort performs more ECO routing iterationsfc_shell> set_app_options -name route.detail.repair_shorts_over_macros_effort_level -value maximum
77route.common.ignore_var_spaci ng_to_shieldControls whether nondefault spacing rules between signal nets and shield wires for PG nets are ignored during routingset_app_options -name route.common.ignore_var_spacing_to_shield -value true
78route.detail.optimize_partition_si ze_for_drcEnables automatic optimization of partition size for DRC improvement in detail routing; improves QoR and reduces runtime for designs with standard cells containing long pinsset_app_options -name route.detail.optimize_partition_size_for_drc -value true
79route.common.ignore_var_spaci ng_to_pgControls whether nondefault spacing rules between signal nets and PG nets are ignored during routingset_app_options -name route.common.ignore_var_spacing_to_pg -value true
80time.si_enable_analysisEnables signal integrity (crosstalk) analysis; required for crosstalk-driven track assignmentset_app_options -name time.si_enable_analysis -value true
81route.common.ignore_var_spaci ng_to_blockageControls whether nondefault spacing rules between signal nets and blockages are ignored during routingset_app_options -name route.common.ignore_var_spacing_to_blockage -value true
82route.track.crosstalk_drivenEnables crosstalk-driven mode for track assignment; must also set time.si_enable_analysis to trueset_app_options -name route.track.crosstalk_driven -value true
83route.common.soft_rule_weight_t o_effort_level_mapMaps soft spacing rule weight levels (low, medium, high) to routing effort levels. Controls how aggressively the router attempts to fix soft spacing rule violations based on their weight classificationfc_shell> set_app_options -name route.common.soft_rule_weight_to_effort_level_map -value { {minimal minimal} {medium medium} {maximum maximum} }
84route.track.timing_drivenEnables timing-driven mode for track assignmentset_app_options -name route.track.timing_driven -value true
85route.common.wire_on_grid_by_l ayer_nameControls off-grid routing for metal layers, overriding technology file onWireTrack and onGrid attribute settings. Specify layers with true to forbid off-grid routing or false to allow itfc_shell> set_app_options -name route.common.wire_on_grid_by_layer_name -value {{M2 true} {M3 true}}
86time.si_enable_analysisEnables signal integrity analysis. Required along with route.global.crosstalk_driven to enable crosstalk-driven global routing
87route.common.via_on_grid_by_la yer_nameControls off-grid routing for via layers, overriding technology file onGrid attribute settings. Specify via layers with true to forbid off-grid routing or false to allow itfc_shell> set_app_options -name route.common.via_on_grid_by_layer_name -value {{V2 true}}
88route.global.crosstalk_drivenEnables crosstalk-driven global routing when set to true. The router calculates net delays before invoking the global router
89route.auto_via_ladder.pattern_m ust_join_over_pin_layerControls the structure level used for pattern-based must-join pin connections. Setting to 2 enables a multi-level structure instead of the default single-levelfc_shell> set_app_options -name route.auto_via_lad der.pattern_must_join_over_pin_layer -value 2
90route.global.timing_driven_effort _levelControls the tradeoff between timing QoR and DRC convergence during timing-driven global routing; high setting favors timing QoR over DRC convergenceset_app_options -name route.global.timing_driven_effort_level -value maximum
91route.auto_via_ladder.pattern_m ust_join_max_number_stagger_t racksSets the maximum number of tracks allowed for staggering on each level of the via ladder to avoid fixed shapes blocking insertion- (referenced by name only)
92route.global.advance_node_timin g_driven_effortControls effort for timing-driven global routing to reduce runtime at possible cost to timing QoR. When set to medium, reroutes newly critical nets only if it does not increase congestion and reduces number of rerouting phases. When set to low, skips timing update and reduces rerouting phases furtherset_app_options -name route.global.advance_node_timing_driven_effort -value medium
93route.auto_via_ladder.pattern_m ust_join_max_number_stagger_t racksSets the maximum number of stagger tracks allowed per level for pattern-based must-join pin connections. Accepts a list with one value per metal levelfc_shell> set_app_options -name route.auto_via_lad der.pattern_must_join_max_number_stagger_tracks -value {3 0}
94route.global.export_soft_congesti on_mapsSaves soft congestion data (including soft nondefault spacing rules and tool-generated soft rules) in the design library after global routingset_app_options -name route.global.export_soft_congestion_maps -value true
95route.auto_via_ladder.update_on _route_group_nets_onlyRestricts pattern-based must-join connection updates during the route_group command to only the nets specified in that commandfc_shell> set_app_options -name route.auto_via_lad der.update_on_route_group_nets_only -value true
96route.global.force_full_effortForces the global router to perform the maximum number of rerouting phases based on the specified effort level, even if congestion appears solvedset_app_options -name route.global.force_full_effort -value true
97route.auto_via_ladder.update_pa ttern_must_join_during_routeControls whether pattern-based must-join connections are updated each time route_auto, route_group, or route_eco commands are run. Setting to false disables all updatesfc_shell> set_app_options -name route.auto_via_lad der.update_pattern_must_join_during_route -value true
98route.global.via_cut_modelingEnables via density modeling during global routing; the tool calculates the number of vias in each global routing cell and reports via overflowsset_app_options -name route.global.via_cut_modeling -value true
99route.common.connect_within_pi ns_by_layer_nameSpecifies per-layer restrictions on how signal routes connect to cell pins (via vs wire, standard cell vs all pins). Takes {layer mode} pairsset_app_options -name route.common.connect_within_pins_by_layer_name -value {{M1 off}}
100route.detail.topology_eco_effort_l evelControls the effort level and number of topology ECO iterations for fixing secondary PG cluster fanout violations during Zroutefc_shell> set_app_options -name route.detail.topology_eco_effort_level -value medium
101route.common.connect_within_pi ns_by_layer_nameSpecifies which layers and via types are allowed for via-to-pin and wire-to-pin connections within pins. Used to restrict how wires connect to cell pins to avoid DRC violationsfc_shell> set_app_options -name route.common.connect_within_pins_by_layer_name -value {{M1 via_wire_standard_cell_pins}}
102route.common.separate_tie_off_f rom_secondary_pgSeparates tie-off connections from secondary power and ground connections so that routing constraints can be applied independently to secondary PGfc_shell> set_app_options -name route.common.separate_tie_off_from_secondary_pg -value true
103route.detail.enable_ndr_tapering _on_voltage_ruleControls pin tapering on nets that have both a nondefault routing rule (defined by create_routing_rule) and voltage-based spacing rules defined in the technology file. By default, Zroute performs pin tapering on such nets based on the nondefault routing rule. Set to false to disable pin tapering on these nets
104route.common.number_of_secon dary_pg_pin_connectionsEstablishes the maximum number of secondary power or ground pins in a cluster. A cluster is a set of connected secondary PG pins that has one connection to a PG strap or ring. Setting to 1 connects all secondary PG pins directly to a PG strap or ringfc_shell> set_app_options -name route.common.nu mber_of_secondary_pg_pin_connections -value 1
105route.detail.pin_taper_modeControls the wire tapering target width at pins during detail routing. Default tapers to the routing layer default width; pin_width tapers to the pin widthfc_shell> set_app_options -name route.detail.pin_taper_mode -value pin_width
106route.common.connect_within_pi ns_by_layer_nameRequires that connections at specified layers use vias contained within the pin shapes. Specified as a list of {layer via_type} pairsfc_shell> set_app_options -name route.common.connect_within_pins_by_layer_name -value {{M1 via_standard_cell_pins}}
107route.detail.use_wide_wire_effort _levelEnables pin tapering only when required to avoid DRC violations. Improves nondefault via rate at cost of longer runtime. Use only when majority of pins on routed nets are accessible with nondefault viasfc_shell> set_app_options -name route.detail.use_wide_wire_effort_level -value minimal
108route.common.single_connection _to_pinsSpecifies preferred single connection to pins for secondary power and ground pin routing. Setting to standard_cell_pins requires a single connection to the secondary PG pinsfc_shell> set_app_options -name route.common.single_connection_to_pins -value standard_cell_pins
109route.detail.use_wide_wire_to_in put_pinWhen set to true, disables wire tapering for input pins during detail routingfc_shell> set_app_options -name route.detail.use_wide_wire_to_input_pin -value true
110route.common.post_group_route _fix_soft_violationsEnables fixing of soft DRC violations (such as bridge rule violations) after the final detail routing iteration when using route_groupfc_shell> set_app_options -name route.common.post_group_route_fix_soft_violations -value true
111route.detail.use_wide_wire_to_o utput_pinWhen set to true, disables wire tapering for output pins during detail routingfc_shell> set_app_options -name route.detail.use_wide_wire_to_output_pin -value true
112route.common.clock_topologyControls the routing topology used for clock mesh nets. By default, Steiner routing is used to minimize total wire length; setting to comb uses comb routing insteadset_app_options -name route.common.clock_topology -value comb
113route.detail.use_wide_wire_to_m acro_pinWhen set to true, disables wire tapering for macro pins during detail routingfc_shell> set_app_options -name route.detail.use_wide_wire_to_macro_pin -value true
114route.common.verbose_levelControls the verbosity of the routing log. When set to 1, displays settings for all routing options (not only those that have been explicitly set) in the routing logfc_shell> set_app_options -name route.common.verbose_level -value 1
115route.detail.use_wide_wire_to_p ad_pinWhen set to true, disables wire tapering for pad pins during detail routingfc_shell> set_app_options -name route.detail.use_wide_wire_to_pad_pin -value true
116route.detail.allow_default_rule_n ets_via_ladder_lower_layer_con nectionWhen set to true, allows nets with default routing rules to connect directly to the pin or to any layer of the via ladderfc_shell> set_app_options -name route.detail.allow_ default_rule_nets_via_ladder_lower_layer_connectio n -value true
117route.detail.use_wide_wire_to_p ortWhen set to true, disables wire tapering for ports during detail routingfc_shell> set_app_options -name route.detail.use_wide_wire_to_port -value true
118route.detail.via_ladder_upper_lay er_via_connection_modeControls how vias connect to via ladders. Setting to 'any' allows vias to connect to the top level of a via ladder from belowfc_shell> set_app_options -name route.detail.via_lad der_upper_layer_via_connection_mode -value any

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

Replying to