BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/Chicago
BEGIN:DAYLIGHT
DTSTART:20230312T030000
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20221106T010000
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20230124T014538Z
UID:8C86671F-A30B-4550-905F-E077B5E33BE5
DTSTART;TZID=America/Chicago:20230123T183000
DTEND;TZID=America/Chicago:20230123T194500
DESCRIPTION:There is a lot of glorious high-tech science in modernsilicon I
 C design\, but someone still needs to take out the trash. Yes\, chip desig
 n is hardware engineering\, but with billions of gates on a chip\, softwar
 e is involved at every step. Mundane tasks for the engineer include analyz
 ing log files from EDA (Electronic Design Automation) tools\, which can sp
 ew out millions of lines with each run. How do you know which errors and w
 arnings really matter? And you can’t just ignore them – an undetected 
 error might mean a respin of masks\, costing millions of dollars and inest
 imable loss due to schedule slip. This talk describes how Marvell deals wi
 th large amounts of EDA tool logfile reports on a daily basis\, using data
  analysis techniques in Chew_Logs (Check Errors &amp; Warnings in Logfiles).\n
 \nSpeaker(s): Thomas Arneberg of Marvell Technology\, Inc.\, \n\nRoom: Man
 n Hall\, Bldg: Medical Sciences Building\, 300 3rd Ave SW\, Rochester\, Mi
 nnesota\, United States\, 55902
LOCATION:Room: Mann Hall\, Bldg: Medical Sciences Building\, 300 3rd Ave SW
 \, Rochester\, Minnesota\, United States\, 55902
ORGANIZER:pramanik.leena@ieee.org
SEQUENCE:3
SUMMARY:JANUARY TALK: ANALYZING MILLIONS OF LINES OF LOGFILES WITH CHEW_LOG
 S
URL;VALUE=URI:https://events.vtools.ieee.org/m/343650
X-ALT-DESC:Description: &lt;br /&gt;&lt;p&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20
 &quot;&gt;There is a lot of glorious high-tech &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;spa
 n class=&quot;bumpedFont20&quot;&gt;science&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;
 bumpedFont20&quot;&gt; in &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20
 &quot;&gt;modern&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;silicon 
 &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;IC&lt;/span&gt;&lt;/span&gt;
 &lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt; design\, but someone still ne
 eds to take out the trash. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bum
 pedFont20&quot;&gt;Yes\, c&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20
 &quot;&gt;hip design &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;is 
 hardware engineering\, but with billions of gates on a chip\, software is 
 involved at every step. &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumped
 Font20&quot;&gt;Mundane tasks for the engineer include &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;
 s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;analyzing log files from &lt;/span&gt;&lt;/span&gt;&lt;spa
 n class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;EDA (Electronic Design Automation)
  tools\, which can spew out millions of lines&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6
 &quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt; with each run&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;
 &lt;span class=&quot;bumpedFont20&quot;&gt;. How do you know which errors and warnings rea
 lly matter? &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;And 
 you can&amp;rsquo\;t &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;
 &gt;just ignore them &amp;ndash\; an undetected error might mean a respin of mask
 s\, costing millions of dollars and inestimable loss due to schedule slip.
  &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;This talk descr
 ibes how Marvell &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;
 &gt;deals with large amounts of &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;b
 umpedFont20&quot;&gt;EDA &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;
 &gt;tool logfile &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;re
 ports&lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt; on a daily
  basis\, using &lt;/span&gt;&lt;/span&gt;&lt;span class=&quot;s6&quot;&gt;&lt;span class=&quot;bumpedFont20&quot;&gt;d
 ata analysis techniques in Chew_Logs (Check Errors &amp;amp\; Warnings in Logf
 iles).&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
END:VEVENT
END:VCALENDAR