http://www.maketecheasier.

com/8-useful-and-interesting-bash-prompts/
https://solvnet.synopsys.com/retrieve/015861.html?otSearchResultSrc=advSearch&ot
SearchResultNumber=1&otPageNum=1
https://solvnet.synopsys.com/retrieve/002064.html?otSearchResultSrc=advSearch&ot
SearchResultNumber=10&otPageNum=1
https://solvnet.synopsys.com/retrieve/031744.html?otSearchResultSrc=advSearch&ot
SearchResultNumber=1&otPageNum=1
http://www.paripath.com/blog/characterization-blog/comparing-nldm-and-ccs-delaymodels
http://www.suvolta.com/technology/ddc/
http://www.synopsys.com/Company/Publications/SynopsysInsight/Pages/Art2-finfet-c
hallenges-ip-IssQ3-12.aspx
http://www.techdesignforums.com/practice/technique/using-multi-corner-multi-mode
-techniques-to-meet-the-p-r-challenges-at-65-nm-and-below/
http://www.semiwiki.com/forum/content/2644-brief-history-docea-power.html?goback
=.gde_30219_member_262961008
http://www.semiwiki.com/forum/content/2631-power-reliability-sign-off-%96-must-b
ut-how.html?goback=%2Egde_53610_member_261700729
http://www.zimmerdesignservices.com/better_way_to_do_it.pdf
http://www.ee.bgu.ac.il/~digivlsi/slides/synopsys_class_2_5_1.pdf
http://vlsiweb.stanford.edu/~jsolomon/SPP/manpages/Synopsys__Collection.html
http://iccprocedures.blogspot.in/2009/02/icc-get-worst-timing-paths-end-point.ht
ml
SSH File Transfer with PuTTY - hostknox.com
http://www.hostknox.com/tutorials/ssh/putty/file-transfer

Basic idea is to get the timing path and manipulate the points attribute of the
timing path.
With the points, you can get all other info like nets, ref lib cell and so on...
through simple code manipulation.
Anyways try this code below to get the cells. Try using the lappend or add_to_co
ll commands
if you prefer to store the cells for further analysis rather than echoing.
You can also use get_timing_path -group -nworst etc switches to expand your sear
ch to multiple paths.
set start_point "enter your start point of interest here"
set end_point "enter your end point of interest here"
set timing_path [get_timing_path -from $start_point -to $end_point]
set timing_points [get_attr $timing_path points]
foreach_in_collection this_point $timing_points {
echo "[get_object_name [get_cells -of_obj [get_object_name [get_attr $this_point
object]]]]"
}

Extra space is shown to be more efficient for shorter and

narrower lines while shield insertion is preferable for longer
and thicker lines. The effect of the driver resistance of the
interconnect line on the crosstalk noise is also investigated.
Shielding is preferable for smaller driver resistances and
physical spacing is preferable for higher driver resistances. The

ratio of the ground capacitance to the coupling capacitance is

explored in terms of mitigating coupling noise. Shield insertion
is preferable for those lines with higher coupling capacitance
than line-to-ground capacitance