Your Analysis Matters ....

Hi,

Please find below timing summary from latest run.

 Rgds

The Sender

When a timing summary report from last night's run is asked, many people effortlessly paste that section at end of file and send it as a response.  Analysis of data is generally assumed as "not required" or "not meaningful" by sender.

Contrary to this belief or understanding, providing your analysis is very much appreciated by receiver. 

The engineer working on it knows everything about that part of design and is best suited to provide a crisp opinion on data and next actions. Moreover, summary hides many critical details and receiver assumes that what is not mentioned in email is a non-issue.

For the above example, if sender adds few lines of his analysis and suggestion then it will be much more meaningful compared to raw data. eg.

- Results improved from previous run.

- Only change from previous run is newly characterized .lib. The .lib tables has improved delays for input transition below 150ps.

- there is scope to improve violating paths. One more optimization should fix timing. Better to close DRC violations first.

- new .libs can also improve other blocks which are at synthesis stage. Area/power improvement of 2%-5% is possible.

Each one of us has good data analytics capability and few have lateral analytical capabilities too. Presenting an observation along with raw data helps the receiver to look at data from a new perspective which she/he might not have thought off. 

It can also be the first step to get into a constructive discussion with person receiving the data and learn a lot more in collaboration.

There are multiple benefits of adding your analysis of data, so send a complete package of "raw data + analysis" next time and every time. Make it a habit !!