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:20240624T170000
DTEND;TZID=America/Los_Angeles:20240624T180000
UID:dac_DAC 2024_sess232_ETPOST107@linklings.com
SUMMARY:Executable Tables, 'A Journey from Document to Simulation Capable,
  Exemplified Using DDR5 '
DESCRIPTION:Engineering Track Poster\n\nRahil Jha and Joseph Bauer (Cadenc
 e Design Systems, Inc.)\n\nThere has been an everlasting trend to represen
 t information in tabular form in any kind of document irrespective of the 
 application since tabular format help convey more information in lesser wo
 rds. But extracting and processing data from these tables can be very chal
 lenging. Talking In context of Very Large-Scale Integration (VLSI) domain 
 etc. lots of useful information is encapsulated in tabular form in data sh
 eets, specification etc. This stands true for other applications like AI, 
 ML, DBMS etc. as well. Talking about Double Data Rate Generation 5 (DDR5) 
 specification itself has more than 300+ tables which contributes ~20% or m
 ore of entire specification and there's been >50 spec iterations in gettin
 g there. The manual extraction of this data and information is prone to er
 ror and requires significant efforts. Hence we proposed a solution for aut
 omatically extracting tabular information and doing some processing to con
 vert it into executable code form. Solution demonstrated is generic enough
  to be extended to other any application where information from tabular fo
 rm needs to be extracted and processed.\n\nTopic: Back-End Design, Embedde
 d Systems, Front-End Design, IP
END:VEVENT
END:VCALENDAR