*: MECO Linting Checker
*:: Requirements
*::: Command to get list of changed modules:
*:::: User can refer information from ‘report_eco_change’ . After that user need to specify which module they want to check.


*::: This checker is target on the netlist design which include (assign statement) but not include behavior modeling (like always block , or others)
*:::  Q: What’s defined as a netlist and what’s defined as a behavior code requires your expertise to complete it. Basically, a netlist is what it can be accepted by Innovus.

*::: Command Name  :   check_connection <module>  [-recursive]
*:::: This command check the design connection for the following scenarios on this module. When with ‘-recursive’, it will iterate the check on all the submodule that are
      Used in this module.

*::: Checks
*:::: 1. [multiple driven net] A net has multiple driving source.
*:::: 2. [floating input ] An input pin/inout pin is floating which implies there is no net is associated on the pin.
*:::: 3. [floating output] An output pin is floating which implies there is no net is associated on the pin
*:::: 4. [net with no driver] A net has no driving source which implies the net doesn’t connected to any of  module input/inout port, cell output/inout pin, instance output/inout pin.
*:::: 5. [net with no load] A net has no loading destination which implies the net doesn’t connected to any of module ouput/inout port, cell input/inout pin, instance input/inout pin.
*:::: 6. [floating port] A module port is floating implies there is no cell pin/instance pin/or assign net is associated on the port.
*:::: 7. [redundant wire ] A floating wire implies the wire is not connected to any module port

*:: Implementation Spec.
*::: TBD


*: FrequentlyAskedQuestions
*: CvstracDocumentation
*: WikiDocumentation
*: CreatingNewWiki
*: RecentChanges to CVSTrac.