BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20240626T180033Z
LOCATION:Level 2 Exhibit Hall
DTSTART;TZID=America/Los_Angeles:20240625T170000
DTEND;TZID=America/Los_Angeles:20240625T180000
UID:dac_DAC 2024_sess233_ETPOST196@linklings.com
SUMMARY:Timing Takedown Reports 3
DESCRIPTION:Engineering Track Poster\n\nLukas Pettersson (Marvell)\n\nAs d
 esigns scale up in size and complexity timing takedown can become a tediou
 s and overwhelming task. Gathering any insightful information from the mil
 lions of paths that are generated from a full timing run is, in many cases
 , not possible. The solution to this problem is generally scripts that rea
 d in timing reports, summarize, process, and draw some conclusions about t
 he data. \n\nThese scripts are often a critical to any timing signoff. The
 refore, these scripts should be written to be customizable, lightweight, a
 nd first and foremost fast. By leveraging industry standard software archi
 tecture practices, we were able to write an application that that can be e
 asily expanded, handle reports from multiple tool vendors and technology n
 odes, run quickly, and is fully user customizable. By defining our own dat
 abase structure we let anyone write their own interfaces to this database,
  enabling any engineer with access to the program to write custom python s
 cripts using the same data, Using standardized software architectures also
  makes it easier to add or remove developers as needed to support future d
 evelopment. In addition, this methodology can serve as the first stepping 
 stone to sanitize data for AI/ML use cases.\n\nTopic: Back-End Design, Emb
 edded Systems, Front-End Design, IP
END:VEVENT
END:VCALENDAR