TechTables
Your library
Open full library →
Artificial Intelligence ·

Can AI Wearables Predict a Heart Attack Before It Strikes?

In this episode, Joe talks with University of Pittsburgh's Pengfei Zhou & Matt de Lima Barbosa, along with Dell Technologies' Adrienne Garber, about how AI, edge computing, and wearable devices are shaping the future of heart monitoring.

Joe Toste Joe Toste Santa Barbara, CA

Player

Can AI Wearables Predict a Heart Attack Before It Strikes?

Show notes

Key Takeaways

  1. Why wearables are the next frontier for heart health: how real-time sensor data from everyday devices could detect cardiovascular risk before symptoms ever appear.
  2. What AIoT actually means in practice: how Pengfei's research combines AI and connected sensors to build deep learning models that go far beyond step counting.
  3. The role of embedded IT in research speed: how Matt's team connects faculty to secure infrastructure and technical support so researchers can move faster and focus on the science.
  4. How Dell is partnering with higher ed researchers: why Adrienne's team invests in university innovation programs — and what that looks like when it reaches researchers working on real health problems.
  5. Why localized AI wins on speed, privacy, and personalization: the case for keeping AI processing at the edge instead of sending sensitive health data to the cloud.
  6. What the future of higher ed innovation actually requires: why the collaboration between researchers, IT, and technology partners like Dell is the ingredient most people overlook.

Featuring

  • Pengfei Zhou - Assistant Professor, University of Pittsburgh School of Computing and Information
  • Matt de Lima Barbosa Director of Information Technology, University of Pittsburgh School of Computing and Information
  • Adrienne Garber - Chief Technology and Innovation Strategist for Higher Education, Dell Technologies

Connect with Me

Platinum Newsletter Sponsor:

This newsletter is presented by Infotech, the fastest growing research & advisory firm that senior technology leaders in the public sector actually call when it matters.

—> Click here to see all ITRG episodes

Gold Newsletter Sponsor:

00:00:00 Welcome And Guest Introductions
00:02:37 Peng Fei's Teaching And Research Focus
00:04:10 Why Heart Disease Is The Number One Killer
00:06:49 Dell's Partnership With Pitt On AI Hardware
00:09:22 Vision For The Monitoring Platform's Future
00:10:44 Benefits Of Local Versus Cloud Processing
00:12:17 IT And Research Collaboration At Pitt
00:17:00 The Cross-Departmental Research Team
00:19:11 Combining Sensors To Measure Blood Pressure
00:21:06 Bridging University IT And Local Researchers
00:24:44 Defining AI Versus Deep Learning
00:28:13 What To Gain From Attending Conferences
00:35:01 Closing Thoughts And Thanks
WEBVTT

00:00:00.000 --> 00:00:02.680
Welcome<00:00:00.360> to<00:00:00.480> the<00:00:00.600> Public<00:00:00.920> Sector<00:00:01.200> Show<00:00:01.400> by<00:00:01.760> TechTables.

00:00:02.680 --> 00:00:08.760
Super<00:00:02.960> excited<00:00:03.280> to<00:00:03.320> have<00:00:03.480> everyone<00:00:03.880> on<00:00:04.200> cuz<00:00:04.360> we've<00:00:04.600> got<00:00:04.880> Peng<00:00:05.200> Fei<00:00:05.640> coming<00:00:05.920> back<00:00:06.640> and<00:00:06.760> we'll<00:00:06.840> kick<00:00:07.040> it<00:00:07.160> off<00:00:07.520> with<00:00:07.760> Peng<00:00:08.000> Fei.

00:00:08.760 --> 00:00:15.920
Why<00:00:08.840> don't<00:00:08.960> you<00:00:09.000> give<00:00:09.120> us<00:00:09.240> a<00:00:09.280> short<00:00:09.600> intro?<00:00:10.200> Hi,<00:00:10.560> very<00:00:10.840> excited<00:00:11.320> to<00:00:11.400> be<00:00:11.520> here<00:00:11.760> today<00:00:12.280> and<00:00:12.680> I'm<00:00:12.840> an<00:00:12.920> assistant<00:00:13.280> professor<00:00:14.320> in<00:00:14.440> the<00:00:14.520> University<00:00:14.960> of<00:00:15.040> Pittsburgh<00:00:15.720> School

00:00:15.920 --> 00:00:24.560
of<00:00:16.040> Computing<00:00:16.480> and<00:00:16.560> Information.<00:00:17.560> I<00:00:18.480> I'm<00:00:18.640> doing<00:00:18.880> some<00:00:19.040> research<00:00:19.640> on<00:00:19.840> cardiovascular<00:00:20.800> monitoring<00:00:21.800> for<00:00:21.920> everyday<00:00:22.240> life<00:00:22.920> and<00:00:23.360> uh<00:00:23.440> I'm<00:00:23.800> very<00:00:23.920> excited

00:00:24.560 --> 00:00:32.960
to<00:00:25.200> do<00:00:25.440> this<00:00:25.880> and<00:00:26.120> I<00:00:26.240> envisioned<00:00:27.120> that<00:00:27.720> we<00:00:27.880> can<00:00:28.120> have<00:00:28.400> a<00:00:28.840> tailored<00:00:29.240> device<00:00:29.960> and<00:00:30.080> tell<00:00:30.240> that<00:00:30.520> form<00:00:30.880> for<00:00:31.560> everybody<00:00:32.080> to<00:00:32.439> monitor<00:00:32.840> the

00:00:32.960 --> 00:00:37.760
health<00:00:33.760> and<00:00:34.320> to<00:00:34.480> provide<00:00:34.920> air<00:00:35.120> to<00:00:35.240> prevent<00:00:35.640> any<00:00:35.880> heart<00:00:36.160> attack<00:00:36.560> risk<00:00:37.120> in<00:00:37.240> the<00:00:37.320> future.

00:00:37.760 --> 00:00:41.560
Matt,<00:00:38.080> you<00:00:38.160> want<00:00:38.280> to<00:00:38.320> give<00:00:38.400> us<00:00:38.520> a<00:00:38.600> quick<00:00:38.840> intro?<00:00:39.480> Sure,<00:00:39.880> thanks<00:00:40.320> for<00:00:40.560> having<00:00:40.920> us<00:00:41.080> here.

00:00:41.560 --> 00:00:48.320
Hi,<00:00:41.920> I'm<00:00:42.280> Matt<00:00:42.480> Prophet.<00:00:42.880> I'm<00:00:43.040> director<00:00:43.760> of<00:00:43.960> information<00:00:44.480> technology<00:00:45.120> at<00:00:45.240> the<00:00:45.280> University<00:00:45.760> of<00:00:45.880> Pittsburgh<00:00:46.360> School<00:00:46.640> of<00:00:46.760> Computing<00:00:47.240> Information.

00:00:48.320 --> 00:00:55.280
I<00:00:48.720> am<00:00:49.080> a<00:00:49.160> young<00:00:49.480> father<00:00:50.000> of<00:00:50.400> a<00:00:50.560> 3-year-old<00:00:51.400> and<00:00:51.720> a<00:00:51.800> 22-day-old<00:00:53.440> daughter<00:00:53.960> and<00:00:54.240> I'm<00:00:54.320> very<00:00:54.600> happy<00:00:54.840> to<00:00:54.960> be<00:00:55.040> here.

00:00:55.280 --> 00:01:01.920
Thanks<00:00:55.680> for<00:00:55.840> inviting<00:00:56.200> me.<00:00:56.560> Super<00:00:56.840> excited<00:00:57.480> to<00:00:58.360> have<00:00:58.600> you<00:00:58.680> here<00:00:59.440> and<00:00:59.640> always<00:00:59.880> love<00:01:00.200> highlighting<00:01:01.200> higher<00:01:01.400> education.

00:01:01.920 --> 00:01:03.840
And<00:01:02.040> so<00:01:02.320> Matt,<00:01:02.800> let's<00:01:03.000> continue<00:01:03.320> with<00:01:03.480> you.

00:01:03.840 --> 00:01:06.640
Just<00:01:04.040> give<00:01:04.199> us<00:01:04.360> the<00:01:04.800> 30,000-foot<00:01:05.760> overview.

00:01:06.640 --> 00:01:09.200
What<00:01:06.800> does<00:01:06.920> it<00:01:07.000> look<00:01:07.200> like<00:01:07.520> for<00:01:07.720> other<00:01:07.920> viewers<00:01:08.280> who<00:01:08.360> are<00:01:08.440> listening<00:01:08.800> in?

00:01:09.200 --> 00:01:17.800
The<00:01:09.747> School<00:01:10.293> of<00:01:10.840> Computing<00:01:11.387> and<00:01:11.933> Information<00:01:12.480> has<00:01:13.027> currently<00:01:13.573> about<00:01:14.120> 2,200<00:01:14.667> students<00:01:15.213> and<00:01:15.760> about<00:01:16.307> 120<00:01:16.853> individuals<00:01:17.400> between

00:01:17.800 --> 00:01:21.360
faculty<00:01:18.280> and<00:01:18.400> staff.<00:01:19.200> We<00:01:19.320> do<00:01:19.680> research<00:01:20.280> in<00:01:20.400> several<00:01:20.800> areas.

00:01:21.360 --> 00:01:30.600
Most<00:01:22.440> One<00:01:22.600> of<00:01:22.680> the<00:01:22.880> field<00:01:23.120> of<00:01:23.280> top<00:01:23.640> areas<00:01:24.080> you<00:01:24.160> would<00:01:24.320> be<00:01:24.600> biomedical<00:01:25.360> and<00:01:25.440> clinical<00:01:26.200> research,<00:01:27.120> education,<00:01:28.080> technologies,<00:01:28.800> public<00:01:29.240> sector,<00:01:30.240> smart

00:01:30.600 --> 00:01:34.000
buildings,<00:01:31.240> cities,<00:01:31.720> and<00:01:31.840> transportation,<00:01:32.720> sustainability.

00:01:34.000 --> 00:01:42.400
The<00:01:34.080> research<00:01:34.600> here<00:01:34.840> comes<00:01:35.160> from<00:01:35.880> several<00:01:36.240> different<00:01:36.800> agencies<00:01:37.600> like<00:01:37.960> Google,<00:01:38.640> Microsoft,<00:01:39.880> NASA,<00:01:40.400> DARPA,<00:01:41.040> NIH,<00:01:42.200> just

00:01:42.400 --> 00:01:47.120
to<00:01:42.480> name<00:01:42.680> a<00:01:42.720> few.<00:01:43.280> That's<00:01:43.480> great.<00:01:44.000> So<00:01:44.160> now<00:01:44.880> bridging<00:01:45.360> to<00:01:46.200> Peng<00:01:46.480> Fei.

00:01:47.120 --> 00:01:51.040
Yeah,<00:01:47.349> tell<00:01:47.577> us<00:01:47.806> a<00:01:48.034> little<00:01:48.263> bit<00:01:48.491> more<00:01:48.720> about<00:01:48.949> what<00:01:49.177> you're<00:01:49.406> working<00:01:49.634> on<00:01:49.863> within<00:01:50.091> the<00:01:50.320> school.

00:01:51.040 --> 00:01:53.520
I'm<00:01:51.320> a<00:01:51.360> professor.<00:01:52.000> So<00:01:52.240> first<00:01:52.480> of<00:01:52.640> all,<00:01:52.800> I'm<00:01:52.920> a<00:01:53.000> professor.

00:01:53.520 --> 00:01:59.240
So<00:01:53.920> in<00:01:54.040> the<00:01:54.160> school<00:01:54.680> I<00:01:55.440> as<00:01:55.560> a<00:01:55.600> professor<00:01:56.120> I<00:01:56.200> do<00:01:56.360> everything<00:01:56.800> a<00:01:56.880> professor<00:01:57.880> does,<00:01:58.640> right?

00:01:59.240 --> 00:02:03.640
And<00:01:59.800> I<00:01:59.920> do<00:02:00.600> research,<00:02:01.320> teaching,<00:02:02.040> and<00:02:02.520> some<00:02:03.040> service.

00:02:03.640 --> 00:02:09.360
I<00:02:03.720> will<00:02:03.840> call<00:02:04.000> it<00:02:04.080> a<00:02:04.120> service.<00:02:04.520> Basically,<00:02:04.920> some<00:02:05.160> activities<00:02:05.880> within<00:02:06.240> the<00:02:06.360> school<00:02:06.880> or<00:02:07.000> department<00:02:08.039> or<00:02:08.280> within<00:02:08.600> the<00:02:08.640> university.

00:02:09.360 --> 00:02:17.320
So,<00:02:09.479> for<00:02:09.600> example,<00:02:09.960> you<00:02:10.080> have<00:02:10.399> organizing<00:02:11.280> a<00:02:11.360> workshop<00:02:12.240> or<00:02:12.560> you<00:02:12.959> host<00:02:13.520> a<00:02:13.600> committee<00:02:14.240> for<00:02:14.600> the<00:02:14.720> students<00:02:15.240> for<00:02:15.400> specific<00:02:15.840> students,<00:02:16.280> for<00:02:16.400> example,<00:02:16.640> award<00:02:16.959> student.

00:02:17.320 --> 00:02:20.040
We<00:02:17.440> have<00:02:17.600> some<00:02:17.760> scholarship<00:02:18.640> and<00:02:18.959> something<00:02:19.240> like<00:02:19.400> that.

00:02:20.040 --> 00:02:22.480
And<00:02:20.360> my<00:02:21.000> I<00:02:21.120> love<00:02:21.400> the<00:02:21.680> life<00:02:22.000> here.

00:02:22.480 --> 00:02:25.080
It's<00:02:22.720> very<00:02:23.560> I<00:02:23.640> use<00:02:23.840> It<00:02:24.000> is<00:02:24.160> amazing<00:02:24.720> here.

00:02:25.080 --> 00:02:31.760
I<00:02:25.160> would<00:02:25.360> say.<00:02:25.880> And<00:02:26.400> we<00:02:26.520> have<00:02:26.680> amazing<00:02:27.200> team<00:02:28.040> in<00:02:28.240> the<00:02:28.360> research<00:02:29.400> and<00:02:29.760> in<00:02:29.920> the<00:02:30.160> administrative<00:02:31.080> work.

00:02:31.760 --> 00:02:37.080
Yeah,<00:02:31.959> I<00:02:32.440> love<00:02:32.760> it<00:02:32.959> working<00:02:33.320> here,<00:02:33.800> especially<00:02:34.400> with<00:02:34.920> very<00:02:35.200> nice<00:02:35.920> colleagues<00:02:36.400> in<00:02:36.560> here.

00:02:37.080 --> 00:02:40.640
That's<00:02:37.280> great.<00:02:37.720> Let's<00:02:37.959> dive<00:02:38.280> into<00:02:39.480> the<00:02:39.680> research.

00:02:40.640 --> 00:02:45.920
So,<00:02:40.880> also,<00:02:41.200> why<00:02:41.280> don't<00:02:41.440> you<00:02:41.520> tell<00:02:41.680> people<00:02:42.000> what<00:02:42.200> you<00:02:42.320> typically<00:02:42.800> teach<00:02:43.600> and<00:02:43.760> then<00:02:43.920> also<00:02:44.320> what<00:02:44.480> you<00:02:44.600> do<00:02:44.680> on<00:02:44.800> the<00:02:44.880> research<00:02:45.280> side?

00:02:45.920 --> 00:02:51.440
All<00:02:45.959> right.<00:02:46.240> Yeah,<00:02:46.520> my<00:02:47.400> teaching<00:02:47.880> and<00:02:48.080> research,<00:02:48.480> I<00:02:48.600> would<00:02:48.760> say<00:02:48.920> they<00:02:49.040> are<00:02:49.160> very<00:02:49.440> correlated<00:02:50.400> in<00:02:50.480> the<00:02:50.600> topics.

00:02:51.440 --> 00:02:53.800
I<00:02:51.920> Right<00:02:52.160> now,<00:02:52.360> I<00:02:52.480> teach<00:02:52.880> two<00:02:53.080> courses.

00:02:53.800 --> 00:03:01.880
One<00:02:54.040> is<00:02:54.280> algorithm<00:02:54.760> design<00:02:55.560> to<00:02:55.760> teach<00:02:55.959> your<00:02:56.040> students<00:02:56.480> how<00:02:56.640> to<00:02:56.840> do<00:02:57.120> design<00:02:57.600> algorithm<00:02:58.200> for<00:02:58.440> specific<00:02:58.959> problem,<00:02:59.800> how<00:02:59.959> to<00:03:00.120> do<00:03:00.280> it<00:03:00.400> fast<00:03:00.880> and<00:03:01.000> efficient.

00:03:01.880 --> 00:03:05.040
And<00:03:02.160> the<00:03:02.239> other<00:03:02.440> course<00:03:02.680> I'm<00:03:02.840> teaching<00:03:03.160> now<00:03:03.480> is<00:03:03.720> applied<00:03:04.200> deep<00:03:04.400> learning.

00:03:05.040 --> 00:03:13.000
And<00:03:05.200> in<00:03:05.320> how<00:03:05.560> do<00:03:05.680> you<00:03:05.800> apply<00:03:06.280> your<00:03:06.920> the<00:03:07.400> very<00:03:07.880> fast<00:03:08.360> developing<00:03:09.400> deep<00:03:09.600> learning<00:03:09.840> technologies<00:03:10.600> and<00:03:10.720> models<00:03:11.239> into<00:03:11.720> your<00:03:11.920> real<00:03:12.160> problems.

00:03:13.000 --> 00:03:18.840
And<00:03:13.480> also<00:03:14.000> in<00:03:14.200> the<00:03:14.320> research<00:03:14.760> part,<00:03:15.560> I'm<00:03:15.720> also<00:03:16.080> using<00:03:16.600> this<00:03:16.800> kind<00:03:17.000> of<00:03:17.040> deep<00:03:17.239> learning<00:03:17.600> or<00:03:17.720> we<00:03:17.880> call<00:03:18.120> it<00:03:18.200> AI.

00:03:18.840 --> 00:03:23.160
People<00:03:19.120> are<00:03:19.280> now<00:03:19.600> referring<00:03:20.000> deep<00:03:20.239> learning<00:03:20.480> as<00:03:20.640> basically<00:03:21.440> they're<00:03:21.600> two<00:03:21.800> different<00:03:22.160> terms,<00:03:22.480> actually.

00:03:23.160 --> 00:03:31.560
I'm<00:03:23.239> using<00:03:23.519> this<00:03:23.680> deep<00:03:23.920> learning<00:03:24.160> models<00:03:24.959> to<00:03:25.320> solve<00:03:25.959> real-world<00:03:26.440> problems,<00:03:27.360> especially<00:03:28.080> the<00:03:28.239> problem<00:03:28.840> that<00:03:29.560> help<00:03:29.840> people<00:03:30.640> every<00:03:30.959> day.

00:03:31.560 --> 00:03:38.360
It's<00:03:31.880> for<00:03:32.000> example,<00:03:32.519> the<00:03:33.000> the<00:03:33.120> major<00:03:33.400> part<00:03:33.680> I'm<00:03:33.840> doing<00:03:34.080> is<00:03:34.239> a<00:03:34.320> since<00:03:34.760> we<00:03:34.959> call<00:03:35.200> it<00:03:35.320> is<00:03:35.440> a<00:03:35.519> term<00:03:35.760> called<00:03:36.000> artificial<00:03:36.519> intelligence<00:03:37.239> of<00:03:37.480> things.

00:03:38.360 --> 00:03:43.440
I<00:03:38.519> want<00:03:38.840> to<00:03:39.239> make<00:03:39.680> everything<00:03:40.720> intelligent<00:03:41.920> that<00:03:42.080> is<00:03:42.200> powered<00:03:42.519> by<00:03:42.959> AI.

00:03:43.440 --> 00:03:48.480
So,<00:03:43.600> in<00:03:43.760> that<00:03:43.959> case,<00:03:44.519> then<00:03:44.800> you<00:03:44.920> can<00:03:45.200> enable<00:03:45.760> a<00:03:45.880> lot<00:03:46.360> of<00:03:46.519> different<00:03:46.880> applications,<00:03:48.000> right?

00:03:48.480 --> 00:03:53.760
That's<00:03:48.800> my<00:03:49.040> like<00:03:49.320> overall<00:03:49.920> of<00:03:50.040> the<00:03:50.160> long-term<00:03:50.720> research<00:03:51.400> objective<00:03:52.400> in<00:03:52.600> my<00:03:53.000> career.

00:03:53.760 --> 00:03:58.440
So<00:03:53.840> now<00:03:54.120> let's<00:03:54.360> go<00:03:54.760> a<00:03:54.880> little<00:03:55.120> bit<00:03:55.560> deeper<00:03:56.360> into<00:03:57.480> the<00:03:57.600> wearables.

00:03:58.440 --> 00:04:00.680
A-<00:03:58.680> I<00:03:58.800> have<00:03:58.960> an<00:03:59.080> Apple<00:03:59.320> Watch<00:03:59.600> charging<00:04:00.000> over<00:04:00.160> there.

00:04:00.680 --> 00:04:04.000
This<00:04:00.760> is<00:04:00.800> when<00:04:00.920> I'm<00:04:01.240> when<00:04:01.400> I'm<00:04:01.520> sitting,<00:04:02.040> there's<00:04:02.240> not<00:04:02.400> really<00:04:02.640> a<00:04:02.680> use<00:04:02.880> for<00:04:03.000> me<00:04:03.280> to<00:04:03.360> use<00:04:03.560> it.

00:04:04.000 --> 00:04:10.400
So<00:04:04.160> she's<00:04:04.320> charging.<00:04:05.200> Yeah,<00:04:05.400> tell<00:04:05.600> us<00:04:05.680> a<00:04:05.720> little<00:04:05.840> bit<00:04:06.000> more<00:04:06.280> about<00:04:07.160> the<00:04:07.280> research<00:04:07.840> that<00:04:08.400> you're<00:04:08.480> really<00:04:08.720> trying<00:04:09.000> to<00:04:09.080> save<00:04:09.320> lives,<00:04:09.760> right?

00:04:10.400 --> 00:04:13.160
Yeah,<00:04:10.640> I<00:04:10.760> try<00:04:10.959> I'm<00:04:11.120> trying<00:04:11.400> to<00:04:11.720> I<00:04:11.840> hope<00:04:12.080> I<00:04:12.160> can<00:04:12.320> succeed.

00:04:13.160 --> 00:04:18.320
Yeah,<00:04:13.400> and<00:04:13.720> okay,<00:04:13.959> let's<00:04:14.480> I'm<00:04:15.160> let's<00:04:15.360> discuss<00:04:15.760> something<00:04:16.160> about<00:04:16.560> the<00:04:16.720> project<00:04:17.120> I'm<00:04:17.239> doing<00:04:17.480> right<00:04:17.720> now.

00:04:18.320 --> 00:04:24.919
It's<00:04:18.560> a<00:04:18.640> heart<00:04:18.959> monitoring<00:04:19.799> project.<00:04:20.680> I<00:04:20.760> want<00:04:21.320> from<00:04:21.600> the<00:04:21.680> scratch<00:04:22.360> why<00:04:22.680> we<00:04:22.840> did<00:04:23.120> this<00:04:23.440> from<00:04:23.760> the<00:04:23.919> very<00:04:24.160> beginning.

00:04:24.919 --> 00:04:29.480
And<00:04:25.680> right<00:04:25.960> now,<00:04:26.640> people<00:04:27.040> do<00:04:27.200> you<00:04:27.240> know<00:04:27.400> what<00:04:27.560> is<00:04:27.640> the<00:04:27.720> most<00:04:28.000> deadly<00:04:28.440> disease,<00:04:29.040> right?

00:04:29.480 --> 00:04:32.480
Some<00:04:29.640> people<00:04:29.919> may<00:04:30.080> not<00:04:30.760> cancer,<00:04:31.760> right?

00:04:32.480 --> 00:04:37.960
But<00:04:32.919> turns<00:04:33.200> out<00:04:33.320> it's<00:04:33.480> not.<00:04:34.240> The<00:04:34.360> heart<00:04:34.800> disease<00:04:35.360> are<00:04:35.480> number<00:04:35.800> one<00:04:36.000> killers<00:04:36.800> across<00:04:37.320> the<00:04:37.440> world.

00:04:37.960 --> 00:04:43.440
For<00:04:38.080> example,<00:04:38.440> in<00:04:38.680> the<00:04:38.720> last<00:04:38.960> year,<00:04:39.120> if<00:04:39.320> I<00:04:39.400> remember<00:04:39.760> correctly,<00:04:40.200> that<00:04:40.520> 20<00:04:40.880> million<00:04:41.280> people<00:04:41.560> would<00:04:41.680> die<00:04:42.320> from<00:04:42.640> heart<00:04:42.800> disease.

00:04:43.440 --> 00:04:47.160
And<00:04:43.560> in<00:04:43.680> the<00:04:43.800> US,<00:04:44.440> it's<00:04:44.600> about<00:04:45.000> 300,000.

00:04:47.160 --> 00:04:50.160
That<00:04:47.360> is<00:04:47.520> more<00:04:47.760> than<00:04:48.000> the<00:04:48.400> people<00:04:48.640> died<00:04:48.919> from<00:04:49.440> cancer.

00:04:50.160 --> 00:04:59.040
And<00:04:50.360> also<00:04:50.600> it<00:04:50.720> turns<00:04:51.000> out<00:04:51.240> that<00:04:51.760> the<00:04:51.880> heart<00:04:52.120> disease,<00:04:53.040> the<00:04:53.160> reason<00:04:53.560> they<00:04:53.960> most<00:04:54.240> people<00:04:55.040> have<00:04:55.160> this<00:04:55.360> problem,<00:04:55.880> the<00:04:56.040> high<00:04:56.480> degree<00:04:56.840> is<00:04:57.040> because<00:04:57.720> it's<00:04:57.960> happening<00:04:58.480> silent

00:04:59.040 --> 00:05:07.360
silently<00:04:59.720> every<00:05:00.000> day.<00:05:00.600> So<00:05:01.240> when<00:05:01.360> you<00:05:01.480> have<00:05:01.720> a<00:05:01.800> heart<00:05:02.080> problem,<00:05:02.760> you<00:05:02.880> have<00:05:03.080> to<00:05:03.560> when<00:05:03.680> you<00:05:03.800> feel<00:05:04.120> it,<00:05:04.440> it's<00:05:04.919> most<00:05:05.560> of<00:05:05.640> the<00:05:05.760> time<00:05:06.400> it's<00:05:06.560> too<00:05:06.760> late.

00:05:07.360 --> 00:05:12.000
And<00:05:08.000> we<00:05:08.160> want<00:05:08.400> to<00:05:08.480> do<00:05:08.720> this<00:05:09.080> because<00:05:09.640> we<00:05:09.840> can<00:05:10.200> help<00:05:10.680> with<00:05:10.919> some<00:05:11.120> wearables.

00:05:12.000 --> 00:05:20.160
And<00:05:12.320> we<00:05:12.520> the<00:05:12.680> sensors<00:05:13.120> can<00:05:13.320> detect<00:05:13.960> what<00:05:14.120> is<00:05:14.240> your<00:05:14.480> heart<00:05:14.720> is<00:05:14.960> doing<00:05:15.320> now,<00:05:16.120> and<00:05:16.600> they<00:05:16.680> is<00:05:16.800> doing<00:05:17.120> correctly,<00:05:17.680> is<00:05:17.880> any<00:05:18.640> slightly<00:05:19.160> degradation<00:05:19.880> of<00:05:20.040> the

00:05:20.160 --> 00:05:23.760
performance<00:05:20.680> of<00:05:20.880> the<00:05:21.000> heart<00:05:21.600> activity.<00:05:22.480> This<00:05:22.680> can<00:05:22.840> be<00:05:22.960> monitored.

00:05:23.760 --> 00:05:27.600
But<00:05:23.919> people<00:05:24.400> would<00:05:24.600> just<00:05:25.160> because<00:05:25.400> there's<00:05:25.600> no<00:05:25.760> symptom<00:05:26.280> for<00:05:26.400> most<00:05:26.640> of<00:05:26.720> the<00:05:26.800> time.

00:05:27.600 --> 00:05:33.080
So<00:05:28.360> it's<00:05:28.600> very<00:05:28.840> hard<00:05:29.440> for<00:05:29.600> us<00:05:29.840> to<00:05:30.080> notice<00:05:30.520> all<00:05:30.640> these<00:05:30.880> are<00:05:31.000> change<00:05:31.400> there<00:05:31.640> is<00:05:31.840> something<00:05:32.160> happening<00:05:32.480> there.

00:05:33.080 --> 00:05:37.720
And<00:05:33.800> and<00:05:33.960> turns<00:05:34.200> out<00:05:34.400> well,<00:05:34.600> the<00:05:34.960> wearables<00:05:35.880> and<00:05:35.960> the<00:05:36.000> mobile<00:05:36.320> devices<00:05:36.960> can<00:05:37.160> help.

00:05:37.720 --> 00:05:40.160
It's<00:05:37.919> a<00:05:37.960> perfect<00:05:38.440> fit<00:05:38.960> for<00:05:39.120> this<00:05:39.360> scenario.

00:05:40.160 --> 00:05:48.560
That's<00:05:40.400> the<00:05:40.600> primary<00:05:41.160> reason<00:05:41.600> we<00:05:41.720> jump<00:05:42.080> into<00:05:42.440> the<00:05:42.800> this<00:05:43.040> area<00:05:43.520> and<00:05:43.680> start<00:05:43.960> doing<00:05:44.200> something<00:05:44.560> we<00:05:44.680> believe<00:05:45.080> is<00:05:45.760> And<00:05:45.960> then<00:05:46.040> from<00:05:46.280> there<00:05:46.480> we<00:05:46.600> start<00:05:46.880> from<00:05:47.200> very<00:05:47.520> basic<00:05:48.200> basic

00:05:48.560 --> 00:05:57.200
things<00:05:49.120> and<00:05:49.400> move<00:05:49.720> to<00:05:49.840> the<00:05:49.960> future.<00:05:50.360> We<00:05:50.680> would<00:05:51.160> envision<00:05:51.680> that<00:05:51.920> we<00:05:52.040> want<00:05:52.400> this<00:05:53.040> build<00:05:53.240> a<00:05:53.280> platform<00:05:54.200> for<00:05:54.360> everybody<00:05:55.160> running<00:05:55.480> on<00:05:55.600> your<00:05:55.680> mobile<00:05:56.000> device<00:05:56.800> and

00:05:57.200 --> 00:06:06.160
connecting<00:05:57.640> data<00:05:58.320> using<00:05:58.600> sensors<00:05:59.360> every<00:05:59.600> day<00:06:00.000> and<00:06:00.160> the<00:06:00.240> monitor<00:06:00.600> what<00:06:00.760> the<00:06:00.880> heart<00:06:01.320> is<00:06:01.440> doing<00:06:01.680> now<00:06:02.200> and<00:06:03.000> give<00:06:03.200> you<00:06:03.320> some<00:06:03.520> feedback,<00:06:04.360> give<00:06:04.560> you<00:06:04.640> some<00:06:05.120> warning,<00:06:06.000> give

00:06:06.160 --> 00:06:09.040
you<00:06:06.280> some<00:06:06.520> analysis<00:06:07.080> if<00:06:07.280> hey,<00:06:07.480> is<00:06:07.720> there<00:06:07.880> there's<00:06:08.120> a<00:06:08.600> high<00:06:08.760> risk.

00:06:09.040 --> 00:06:11.880
We<00:06:09.120> believe<00:06:09.440> there's<00:06:09.640> a<00:06:09.680> high<00:06:09.840> risk,<00:06:10.080> you<00:06:10.240> need<00:06:10.400> to<00:06:10.520> see<00:06:10.640> some<00:06:10.840> doctor,<00:06:11.360> something<00:06:11.640> like<00:06:11.800> that.

00:06:11.880 --> 00:06:19.919
That's<00:06:12.040> great.<00:06:12.240> I<00:06:12.320> actually<00:06:12.680> knew<00:06:13.160> that<00:06:13.400> was<00:06:13.600> number<00:06:14.000> one<00:06:14.280> that<00:06:14.400> heart<00:06:14.640> disease<00:06:15.040> was<00:06:15.280> number<00:06:15.560> one<00:06:16.040> be-<00:06:16.280> only<00:06:16.560> because<00:06:17.520> my<00:06:17.680> brother<00:06:18.080> is<00:06:18.200> actually<00:06:18.520> a<00:06:18.919> spinal<00:06:19.360> surgeon,

00:06:19.919 --> 00:06:28.400
super<00:06:20.200> random,<00:06:20.560> but<00:06:21.120> and<00:06:21.480> there's<00:06:21.760> a<00:06:21.840> book<00:06:22.360> that<00:06:22.520> was<00:06:22.640> going<00:06:22.880> around<00:06:23.440> called<00:06:23.919> Outlive,<00:06:24.520> The<00:06:24.640> Science<00:06:25.080> and<00:06:25.200> Art<00:06:25.480> of<00:06:26.000> Longevity<00:06:27.200> and<00:06:27.360> they<00:06:27.440> talk<00:06:27.640> about<00:06:27.840> the<00:06:27.960> four

00:06:28.400 --> 00:06:32.720
horsemen<00:06:29.280> of<00:06:29.480> disease.<00:06:30.360> Number<00:06:30.640> one<00:06:31.000> was<00:06:31.840> heart<00:06:32.040> disease.

00:06:32.720 --> 00:06:40.160
So,<00:06:33.200> it<00:06:33.240> was<00:06:33.360> pretty<00:06:33.520> fascinating.<00:06:33.960> Highly<00:06:34.200> recommend<00:06:34.560> the<00:06:34.640> book<00:06:35.120> if<00:06:35.320> you<00:06:35.440> want<00:06:35.560> to<00:06:35.640> live<00:06:35.840> longer<00:06:36.680> and<00:06:37.160> I'm<00:06:37.400> even<00:06:37.720> I'm<00:06:37.880> like<00:06:38.120> almost<00:06:38.440> entirely<00:06:38.960> on<00:06:39.080> a<00:06:39.160> plant-based<00:06:39.680> diet.

00:06:40.160 --> 00:06:47.200
Okay.<00:06:40.800> So,<00:06:41.160> heart<00:06:41.400> disease<00:06:41.880> number<00:06:42.160> one,<00:06:42.840> we've<00:06:42.960> got<00:06:43.560> wearables<00:06:44.960> and<00:06:45.919> AI<00:06:46.200> calling<00:06:46.560> it<00:06:46.960> AI.

00:06:47.200 --> 00:06:49.240
Did<00:06:47.320> I<00:06:47.360> get<00:06:47.480> that<00:06:47.600> right?<00:06:48.040> Perfectly.<00:06:48.800> Perfect.

00:06:49.240 --> 00:06:57.680
Adrian,<00:06:49.560> I'd<00:06:49.640> love<00:06:49.800> to<00:06:49.880> get<00:06:50.200> your<00:06:50.360> perspective<00:06:51.200> on<00:06:51.480> how<00:06:52.360> Dell<00:06:52.760> is<00:06:52.960> partnering<00:06:54.280> with<00:06:54.600> Pitt<00:06:55.280> and<00:06:55.560> other<00:06:55.800> universities<00:06:57.160> to<00:06:57.400> really

00:06:57.680 --> 00:07:04.760
help<00:06:58.280> accelerate<00:06:59.160> and<00:06:59.320> amplify<00:07:00.040> and<00:07:00.200> drive<00:07:01.400> the<00:07:01.520> missions<00:07:02.000> forward<00:07:02.440> in<00:07:02.520> this<00:07:02.720> case<00:07:03.640> on<00:07:03.840> the<00:07:04.080> AI<00:07:04.280> front.

00:07:04.760 --> 00:07:11.960
Hi<00:07:05.000> everybody,<00:07:05.400> my<00:07:05.520> name<00:07:05.720> is<00:07:05.880> Adrian<00:07:06.160> Garber.<00:07:06.560> I'm<00:07:06.760> the<00:07:06.919> Chief<00:07:07.160> Technology<00:07:07.760> and<00:07:07.880> Innovation<00:07:08.320> Strategist<00:07:09.040> for<00:07:09.320> Higher<00:07:09.600> Education<00:07:10.480> at<00:07:10.720> Dell<00:07:10.880> Technologies.

00:07:11.960 --> 00:07:14.520
I'm<00:07:12.160> part<00:07:12.360> of<00:07:12.480> our<00:07:12.720> public<00:07:13.080> sector<00:07:13.400> strategy<00:07:13.960> group.

00:07:14.520 --> 00:07:23.560
In<00:07:14.640> this<00:07:15.000> project,<00:07:15.520> the<00:07:15.600> genesis<00:07:16.080> of<00:07:16.240> it,<00:07:16.720> which<00:07:16.840> is<00:07:17.280> why<00:07:17.440> Dell<00:07:17.680> tells<00:07:17.919> to<00:07:18.040> your<00:07:18.160> question<00:07:18.560> Joe,<00:07:19.000> is<00:07:19.800> it<00:07:20.000> was<00:07:20.160> an<00:07:20.280> initiative<00:07:20.960> from<00:07:21.520> our<00:07:22.120> higher<00:07:22.400> education<00:07:23.000> strategy

00:07:23.560 --> 00:07:30.240
team<00:07:24.280> to<00:07:24.440> create<00:07:24.720> a<00:07:24.800> GB10<00:07:25.520> acceleration<00:07:26.240> pilot<00:07:26.680> program<00:07:27.320> with<00:07:27.640> our<00:07:27.840> higher<00:07:28.160> education<00:07:28.760> CIO<00:07:29.120> advisory<00:07:29.640> board.

00:07:30.240 --> 00:07:38.720
So,<00:07:30.440> we<00:07:30.560> run<00:07:30.760> a<00:07:30.800> board,<00:07:31.240> there's<00:07:31.400> about<00:07:31.720> 30<00:07:32.040> CIOs<00:07:32.760> from<00:07:32.919> across<00:07:33.280> the<00:07:33.360> United<00:07:33.760> States<00:07:34.040> and<00:07:34.160> Canada<00:07:34.600> that<00:07:34.800> meet<00:07:34.960> with<00:07:35.120> us<00:07:35.320> on<00:07:35.440> a<00:07:35.480> quarterly<00:07:35.960> basis<00:07:36.800> and<00:07:37.000> we<00:07:37.360> have<00:07:37.800> presentations

00:07:38.720 --> 00:07:45.840
and<00:07:39.080> subject<00:07:39.440> matter<00:07:39.680> experts<00:07:40.200> come<00:07:40.440> in<00:07:40.600> and<00:07:40.760> run<00:07:40.919> feedback<00:07:41.360> sessions<00:07:41.840> and<00:07:42.000> part<00:07:42.200> of<00:07:42.640> the<00:07:42.840> feedback<00:07:43.160> that<00:07:43.280> they<00:07:43.440> gave<00:07:43.680> us<00:07:43.800> was<00:07:43.960> they<00:07:44.120> really<00:07:44.400> wanted<00:07:44.760> to<00:07:44.880> spend<00:07:45.640> some

00:07:45.840 --> 00:07:53.920
time<00:07:46.080> with<00:07:46.240> us<00:07:46.360> discussing<00:07:47.160> new<00:07:47.400> and<00:07:47.560> novel<00:07:47.960> things,<00:07:48.400> whether<00:07:48.680> it<00:07:48.760> was<00:07:48.880> a<00:07:48.960> piece<00:07:49.200> of<00:07:49.320> hardware<00:07:49.640> that<00:07:49.800> was<00:07:49.920> coming<00:07:50.320> out,<00:07:50.680> whether<00:07:51.000> it<00:07:51.120> was<00:07:51.640> a<00:07:51.760> new<00:07:52.160> model<00:07:52.560> or<00:07:52.680> a<00:07:52.720> new<00:07:52.920> platform.

00:07:53.920 --> 00:07:57.760
And<00:07:54.680> in<00:07:54.800> order<00:07:55.000> to<00:07:55.120> do<00:07:55.280> that,<00:07:55.480> we<00:07:55.600> had<00:07:55.800> to<00:07:55.880> get<00:07:56.080> devices<00:07:56.560> into<00:07:56.840> their<00:07:57.000> hands.

00:07:57.760 --> 00:08:05.840
And<00:07:58.280> so<00:07:58.440> through<00:07:58.680> that<00:07:58.880> CIO<00:07:59.160> advisory<00:07:59.560> board,<00:07:59.800> Mark<00:08:00.000> Henderson,<00:08:00.600> who's<00:08:00.840> the<00:08:00.920> CIO<00:08:01.360> of<00:08:01.480> University<00:08:01.960> of<00:08:02.080> Pittsburgh,<00:08:02.880> was<00:08:03.080> able<00:08:03.320> to<00:08:03.480> help<00:08:03.720> direct<00:08:04.200> us<00:08:04.440> to<00:08:04.840> Pengfei's<00:08:05.400> research

00:08:05.840 --> 00:08:09.200
group<00:08:06.200> through<00:08:06.840> Matt<00:08:07.400> and<00:08:07.800> Adam<00:08:08.160> and<00:08:08.320> others<00:08:08.640> on<00:08:08.760> the<00:08:08.880> IT.

00:08:09.200 --> 00:08:13.840
So<00:08:09.360> we<00:08:09.480> said,<00:08:09.720> "You<00:08:10.040> know<00:08:10.120> your<00:08:10.360> audience<00:08:10.880> and<00:08:11.000> your<00:08:11.120> research<00:08:11.600> teams<00:08:11.880> and<00:08:12.000> your<00:08:12.160> PIs<00:08:12.640> better<00:08:12.880> than<00:08:13.120> we<00:08:13.240> do.

00:08:13.840 --> 00:08:20.400
Here's<00:08:14.080> the<00:08:14.160> device,<00:08:14.560> here's<00:08:14.800> how<00:08:14.919> we<00:08:15.080> think<00:08:15.400> they<00:08:15.520> might<00:08:15.800> use<00:08:16.040> it,<00:08:16.160> here's<00:08:16.400> some<00:08:16.800> some<00:08:17.000> early<00:08:17.240> guidelines<00:08:17.760> and<00:08:17.880> constraints,<00:08:18.880> along<00:08:19.200> with<00:08:19.360> Nvidia<00:08:19.800> who's<00:08:20.040> partnered

00:08:20.400 --> 00:08:28.320
with<00:08:20.560> us<00:08:20.720> on<00:08:20.800> this<00:08:20.960> project."<00:08:21.800> And<00:08:21.919> then<00:08:22.600> through<00:08:22.960> the<00:08:23.160> IT<00:08:23.320> department,<00:08:24.040> they<00:08:24.200> were<00:08:24.360> helping<00:08:24.800> us<00:08:25.440> determine<00:08:26.080> what<00:08:26.280> were<00:08:26.360> the<00:08:26.480> best<00:08:26.800> use<00:08:26.960> cases<00:08:27.360> and<00:08:27.480> opportunities<00:08:28.200> to

00:08:28.320 --> 00:08:30.240
try<00:08:28.600> this<00:08:28.840> new<00:08:29.080> and<00:08:29.160> experimental<00:08:29.919> thing.

00:08:30.240 --> 00:08:37.520
So<00:08:30.360> that's<00:08:30.600> how<00:08:30.800> we<00:08:31.000> found<00:08:31.400> Pengfei.<00:08:32.240> Personally,<00:08:32.719> like<00:08:32.919> how<00:08:33.000> you<00:08:33.159> have<00:08:33.320> a<00:08:33.360> personal<00:08:33.840> anecdote,<00:08:34.680> my<00:08:34.840> mother<00:08:35.159> has<00:08:35.320> been<00:08:35.560> a<00:08:35.640> heart<00:08:35.880> patient<00:08:36.280> for<00:08:36.400> the<00:08:36.479> last<00:08:36.800> three<00:08:37.000> decades

00:08:37.520 --> 00:08:46.200
of<00:08:37.640> my<00:08:37.800> life.<00:08:38.280> So<00:08:38.479> because<00:08:38.880> of<00:08:39.039> that,<00:08:39.680> when<00:08:39.880> I<00:08:39.960> heard<00:08:40.200> about<00:08:40.560> the<00:08:40.760> cross<00:08:41.719> multimodal<00:08:42.479> approach<00:08:43.120> of<00:08:43.520> it's<00:08:43.680> wearable<00:08:44.000> technology,<00:08:44.800> it's<00:08:45.160> for<00:08:45.400> heart<00:08:45.680> patients,

00:08:46.200 --> 00:08:53.600
it's<00:08:46.400> medical<00:08:46.880> records,<00:08:47.640> it's<00:08:48.240> real-time<00:08:48.800> live<00:08:49.040> data<00:08:49.320> processing<00:08:50.400> using<00:08:50.680> a<00:08:50.760> device<00:08:51.240> that's<00:08:51.600> localized,<00:08:52.280> that's<00:08:52.480> how<00:08:52.640> the<00:08:52.760> GB10<00:08:53.240> works.

00:08:53.600 --> 00:09:01.920
I<00:08:53.920> thought<00:08:54.360> this<00:08:54.560> is<00:08:55.160> one<00:08:55.360> of<00:08:55.400> those<00:08:55.720> sweet<00:08:56.080> spots<00:08:56.560> where<00:08:56.760> all<00:08:57.160> things<00:08:57.520> have<00:08:57.760> collaborated<00:08:58.560> together<00:08:59.040> to<00:08:59.240> be<00:08:59.920> maybe<00:09:00.280> new<00:09:00.680> lessons<00:09:01.200> learned<00:09:01.520> for<00:09:01.680> other

00:09:01.920 --> 00:09:07.320
researchers.<00:09:02.680> And<00:09:02.960> shout<00:09:03.200> out<00:09:03.360> to<00:09:03.480> UPMC,<00:09:04.240> I<00:09:04.360> really<00:09:04.640> appreciate<00:09:05.240> the<00:09:05.360> Pitt<00:09:05.680> UPMC<00:09:06.320> partnership.

00:09:07.320 --> 00:09:11.560
In<00:09:07.440> Pittsburgh,<00:09:07.839> it's<00:09:08.000> very<00:09:08.240> important,<00:09:08.880> health<00:09:09.080> care<00:09:09.320> is<00:09:09.520> one<00:09:09.720> of<00:09:09.800> the<00:09:09.920> major<00:09:10.200> industries<00:09:10.680> in<00:09:10.800> the<00:09:10.880> city.

00:09:11.560 --> 00:09:18.640
So<00:09:11.720> seeing<00:09:12.080> a<00:09:12.160> use<00:09:12.440> case<00:09:12.760> where<00:09:13.080> a<00:09:13.120> new<00:09:13.320> technology<00:09:13.880> from<00:09:14.120> Dell<00:09:14.480> is<00:09:14.680> partnered<00:09:15.120> with<00:09:15.720> research<00:09:16.240> that's<00:09:16.480> connected<00:09:16.920> to<00:09:17.000> health<00:09:17.280> care,<00:09:17.880> I<00:09:17.960> don't<00:09:18.120> think<00:09:18.280> we<00:09:18.400> could<00:09:18.520> have

00:09:18.640 --> 00:09:22.600
picked<00:09:18.880> something<00:09:19.240> better<00:09:19.520> for<00:09:19.720> us<00:09:19.839> to<00:09:20.000> spend<00:09:20.320> our<00:09:20.640> acceleration<00:09:21.280> pilot<00:09:21.839> time<00:09:22.120> on.

00:09:22.600 --> 00:09:31.760
That<00:09:22.720> was<00:09:22.880> fantastic.<00:09:23.520> So,<00:09:24.400> Pengfei,<00:09:24.839> I'd<00:09:24.960> love<00:09:25.120> to<00:09:25.240> get<00:09:25.960> I'd<00:09:26.080> love<00:09:26.280> to<00:09:26.440> get<00:09:26.800> the<00:09:27.600> Here<00:09:27.760> we<00:09:27.920> are<00:09:28.040> in<00:09:28.120> 2026,<00:09:29.720> where<00:09:29.880> do<00:09:29.960> you<00:09:30.120> see<00:09:30.320> this<00:09:30.560> going,<00:09:31.320> right?

00:09:31.760 --> 00:09:36.680
In<00:09:31.880> the<00:09:31.960> next,<00:09:32.560> let's<00:09:32.720> call<00:09:32.960> it<00:09:33.200> maybe<00:09:33.640> 6<00:09:34.000> to<00:09:34.160> 18<00:09:34.640> months,<00:09:35.040> like<00:09:35.320> where<00:09:35.440> do<00:09:35.520> you<00:09:35.640> want<00:09:35.760> to<00:09:35.839> take<00:09:36.120> this?

00:09:36.680 --> 00:09:45.840
All<00:09:36.800> right.<00:09:37.360> My<00:09:37.560> envision<00:09:38.320> is<00:09:38.560> that<00:09:39.200> with<00:09:39.760> uh<00:09:40.160> development<00:09:40.800> of<00:09:41.000> AI<00:09:41.640> as<00:09:41.840> well<00:09:42.080> as<00:09:42.360> the<00:09:42.920> platform<00:09:43.760> I<00:09:43.840> was<00:09:44.000> hard<00:09:44.240> of<00:09:44.520> hardware<00:09:44.920> platform,

00:09:45.840 --> 00:09:54.680
I<00:09:46.040> you<00:09:46.160> would<00:09:46.360> envision<00:09:46.880> that<00:09:47.160> in<00:09:47.320> the<00:09:47.680> within<00:09:48.000> next<00:09:48.480> 5<00:09:48.800> years,<00:09:49.200> about<00:09:49.560> 6<00:09:49.920> 60<00:09:50.200> months,<00:09:50.920> we<00:09:51.120> will<00:09:51.320> have<00:09:51.520> an<00:09:51.680> initial<00:09:52.440> platform<00:09:53.480> we<00:09:53.760> are<00:09:54.280> trying

00:09:54.680 --> 00:10:03.360
to<00:09:54.760> build<00:09:55.040> today.<00:09:55.680> That<00:09:55.880> research<00:09:56.280> is<00:09:56.480> like<00:09:56.880> there's<00:09:57.400> so<00:09:57.560> many<00:09:57.800> answer<00:09:58.120> ahead,<00:09:58.640> but<00:09:58.880> I<00:09:58.960> would<00:09:59.120> say<00:09:59.920> the<00:10:00.040> thing<00:10:00.320> is<00:10:00.800> that<00:10:01.560> we<00:10:01.760> can<00:10:01.960> definitely<00:10:02.320> build<00:10:02.600> a<00:10:02.680> platform

00:10:03.360 --> 00:10:12.440
to<00:10:03.720> monitor<00:10:04.200> that.<00:10:04.840> And<00:10:05.440> we<00:10:05.600> want<00:10:05.880> to<00:10:06.040> push<00:10:06.920> our<00:10:07.120> boundary<00:10:07.680> as<00:10:07.920> much<00:10:08.280> as<00:10:08.440> we<00:10:08.600> can,<00:10:08.840> meaning<00:10:09.200> we<00:10:09.360> want<00:10:09.720> to<00:10:10.320> make<00:10:10.920> as<00:10:11.920> more

00:10:12.440 --> 00:10:17.200
I<00:10:12.560> would<00:10:12.720> say<00:10:13.080> accurate<00:10:13.840> as<00:10:14.000> we<00:10:14.160> can,<00:10:14.840> more<00:10:15.200> adaptive<00:10:16.320> as<00:10:16.480> we<00:10:16.640> can.

00:10:17.200 --> 00:10:25.720
But<00:10:17.800> I'm<00:10:17.960> not<00:10:18.160> sure<00:10:18.600> where<00:10:19.000> how<00:10:19.120> much<00:10:19.320> we<00:10:19.400> can<00:10:19.560> get<00:10:19.760> it,<00:10:19.880> but<00:10:20.080> definitely<00:10:20.880> we<00:10:21.120> can<00:10:21.480> have<00:10:22.080> uh<00:10:22.120> for<00:10:22.280> example,<00:10:23.120> as<00:10:23.320> just<00:10:23.520> Andrew<00:10:23.840> just<00:10:24.280> uh<00:10:24.320> said,<00:10:24.720> we<00:10:24.920> are<00:10:25.440> guys

00:10:25.720 --> 00:10:33.160
and<00:10:25.880> putting<00:10:26.160> everything<00:10:26.560> together,<00:10:27.080> multi-modal<00:10:28.000> putting<00:10:28.240> everything<00:10:28.480> together,<00:10:28.840> so<00:10:28.920> real-time<00:10:29.400> sensor<00:10:29.720> data,<00:10:30.400> your<00:10:30.560> medical<00:10:30.960> record,<00:10:31.520> your<00:10:31.680> personal<00:10:32.080> information,

00:10:33.160 --> 00:10:40.880
all<00:10:33.360> these<00:10:33.560> things<00:10:33.760> together.<00:10:34.520> So,<00:10:34.920> we<00:10:35.000> are<00:10:35.080> confident<00:10:35.640> that<00:10:35.880> within<00:10:36.240> the<00:10:36.360> next<00:10:36.760> 3<00:10:36.920> to<00:10:37.040> 5<00:10:37.320> years<00:10:37.840> we<00:10:37.960> will<00:10:38.160> have<00:10:38.360> that<00:10:38.640> platform<00:10:39.520> running<00:10:39.880> on<00:10:40.000> your<00:10:40.120> mobile<00:10:40.480> phone.

00:10:40.880 --> 00:10:44.520
That's<00:10:41.080> great.<00:10:41.280> Can<00:10:41.440> you<00:10:41.520> talk<00:10:41.760> about<00:10:41.960> the<00:10:42.080> benefits<00:10:42.680> of<00:10:43.280> localization<00:10:44.000> of<00:10:44.080> this,<00:10:44.280> right?

00:10:44.520 --> 00:10:47.839
There's<00:10:44.720> a<00:10:44.760> lot<00:10:44.920> of<00:10:45.000> health<00:10:45.240> data,<00:10:45.920> there's<00:10:46.040> a<00:10:46.080> lot<00:10:46.200> of<00:10:46.280> privacy<00:10:46.760> data.

00:10:47.839 --> 00:10:50.760
Yes.<00:10:48.400> Storing<00:10:48.839> that<00:10:48.960> in<00:10:49.040> the<00:10:49.120> cloud<00:10:49.560> can<00:10:49.680> be<00:10:49.800> risky.

00:10:50.760 --> 00:10:55.240
Can<00:10:50.920> you<00:10:51.000> Can<00:10:51.160> you<00:10:51.240> talk<00:10:51.400> about<00:10:51.600> the<00:10:51.680> benefits<00:10:52.120> of<00:10:52.280> having<00:10:52.880> the<00:10:53.440> device<00:10:54.400> on<00:10:54.600> site?

00:10:55.240 --> 00:11:01.839
I<00:10:55.440> would<00:10:55.680> say<00:10:56.240> there<00:10:56.400> are<00:10:56.480> two<00:10:56.839> major<00:10:57.200> benefits<00:10:58.000> and<00:10:58.440> I<00:10:58.520> would<00:10:58.920> maybe<00:10:59.200> privacy<00:10:59.720> if<00:11:00.000> you<00:11:00.160> include<00:11:00.480> privacy<00:11:00.880> that'll<00:11:01.040> be<00:11:01.160> third<00:11:01.360> one.

00:11:01.839 --> 00:11:09.000
The<00:11:01.960> first<00:11:02.320> pro<00:11:02.640> benefit<00:11:03.440> is<00:11:03.680> that<00:11:04.400> you<00:11:04.520> don't<00:11:04.760> need<00:11:05.120> to<00:11:05.360> get<00:11:05.600> to<00:11:05.720> the<00:11:05.839> cloud<00:11:06.720> to<00:11:06.920> run<00:11:07.080> your<00:11:07.200> model,<00:11:07.520> which<00:11:07.800> is<00:11:07.920> very<00:11:08.240> important.

00:11:09.000 --> 00:11:13.839
People<00:11:09.280> think<00:11:09.560> that<00:11:09.960> connecting<00:11:10.400> cloud<00:11:10.760> is<00:11:11.440> okay,<00:11:11.720> just<00:11:11.920> pay<00:11:12.040> the<00:11:12.120> money<00:11:12.440> for<00:11:12.640> everything<00:11:12.920> that<00:11:13.000> you<00:11:13.120> save,<00:11:13.400> right?

00:11:13.839 --> 00:11:18.920
But<00:11:14.000> actually<00:11:14.320> it's<00:11:14.440> not<00:11:15.080> because<00:11:15.560> you<00:11:15.680> especially<00:11:16.160> for<00:11:16.360> this<00:11:16.640> like<00:11:16.880> time<00:11:17.200> sensitive<00:11:17.880> application.

00:11:18.920 --> 00:11:21.480
What<00:11:19.120> if<00:11:19.400> the<00:11:19.680> this<00:11:19.920> network<00:11:20.360> is<00:11:20.480> has<00:11:20.640> a<00:11:20.720> problem?

00:11:21.480 --> 00:11:24.000
What<00:11:21.680> if<00:11:21.839> the<00:11:21.920> data<00:11:22.280> has<00:11:22.600> something<00:11:23.000> wrong<00:11:23.200> with<00:11:23.360> there?

00:11:24.000 --> 00:11:32.680
And<00:11:24.520> if<00:11:24.720> you<00:11:25.000> And<00:11:25.560> the<00:11:25.680> cloud<00:11:26.040> is<00:11:26.200> handling<00:11:26.600> so<00:11:26.800> much<00:11:27.080> data<00:11:27.320> at<00:11:27.440> the<00:11:27.560> same<00:11:27.839> time,<00:11:28.720> then<00:11:29.520> you<00:11:29.760> it's<00:11:30.080> very<00:11:30.280> hard<00:11:30.560> for<00:11:30.720> them<00:11:31.040> to<00:11:31.400> tell<00:11:31.680> your<00:11:32.000> data

00:11:32.680 --> 00:11:41.800
and<00:11:33.200> put<00:11:33.320> that<00:11:33.600> into<00:11:33.960> your<00:11:34.080> application.<00:11:35.000> And<00:11:35.320> we<00:11:35.520> if<00:11:35.640> you<00:11:35.760> host<00:11:36.000> the<00:11:36.040> data<00:11:36.320> do<00:11:36.480> it<00:11:36.640> locally<00:11:37.240> is<00:11:37.480> fast,<00:11:38.240> very<00:11:38.640> efficient,<00:11:39.360> and<00:11:39.520> also<00:11:39.800> the<00:11:39.880> most<00:11:40.120> importantly<00:11:40.560> is<00:11:40.760> personalized.

00:11:41.800 --> 00:11:44.800
It's<00:11:42.080> running<00:11:42.400> only<00:11:42.600> for<00:11:42.840> you<00:11:43.040> and<00:11:43.360> running<00:11:43.640> based<00:11:43.920> on<00:11:44.080> your<00:11:44.240> data.

00:11:44.800 --> 00:11:52.520
And<00:11:45.120> this<00:11:45.280> is<00:11:45.480> a<00:11:45.560> kind<00:11:45.760> of<00:11:46.000> and<00:11:46.240> we<00:11:46.360> try<00:11:46.640> to<00:11:46.880> build<00:11:47.560> like<00:11:47.960> a<00:11:48.000> foundation<00:11:48.560> for<00:11:48.720> them,<00:11:49.320> which<00:11:49.560> is<00:11:49.680> like<00:11:49.800> some<00:11:50.080> put<00:11:50.280> some<00:11:50.440> common<00:11:50.720> knowledge<00:11:51.400> and<00:11:51.720> the<00:11:51.760> build<00:11:51.960> a<00:11:52.000> foundation

00:11:52.520 --> 00:12:00.600
of<00:11:52.640> the<00:11:52.800> application.<00:11:53.400> And<00:11:53.560> then<00:11:54.280> you<00:11:54.440> put<00:11:54.680> your<00:11:54.840> data<00:11:55.080> into<00:11:55.400> it<00:11:55.760> and<00:11:55.960> run<00:11:56.120> it<00:11:56.320> on<00:11:56.480> your<00:11:56.920> edge<00:11:57.160> device,<00:11:57.760> which<00:11:57.960> is<00:11:58.080> perfect<00:11:58.840> for<00:11:59.040> your<00:11:59.200> for<00:11:59.400> this<00:11:59.880> application.

00:12:00.600 --> 00:12:04.360
I<00:12:00.680> would<00:12:00.840> say<00:12:01.280> first<00:12:01.480> one<00:12:01.600> is<00:12:01.760> time<00:12:02.000> sensitive<00:12:02.680> and<00:12:02.920> the<00:12:03.040> other<00:12:03.240> one<00:12:03.320> is<00:12:03.480> accuracy.

00:12:04.360 --> 00:12:06.840
And<00:12:04.520> if<00:12:04.680> you<00:12:04.800> include<00:12:05.160> privacy,<00:12:05.680> that's<00:12:05.920> another<00:12:06.240> part.

00:12:06.840 --> 00:12:12.480
But<00:12:07.200> most<00:12:07.440> of<00:12:07.520> the<00:12:07.640> time<00:12:07.880> we<00:12:07.960> don't<00:12:08.480> at<00:12:08.600> this<00:12:08.840> stage<00:12:09.240> we<00:12:09.360> don't<00:12:10.000> consider<00:12:10.360> much<00:12:10.760> as<00:12:11.160> privacy<00:12:11.600> problem<00:12:12.000> right<00:12:12.200> now.

00:12:12.480 --> 00:12:17.760
We<00:12:12.640> want<00:12:12.840> to<00:12:12.960> build<00:12:13.240> a<00:12:13.280> model<00:12:13.600> and<00:12:14.160> make<00:12:14.440> the<00:12:14.800> model<00:12:15.160> as<00:12:15.400> accurate<00:12:15.800> as<00:12:15.960> we<00:12:16.080> can<00:12:16.720> at<00:12:16.880> this<00:12:17.040> stage.

00:12:17.760 --> 00:12:26.880
Yeah.<00:12:18.180> <00:12:18.600> Matt,<00:12:19.020> can<00:12:19.440> you<00:12:19.860> talk<00:12:20.280> about<00:12:20.700> how<00:12:21.120> you<00:12:21.540> help<00:12:21.960> researchers<00:12:22.380> like<00:12:22.800> Pengfei<00:12:23.220> really<00:12:23.640> getting<00:12:24.060> the<00:12:24.480> devices<00:12:24.900> into<00:12:25.320> their<00:12:25.740> hands,<00:12:26.160> collaborating

00:12:26.880 --> 00:12:34.960
across<00:12:27.200> the<00:12:27.320> departments?<00:12:28.480> I<00:12:28.600> think<00:12:28.800> it'd<00:12:28.960> be<00:12:29.200> a<00:12:29.320> great<00:12:30.080> It'd<00:12:30.200> be<00:12:30.320> great<00:12:30.520> to<00:12:30.600> hear<00:12:30.800> from<00:12:30.960> you<00:12:31.080> just<00:12:31.240> on<00:12:31.360> the<00:12:31.440> collaboration<00:12:32.200> front<00:12:32.440> between<00:12:33.080> IT<00:12:33.800> and<00:12:34.000> the<00:12:34.080> research<00:12:34.480> side.

00:12:34.960 --> 00:12:43.480
<00:12:35.420> Being<00:12:35.880> embedded<00:12:36.340> within<00:12:36.800> the<00:12:37.260> school<00:12:37.720> where<00:12:38.180> research<00:12:38.640> is<00:12:39.100> being<00:12:39.560> done<00:12:40.020> really<00:12:40.480> makes<00:12:40.940> things<00:12:41.400> changes<00:12:41.860> the<00:12:42.320> whole<00:12:42.780> dynamics<00:12:43.240> for

00:12:43.480 --> 00:12:51.880
us<00:12:43.680> here.<00:12:44.240> So,<00:12:45.040> instead<00:12:45.320> of<00:12:45.680> hiding<00:12:46.040> behind<00:12:46.400> a<00:12:46.480> ticket<00:12:46.880> system<00:12:47.680> or<00:12:48.200> several<00:12:48.880> administrative<00:12:49.600> processes,<00:12:50.200> the<00:12:50.440> faculty<00:12:50.960> can<00:12:51.160> walk<00:12:51.440> up<00:12:51.600> to

00:12:51.880 --> 00:12:54.320
our<00:12:52.280> office<00:12:52.920> and<00:12:53.200> ask<00:12:53.440> for<00:12:53.560> help.

00:12:54.320 --> 00:12:58.200
We<00:12:54.560> will<00:12:54.800> find<00:12:55.200> each<00:12:55.400> other<00:12:55.720> in<00:12:55.880> a<00:12:55.920> hallway<00:12:56.480> and<00:12:56.600> we<00:12:56.720> can<00:12:56.880> discuss<00:12:57.320> ideas.

00:12:58.200 --> 00:13:02.040
So,<00:12:58.400> our<00:12:58.600> goal<00:12:58.839> here<00:12:59.040> is<00:12:59.200> really<00:12:59.560> to<00:13:00.040> remove<00:13:00.640> any<00:13:01.240> obstacle.

00:13:02.040 --> 00:13:06.560
We<00:13:02.160> try<00:13:02.400> to<00:13:02.520> be<00:13:02.800> as<00:13:03.200> to<00:13:03.760> be<00:13:03.960> very<00:13:04.520> speedy<00:13:04.880> when<00:13:05.360> we're<00:13:05.480> trying<00:13:05.720> to<00:13:05.839> help.

00:13:06.560 --> 00:13:13.560
And<00:13:07.040> really<00:13:07.560> we<00:13:07.720> really<00:13:07.960> see<00:13:08.440> each<00:13:08.640> other<00:13:09.680> We<00:13:09.720> really<00:13:09.960> see<00:13:10.200> ourselves<00:13:10.760> as<00:13:11.240> partners<00:13:11.880> when<00:13:12.040> it<00:13:12.160> comes<00:13:12.520> to<00:13:12.920> research.

00:13:13.560 --> 00:13:20.560
So,<00:13:13.760> we're<00:13:13.960> here<00:13:14.280> to<00:13:14.520> work<00:13:14.880> with<00:13:15.200> with<00:13:15.360> the<00:13:15.440> school,<00:13:16.040> with<00:13:16.160> the<00:13:16.280> faculty<00:13:17.200> to<00:13:17.320> get<00:13:17.640> things<00:13:17.920> done,<00:13:18.320> to<00:13:18.520> promote<00:13:19.080> innovation<00:13:19.680> within<00:13:19.920> the<00:13:20.000> school.

00:13:20.560 --> 00:13:25.640
And<00:13:20.720> we're<00:13:20.960> also<00:13:21.240> here<00:13:21.480> to<00:13:21.640> connect<00:13:22.480> our<00:13:22.720> faculty<00:13:23.400> with<00:13:23.600> a<00:13:23.680> larger<00:13:24.440> environment<00:13:24.960> at<00:13:25.040> the<00:13:25.120> university.

00:13:25.640 --> 00:13:28.160
We<00:13:25.760> are<00:13:26.080> Our<00:13:26.320> team<00:13:26.560> is<00:13:26.760> really<00:13:26.960> good<00:13:27.280> in<00:13:27.360> navigating<00:13:27.920> that.

00:13:28.160 --> 00:13:30.800
We're<00:13:28.720> we<00:13:28.880> that's<00:13:29.160> what<00:13:29.280> we<00:13:29.400> do<00:13:29.560> on<00:13:29.720> a<00:13:29.760> daily<00:13:30.000> basis.

00:13:30.800 --> 00:13:35.640
So<00:13:30.920> that<00:13:31.120> way<00:13:31.440> they<00:13:31.680> they<00:13:31.760> allow<00:13:32.000> the<00:13:32.120> researchers<00:13:32.680> they<00:13:32.800> don't<00:13:33.000> need<00:13:33.200> to<00:13:33.400> expend<00:13:34.040> time<00:13:34.480> on<00:13:34.760> these<00:13:35.000> other<00:13:35.320> things.

00:13:35.640 --> 00:13:41.240
We<00:13:35.760> do<00:13:35.920> that<00:13:36.120> for<00:13:36.280> them.<00:13:36.880> So<00:13:37.040> then<00:13:37.280> they<00:13:37.440> can<00:13:38.000> spend<00:13:38.320> their<00:13:38.520> time<00:13:38.880> doing<00:13:39.200> what<00:13:39.480> matters<00:13:39.800> the<00:13:39.880> most<00:13:40.280> for<00:13:40.440> everybody.

00:13:41.240 --> 00:13:48.320
<00:13:41.498> That's<00:13:41.755> great.<00:13:42.013> Now<00:13:42.270> Adrian,<00:13:42.528> you're<00:13:42.786> going<00:13:43.043> to<00:13:43.301> bring<00:13:43.558> it<00:13:43.816> all<00:13:44.074> together<00:13:44.331> because<00:13:44.589> now<00:13:44.846> you're<00:13:45.104> going<00:13:45.362> to<00:13:45.619> tell<00:13:45.877> us<00:13:46.134> how<00:13:46.392> Dell<00:13:46.650> partners<00:13:46.907> with<00:13:47.165> both<00:13:47.422> the<00:13:47.680> researchers

00:13:48.320 --> 00:13:54.320
and<00:13:48.647> on<00:13:48.974> the<00:13:49.301> IT<00:13:49.628> side.<00:13:49.955> <00:13:50.282> I<00:13:50.609> think<00:13:50.936> our<00:13:51.264> power<00:13:51.591> is<00:13:51.918> that<00:13:52.245> connective<00:13:52.572> tissue<00:13:52.899> between<00:13:53.226> the<00:13:53.553> two<00:13:53.880> groups.

00:13:54.320 --> 00:14:02.480
I<00:13:54.400> think<00:13:54.600> sometimes<00:13:55.120> it's<00:13:55.360> seen<00:13:55.680> as<00:13:56.720> IT<00:13:57.120> central<00:13:57.480> IT<00:13:57.760> sitting<00:13:58.040> on<00:13:58.200> one<00:13:58.440> side<00:13:59.080> and<00:13:59.440> university<00:14:00.280> innovation<00:14:01.040> and<00:14:01.360> where<00:14:01.720> the<00:14:01.880> PIs<00:14:02.360> are

00:14:02.480 --> 00:14:07.800
living<00:14:02.800> in<00:14:03.000> different<00:14:03.320> labs<00:14:03.520> and<00:14:03.640> institutes<00:14:04.320> and<00:14:04.440> centers<00:14:04.720> are<00:14:04.840> on<00:14:04.960> the<00:14:05.080> other<00:14:05.320> end<00:14:05.440> of<00:14:05.520> the<00:14:05.600> spectrum<00:14:06.040> and<00:14:06.160> you<00:14:06.240> put<00:14:06.680> Dell<00:14:06.960> in<00:14:07.040> the<00:14:07.160> middle.

00:14:07.800 --> 00:14:16.400
To<00:14:07.920> me<00:14:08.080> I<00:14:08.120> actually<00:14:08.440> think<00:14:08.600> it's<00:14:08.760> a<00:14:08.800> triangle.<00:14:09.440> It's<00:14:09.600> like<00:14:09.880> at<00:14:10.040> any<00:14:10.240> given<00:14:10.600> time<00:14:11.480> we<00:14:11.640> might<00:14:11.800> be<00:14:11.960> more<00:14:13.000> directly<00:14:13.480> connected<00:14:14.080> to<00:14:14.880> troubleshooting<00:14:15.840> individual

00:14:16.400 --> 00:14:24.600
meetings<00:14:16.840> with<00:14:17.000> PIs<00:14:17.400> like<00:14:17.600> Pengfei<00:14:18.320> with<00:14:18.640> Dell<00:14:19.080> and<00:14:19.200> Nvidia<00:14:19.720> giving<00:14:20.000> us<00:14:20.120> direct<00:14:20.480> feedback<00:14:20.960> about<00:14:21.720> what<00:14:21.840> models<00:14:22.160> he's<00:14:22.400> using,<00:14:23.000> what<00:14:23.360> frameworks<00:14:23.880> he's<00:14:24.200> approached,

00:14:24.600 --> 00:14:27.960
what<00:14:24.760> challenges<00:14:25.400> has<00:14:25.560> he<00:14:26.160> hit<00:14:26.360> with<00:14:26.600> and<00:14:26.720> what<00:14:26.880> obstacles<00:14:27.360> there<00:14:27.480> might<00:14:27.720> be.

00:14:27.960 --> 00:14:34.080
If<00:14:28.120> he's<00:14:28.280> tried<00:14:28.560> something<00:14:28.840> different<00:14:29.160> that's<00:14:29.400> outside<00:14:29.760> of<00:14:29.839> the<00:14:29.920> scope<00:14:30.240> and<00:14:30.360> guidelines<00:14:30.839> and<00:14:30.960> so<00:14:31.080> it<00:14:31.160> gives<00:14:31.360> us<00:14:31.520> a<00:14:31.600> chance<00:14:31.920> to<00:14:32.040> revise<00:14:32.400> our<00:14:32.520> documentation,<00:14:33.720> talking

00:14:34.080 --> 00:14:36.680
about<00:14:34.560> opportunities<00:14:35.320> for<00:14:35.960> skill<00:14:36.280> building.

00:14:36.680 --> 00:14:42.560
Like<00:14:36.880> maybe<00:14:37.120> there's<00:14:37.800> like<00:14:37.920> professional<00:14:38.320> development<00:14:38.800> programs<00:14:39.160> that<00:14:39.280> we<00:14:39.440> have<00:14:39.720> that<00:14:39.920> his<00:14:40.120> researchers<00:14:40.720> or<00:14:40.839> his<00:14:41.040> postdocs<00:14:41.560> might<00:14:41.720> want<00:14:41.839> to<00:14:41.920> take<00:14:42.080> advantage<00:14:42.440> of.

00:14:42.560 --> 00:14:49.160
So<00:14:42.640> that<00:14:42.760> could<00:14:42.880> be<00:14:43.000> a<00:14:43.040> direct<00:14:43.800> and<00:14:43.920> then<00:14:44.040> also<00:14:44.320> with<00:14:44.520> IE<00:14:44.760> talking<00:14:45.120> about<00:14:45.560> governance<00:14:46.200> and<00:14:46.560> and<00:14:46.800> budgets<00:14:47.560> and<00:14:48.080> funding<00:14:48.480> constraints.

00:14:49.160 --> 00:14:55.600
And<00:14:49.320> so<00:14:49.920> I<00:14:50.000> think<00:14:50.200> at<00:14:50.280> any<00:14:50.440> given<00:14:50.760> time<00:14:51.360> all<00:14:51.600> three<00:14:52.000> of<00:14:52.160> us<00:14:52.600> in<00:14:52.760> that<00:14:52.960> triangle<00:14:53.880> have<00:14:54.040> a<00:14:54.080> very<00:14:54.360> balanced<00:14:54.920> relationship.

00:14:55.600 --> 00:15:04.600
It's<00:14:55.760> just<00:14:56.400> in<00:14:56.520> different<00:14:56.880> phases<00:14:57.440> of<00:14:58.280> research<00:14:58.720> development<00:14:59.600> you<00:14:59.720> might<00:14:59.960> be<00:15:00.480> the<00:15:00.640> vendor<00:15:01.040> like<00:15:01.280> Dell<00:15:01.520> might<00:15:01.720> be<00:15:01.880> more<00:15:02.520> in<00:15:02.720> tune<00:15:03.080> with<00:15:03.839> direct

00:15:04.600 --> 00:15:13.200
feedback<00:15:05.120> loop<00:15:05.440> with<00:15:05.640> the<00:15:05.760> researcher<00:15:06.320> versus<00:15:07.280> the<00:15:07.400> times<00:15:07.760> that<00:15:07.920> we're<00:15:08.040> looking<00:15:08.400> at<00:15:08.960> governance<00:15:09.680> and<00:15:09.800> a<00:15:09.839> systemic<00:15:10.440> approach<00:15:11.080> and<00:15:11.480> looking<00:15:11.839> for<00:15:12.360> additional<00:15:12.800> pilots,

00:15:13.200 --> 00:15:22.160
going<00:15:13.520> back<00:15:13.800> and<00:15:14.000> adding<00:15:14.360> new<00:15:14.520> technology.<00:15:15.200> So<00:15:15.360> I<00:15:15.400> know<00:15:16.000> for<00:15:16.080> University<00:15:16.640> of<00:15:16.760> Pittsburgh<00:15:17.320> we've<00:15:17.880> actually<00:15:18.720> deployed<00:15:19.440> extra<00:15:19.800> GB10<00:15:20.400> devices<00:15:20.960> to<00:15:21.080> the<00:15:21.160> university<00:15:21.800> because

00:15:22.160 --> 00:15:27.920
of<00:15:22.280> the<00:15:22.400> work<00:15:22.600> that<00:15:22.760> Peng<00:15:23.000> Fei<00:15:23.160> is<00:15:23.360> doing<00:15:24.040> and<00:15:24.200> having<00:15:24.480> other<00:15:24.840> labs<00:15:25.320> be<00:15:25.440> involved<00:15:25.960> in<00:15:26.080> other<00:15:26.480> research<00:15:26.840> centers<00:15:27.160> and<00:15:27.280> institutes.

00:15:27.920 --> 00:15:36.400
So,<00:15:28.520> I<00:15:28.640> think<00:15:28.880> that<00:15:29.560> the<00:15:29.680> whole<00:15:29.840> idea<00:15:30.040> of<00:15:30.160> about<00:15:30.520> bringing<00:15:30.840> it<00:15:30.960> all<00:15:31.080> together,<00:15:31.600> it's<00:15:31.960> balancing<00:15:33.080> the<00:15:33.480> financial<00:15:34.000> constraints,<00:15:34.680> the<00:15:34.800> governance<00:15:35.400> constraints,<00:15:36.200> like

00:15:36.400 --> 00:15:43.080
the<00:15:36.520> things<00:15:36.800> that<00:15:36.920> you<00:15:37.040> don't<00:15:37.280> want<00:15:37.480> to<00:15:37.600> stymie<00:15:38.080> innovation,<00:15:39.080> but<00:15:39.240> they<00:15:39.440> are<00:15:39.960> mandates<00:15:40.480> from<00:15:40.640> the<00:15:40.720> university<00:15:41.400> and<00:15:41.520> there<00:15:41.680> are<00:15:41.880> rules<00:15:42.120> and<00:15:42.240> regulations<00:15:42.800> that<00:15:42.920> need

00:15:43.080 --> 00:15:50.520
to<00:15:43.160> be<00:15:43.280> followed.<00:15:43.640> And<00:15:43.800> so,<00:15:43.960> as<00:15:44.160> a<00:15:44.200> vendor,<00:15:44.640> like<00:15:44.800> we're<00:15:44.960> very<00:15:45.280> much<00:15:45.680> in<00:15:45.880> line<00:15:46.200> with<00:15:46.320> the<00:15:46.440> things<00:15:46.720> that<00:15:46.920> Matt's<00:15:47.320> team<00:15:47.800> needs<00:15:48.520> in<00:15:48.640> order<00:15:48.840> for<00:15:48.960> projects<00:15:49.440> to<00:15:49.560> move<00:15:49.760> forward.

00:15:50.520 --> 00:15:58.960
But<00:15:50.640> at<00:15:50.720> the<00:15:50.800> same<00:15:51.000> time,<00:15:51.280> balancing<00:15:52.280> Peng<00:15:52.520> Fei's<00:15:52.920> group,<00:15:53.680> his<00:15:53.920> research<00:15:54.400> team<00:15:54.880> of<00:15:55.160> here's<00:15:55.400> the<00:15:55.520> innovation,<00:15:56.000> here's<00:15:56.240> us<00:15:56.360> pushing<00:15:56.800> the<00:15:56.920> technology,<00:15:57.640> here's<00:15:58.440> ways<00:15:58.720> that

00:15:58.960 --> 00:16:02.640
we<00:15:59.200> are<00:15:59.400> envisioning<00:16:00.000> use<00:16:00.160> cases<00:16:00.560> that<00:16:00.760> you<00:16:00.880> haven't<00:16:01.240> considered,<00:16:02.040> vendor.

00:16:02.640 --> 00:16:10.920
And<00:16:02.840> so,<00:16:03.000> I<00:16:03.080> think<00:16:03.320> that's<00:16:03.640> the<00:16:03.720> exciting<00:16:04.280> piece<00:16:04.600> is<00:16:05.120> making<00:16:05.440> sure<00:16:05.640> the<00:16:05.760> experimentation<00:16:06.800> is<00:16:07.000> happening<00:16:07.920> in<00:16:08.040> an<00:16:08.160> environment<00:16:09.000> that's<00:16:09.240> still<00:16:09.520> safe<00:16:10.120> and<00:16:10.200> protected.

00:16:10.920 --> 00:16:16.480
<00:16:11.120> So,<00:16:11.320> Adrian's<00:16:11.520> probably<00:16:11.720> going<00:16:11.920> to<00:16:12.120> laugh<00:16:12.320> at<00:16:12.520> me,<00:16:12.720> but<00:16:12.920> I<00:16:13.120> am<00:16:13.320> going<00:16:13.520> to<00:16:13.720> correct<00:16:13.920> her<00:16:14.120> on<00:16:14.320> the<00:16:14.520> podcast<00:16:14.720> cuz,<00:16:14.920> hey,<00:16:15.120> I<00:16:15.320> got<00:16:15.520> the<00:16:15.720> podcast.

00:16:16.480 --> 00:16:18.920
<00:16:16.597> So,<00:16:16.715> your<00:16:16.832> name's<00:16:16.949> on<00:16:17.067> your<00:16:17.184> letterhead<00:16:17.301> and<00:16:17.419> you<00:16:17.536> didn't<00:16:17.653> know<00:16:17.771> it.<00:16:17.888> <00:16:18.005> it's<00:16:18.123> my<00:16:18.240> podcast.

00:16:18.920 --> 00:16:26.680
So,<00:16:19.920> you<00:16:20.000> keep<00:16:20.160> referring<00:16:20.560> You<00:16:20.640> keep<00:16:21.160> You<00:16:21.280> kept<00:16:21.520> referring<00:16:21.920> yourself<00:16:22.440> as<00:16:22.640> a<00:16:22.720> vendor,<00:16:23.080> but<00:16:23.560> having<00:16:23.800> spent<00:16:23.960> some<00:16:24.080> time<00:16:24.280> with<00:16:24.440> Adrian,<00:16:24.920> I<00:16:25.080> would<00:16:25.320> put<00:16:25.600> her<00:16:25.839> in<00:16:26.000> the<00:16:26.160> partner

00:16:26.680 --> 00:16:28.760
bucket.<00:16:27.080> I'm<00:16:27.200> going<00:16:27.320> to<00:16:27.360> just<00:16:27.520> put<00:16:27.720> you<00:16:27.839> in<00:16:27.920> the<00:16:28.000> partner<00:16:28.320> bucket.

00:16:28.760 --> 00:16:33.200
So,<00:16:29.480> a<00:16:29.560> vendor<00:16:31.480> Yeah,<00:16:32.000> you<00:16:32.120> got<00:16:32.280> upgraded,<00:16:32.680> yeah.

00:16:33.200 --> 00:16:35.680
Vendor,<00:16:34.240> they<00:16:34.400> just<00:16:34.560> want<00:16:34.680> to<00:16:34.760> sell<00:16:34.920> you<00:16:35.000> something.

00:16:35.680 --> 00:16:42.880
Partner,<00:16:36.600> you're<00:16:36.760> listening<00:16:37.160> to<00:16:37.280> use<00:16:37.520> cases,<00:16:38.160> you're<00:16:38.280> taking<00:16:38.720> feedback,<00:16:39.640> you're<00:16:40.360> working<00:16:40.680> the<00:16:40.800> triangle,<00:16:41.680> right,<00:16:42.040> as<00:16:42.200> you<00:16:42.320> put<00:16:42.520> it.

00:16:42.880 --> 00:16:45.080
<00:16:43.048> It's<00:16:43.216> built<00:16:43.384> on<00:16:43.552> a<00:16:43.720> triangle,<00:16:43.888> so<00:16:44.056> it's<00:16:44.224> in<00:16:44.392> my<00:16:44.560> mind.

00:16:45.080 --> 00:16:47.640
Pittsburgh<00:16:45.520> is<00:16:45.680> a<00:16:45.720> triangle,<00:16:46.520> the<00:16:46.640> three<00:16:46.839> rivers.

00:16:47.640 --> 00:16:49.520
<00:16:47.863> Oh,<00:16:48.086> yes.<00:16:48.309> It's<00:16:48.531> all<00:16:48.754> coming<00:16:48.977> full<00:16:49.200> circle.

00:16:49.520 --> 00:16:52.920
Peng<00:16:49.720> Fei,<00:16:49.880> I'd<00:16:50.000> like<00:16:50.160> to<00:16:50.280> hear<00:16:50.520> more<00:16:50.760> about<00:16:51.240> the<00:16:51.360> research<00:16:51.960> team.

00:16:52.920 --> 00:16:55.120
You're<00:16:53.080> clearly<00:16:53.440> not<00:16:53.720> doing<00:16:54.000> everything,<00:16:54.880> right?

00:16:55.120 --> 00:17:00.360
Tell<00:16:55.280> us<00:16:55.400> a<00:16:55.440> little<00:16:55.640> bit<00:16:55.800> more<00:16:55.960> about<00:16:56.200> the<00:16:56.280> team<00:16:56.760> and<00:16:57.200> how<00:16:57.480> it's<00:16:58.040> helping<00:16:58.440> you<00:16:58.600> to<00:16:59.080> push<00:16:59.320> forward<00:16:59.839> the<00:16:59.920> mission.

00:17:00.360 --> 00:17:03.960
<00:17:00.588> Yeah,<00:17:00.815> as<00:17:01.043> you<00:17:01.271> mentioned,<00:17:01.498> I'm<00:17:01.726> not<00:17:01.954> doing<00:17:02.182> this<00:17:02.409> by<00:17:02.637> myself,<00:17:02.865> it's<00:17:03.092> not<00:17:03.320> possible.

00:17:03.960 --> 00:17:09.360
This<00:17:04.199> is<00:17:04.360> a<00:17:04.439> collaborative<00:17:05.240> research<00:17:05.880> project<00:17:06.520> across<00:17:06.959> three<00:17:07.199> departments<00:17:07.880> in<00:17:08.000> the<00:17:08.079> University<00:17:08.480> of<00:17:08.520> Pittsburgh.

00:17:09.360 --> 00:17:17.640
And<00:17:09.720> I'm<00:17:09.880> the<00:17:10.000> PI<00:17:10.319> in<00:17:10.480> the<00:17:10.920> School<00:17:11.160> of<00:17:11.199> Computing<00:17:11.640> and<00:17:11.720> Information,<00:17:12.720> and<00:17:12.880> I<00:17:12.959> have<00:17:13.079> a<00:17:13.160> collaborator<00:17:13.680> we<00:17:13.839> got<00:17:14.079> from<00:17:14.480> Electrical<00:17:15.319> and<00:17:15.400> Computer<00:17:15.640> Engineering<00:17:16.680> Department.

00:17:17.640 --> 00:17:23.160
And<00:17:17.800> then<00:17:17.880> we<00:17:18.040> also<00:17:18.400> have<00:17:18.600> a<00:17:18.680> collaborator<00:17:19.240> from<00:17:19.480> the<00:17:19.760> medical<00:17:20.120> school,<00:17:20.839> which<00:17:21.000> is<00:17:21.120> cardiovascular<00:17:22.199> professional.

00:17:23.160 --> 00:17:25.920
He's<00:17:23.520> So,<00:17:23.680> we<00:17:23.839> are<00:17:23.959> doing<00:17:24.240> this<00:17:24.439> together<00:17:25.040> to<00:17:25.160> do<00:17:25.319> that.

00:17:25.920 --> 00:17:34.120
And<00:17:26.640> so,<00:17:26.760> for<00:17:26.880> all<00:17:27.079> of<00:17:27.199> us,<00:17:27.600> and<00:17:28.000> I'm<00:17:28.160> more<00:17:28.600> focusing<00:17:29.040> on<00:17:29.200> the<00:17:29.320> technical<00:17:29.760> part,<00:17:30.120> how<00:17:30.240> to<00:17:30.360> develop<00:17:30.680> models,<00:17:31.200> how<00:17:31.400> to<00:17:32.320> deal<00:17:32.560> with<00:17:32.840> the<00:17:33.480> data.

00:17:34.120 --> 00:17:42.840
And<00:17:34.600> the<00:17:35.120> team<00:17:35.720> the<00:17:35.840> good<00:17:36.360> team<00:17:36.600> in<00:17:36.720> the<00:17:36.960> ECE<00:17:37.360> department,<00:17:37.960> they<00:17:38.040> are<00:17:38.160> all<00:17:38.600> focused<00:17:39.000> on<00:17:39.120> how<00:17:39.240> to<00:17:39.680> how<00:17:39.840> to<00:17:40.120> do<00:17:40.320> this<00:17:40.480> computation<00:17:41.160> on<00:17:41.360> your<00:17:41.760> on<00:17:41.880> your<00:17:41.960> device,<00:17:42.720> how

00:17:42.840 --> 00:17:49.840
to<00:17:42.960> make<00:17:43.160> it<00:17:43.240> efficient,<00:17:44.000> something<00:17:44.280> like<00:17:44.600> because<00:17:45.080> that<00:17:45.320> model<00:17:45.760> efficient<00:17:46.560> will<00:17:46.680> eventually<00:17:47.160> run<00:17:47.400> on<00:17:47.520> your<00:17:47.640> mobile<00:17:47.880> device,<00:17:48.280> and<00:17:48.400> the<00:17:48.480> mobile<00:17:48.720> device<00:17:49.080> is<00:17:49.400> a<00:17:49.480> battery

00:17:49.840 --> 00:17:58.320
power.<00:17:50.360> So,<00:17:50.600> you<00:17:50.720> want<00:17:50.840> to<00:17:50.920> make<00:17:51.120> it<00:17:51.160> efficient.<00:17:51.920> And<00:17:52.280> the<00:17:52.400> other<00:17:52.600> one,<00:17:52.880> the<00:17:53.040> medical<00:17:53.400> school<00:17:53.760> the<00:17:53.880> team<00:17:54.280> is<00:17:54.600> doing<00:17:54.920> the<00:17:55.560> recruit<00:17:55.920> patients,<00:17:56.840> collect<00:17:57.200> data,<00:17:58.040> and

00:17:58.320 --> 00:18:04.640
provide<00:17:58.840> very<00:17:59.240> professional<00:18:00.520> knowledge<00:18:01.000> and<00:18:01.160> guidance,<00:18:01.680> how<00:18:01.920> should<00:18:02.120> we<00:18:02.240> do<00:18:02.440> it,<00:18:02.680> which<00:18:02.880> part<00:18:03.120> is<00:18:03.240> important,<00:18:03.640> something<00:18:03.960> like<00:18:04.120> that.

00:18:04.640 --> 00:18:07.600
So,<00:18:04.760> it's<00:18:04.840> very<00:18:05.280> unique<00:18:05.760> medical<00:18:06.200> domain<00:18:06.760> knowledge.

00:18:07.600 --> 00:18:15.800
This<00:18:07.800> is<00:18:08.000> our<00:18:08.240> big<00:18:08.440> team,<00:18:08.840> and<00:18:09.200> for<00:18:09.480> all<00:18:09.600> my<00:18:10.000> small<00:18:10.400> team,<00:18:10.880> on<00:18:11.040> my<00:18:11.200> small<00:18:11.440> team<00:18:11.760> where<00:18:11.920> I<00:18:12.000> have<00:18:12.200> three<00:18:12.440> PhD<00:18:12.880> students<00:18:13.360> working<00:18:13.640> with<00:18:13.800> me,<00:18:14.440> and<00:18:15.120> and<00:18:15.200> they<00:18:15.320> are<00:18:15.400> doing<00:18:15.600> great

00:18:15.800 --> 00:18:23.040
job.<00:18:16.089> <00:18:16.377> Can<00:18:16.666> you<00:18:16.955> describe<00:18:17.243> just<00:18:17.532> a<00:18:17.821> little<00:18:18.110> bit<00:18:18.398> more<00:18:18.687> about<00:18:18.976> maybe<00:18:19.264> some<00:18:19.553> of<00:18:19.842> the<00:18:20.130> specific<00:18:20.419> use<00:18:20.708> cases<00:18:20.997> that<00:18:21.285> they<00:18:21.574> are<00:18:21.863> working<00:18:22.151> on,<00:18:22.440> too?

00:18:23.040 --> 00:18:27.640
<00:18:23.373> Yeah.<00:18:23.707> I<00:18:24.040> can<00:18:24.373> start<00:18:24.707> with<00:18:25.040> our<00:18:25.373> first<00:18:25.707> problem<00:18:26.040> we<00:18:26.373> tried<00:18:26.707> to<00:18:27.040> solve.

00:18:27.640 --> 00:18:34.120
For<00:18:27.760> example,<00:18:28.200> the<00:18:28.640> right<00:18:28.880> now,<00:18:29.560> the<00:18:29.680> data<00:18:29.960> problem<00:18:30.600> right<00:18:30.760> now<00:18:30.960> the<00:18:31.600> the<00:18:31.720> heart<00:18:32.000> monitoring<00:18:32.560> is<00:18:32.720> not<00:18:32.880> a<00:18:33.160> new<00:18:33.400> topic.

00:18:34.120 --> 00:18:39.560
People<00:18:34.400> are<00:18:34.520> doing<00:18:34.800> it<00:18:34.880> for<00:18:35.040> many<00:18:35.320> years.<00:18:36.080> And<00:18:36.600> for<00:18:36.720> example,<00:18:37.080> people<00:18:37.320> are<00:18:37.440> monitoring<00:18:38.000> the<00:18:38.480> blood<00:18:38.760> pressure.

00:18:39.560 --> 00:18:45.640
And<00:18:40.320> as<00:18:40.520> I<00:18:40.560> would<00:18:40.680> discuss<00:18:41.120> before,<00:18:41.480> the<00:18:42.160> this<00:18:42.520> kind<00:18:42.680> of<00:18:42.800> heart<00:18:43.000> disease<00:18:43.480> happens<00:18:43.880> suddenly<00:18:44.640> all<00:18:44.760> the<00:18:44.840> time.

00:18:45.640 --> 00:18:53.960
So,<00:18:46.400> if<00:18:46.560> you<00:18:46.680> put<00:18:46.880> more<00:18:47.080> effort<00:18:47.440> to<00:18:47.560> monitor<00:18:48.080> it,<00:18:48.320> to<00:18:48.440> track<00:18:48.800> the<00:18:49.320> status,<00:18:50.160> you<00:18:50.280> will<00:18:50.400> be<00:18:50.960> more<00:18:51.320> conscious,<00:18:51.840> or<00:18:52.040> you'll<00:18:52.200> be<00:18:52.840> know<00:18:53.600> when<00:18:53.880> you

00:18:53.960 --> 00:19:01.800
should<00:18:54.160> you<00:18:54.280> see<00:18:54.400> a<00:18:54.480> doctor.<00:18:55.280> And<00:18:55.960> but<00:18:56.480> even<00:18:56.800> the<00:18:56.880> monitoring<00:18:57.400> the<00:18:57.520> heart<00:18:57.960> blood<00:18:58.240> pressure<00:18:58.760> is<00:18:59.080> not<00:18:59.320> a<00:18:59.720> not<00:18:59.920> something<00:19:00.320> people<00:19:00.800> like<00:19:01.160> do<00:19:01.360> every<00:19:01.560> day.

00:19:01.800 --> 00:19:05.920
For<00:19:01.920> example,<00:19:02.320> we<00:19:02.480> I<00:19:02.560> don't<00:19:02.800> do<00:19:02.920> it<00:19:03.080> every<00:19:03.280> day,<00:19:03.920> and<00:19:04.120> I<00:19:04.160> don't<00:19:04.360> believe<00:19:04.800> most<00:19:05.080> people<00:19:05.280> do<00:19:05.440> it.

00:19:05.920 --> 00:19:11.640
But<00:19:06.080> it<00:19:06.200> turns<00:19:06.520> out<00:19:06.680> people<00:19:06.960> are<00:19:07.080> having<00:19:07.480> it<00:19:07.840> long<00:19:08.480> before<00:19:09.080> they<00:19:09.560> really<00:19:09.840> realize<00:19:10.640> it<00:19:10.760> has<00:19:10.960> happened.

00:19:11.640 --> 00:19:19.920
And<00:19:12.280> it's<00:19:12.560> is<00:19:12.960> that<00:19:13.040> we<00:19:13.200> are<00:19:13.320> doing<00:19:14.160> the<00:19:14.240> blood<00:19:14.560> pressure<00:19:14.880> basically<00:19:15.240> have<00:19:15.480> we<00:19:15.600> wear<00:19:15.760> a<00:19:15.840> cuff<00:19:16.320> and<00:19:16.520> a<00:19:16.560> bump<00:19:16.960> pump<00:19:17.240> some<00:19:18.080> gas<00:19:18.440> into<00:19:18.720> it<00:19:18.920> and<00:19:19.080> release<00:19:19.440> it<00:19:19.600> and<00:19:19.800> you

00:19:19.920 --> 00:19:22.760
have<00:19:20.040> a<00:19:20.120> mirror<00:19:20.440> on<00:19:20.600> it,<00:19:20.760> right?<00:19:21.240> So,<00:19:21.520> this<00:19:21.760> is<00:19:21.840> a<00:19:21.960> problem.

00:19:22.760 --> 00:19:27.480
Say,<00:19:23.400> can<00:19:23.600> do<00:19:23.760> that<00:19:24.120> to<00:19:24.560> theoretically<00:19:25.160> yes,<00:19:25.400> you<00:19:25.480> can<00:19:25.600> do<00:19:25.760> that<00:19:25.920> every<00:19:26.120> day,<00:19:26.320> but<00:19:26.680> people<00:19:26.920> won't<00:19:27.080> do<00:19:27.240> that.

00:19:27.480 --> 00:19:35.680
It's<00:19:27.720> too<00:19:27.920> troublesome.<00:19:28.760> And<00:19:29.080> also<00:19:29.360> then<00:19:29.720> that<00:19:29.880> we<00:19:30.000> want<00:19:30.240> to<00:19:30.680> build<00:19:30.920> something<00:19:31.720> can<00:19:32.040> sense<00:19:32.400> your<00:19:32.520> heart<00:19:32.840> blood<00:19:33.120> pressure<00:19:33.920> continuously<00:19:35.200> you<00:19:35.320> don't<00:19:35.480> need

00:19:35.680 --> 00:19:41.360
any<00:19:36.240> intervention<00:19:36.800> into<00:19:37.080> it.<00:19:37.600> So,<00:19:38.040> then<00:19:38.320> we<00:19:38.520> have<00:19:38.680> tried<00:19:38.920> to<00:19:39.040> build<00:19:39.240> some<00:19:39.760> sensor<00:19:40.040> data<00:19:40.640> from<00:19:40.960> it.

00:19:41.360 --> 00:19:47.040
And<00:19:41.560> right<00:19:41.760> now<00:19:42.400> the<00:19:42.520> sensor<00:19:42.800> data<00:19:43.040> is<00:19:43.960> then<00:19:44.240> the<00:19:44.480> problems<00:19:45.080> becomes<00:19:45.880> the<00:19:46.000> accuracy<00:19:46.440> problem.

00:19:47.040 --> 00:19:55.120
You<00:19:47.240> some<00:19:47.480> of<00:19:47.600> the<00:19:47.680> sensor<00:19:47.920> data<00:19:48.200> is<00:19:48.360> easy<00:19:48.640> to<00:19:48.760> get,<00:19:49.120> but<00:19:49.320> it's<00:19:49.480> not<00:19:49.880> accuracy,<00:19:50.440> but<00:19:50.600> some<00:19:50.840> of<00:19:51.040> them<00:19:51.680> for<00:19:51.800> example,<00:19:52.120> you<00:19:52.280> attach<00:19:52.800> some<00:19:53.240> tablets<00:19:53.800> on<00:19:53.960> your<00:19:54.120> body<00:19:54.440> you<00:19:54.840> measure

00:19:55.120 --> 00:19:59.960
the<00:19:55.240> electricity<00:19:56.200> running<00:19:56.520> through<00:19:56.760> your<00:19:57.280> heart,<00:19:57.640> which<00:19:57.760> is<00:19:57.880> called<00:19:58.160> electrical<00:19:59.240> photography.

00:19:59.960 --> 00:20:05.240
It's<00:20:00.160> called<00:20:00.360> ECG.<00:20:01.280> And<00:20:01.640> but<00:20:01.880> that<00:20:02.080> kind<00:20:02.240> of<00:20:02.360> things<00:20:02.800> is<00:20:03.040> also<00:20:03.320> a<00:20:03.400> problem<00:20:04.040> because<00:20:04.320> you<00:20:04.400> can<00:20:04.560> do<00:20:04.720> that<00:20:04.880> every<00:20:05.080> day.

00:20:05.240 --> 00:20:12.480
You<00:20:05.400> wear<00:20:05.600> the<00:20:05.720> tabs.<00:20:06.320> So,<00:20:06.680> then<00:20:06.960> the<00:20:07.280> technical<00:20:07.720> problem<00:20:08.080> becomes<00:20:08.440> can<00:20:08.760> we<00:20:09.160> somehow<00:20:10.080> combine<00:20:10.440> the<00:20:10.600> two<00:20:11.200> to<00:20:11.320> get<00:20:11.520> it<00:20:11.640> done,<00:20:12.120> right?

00:20:12.480 --> 00:20:15.640
To<00:20:12.880> to<00:20:12.960> get<00:20:13.160> a<00:20:13.640> super<00:20:14.040> easy<00:20:14.280> sensor,<00:20:14.680> which<00:20:14.920> we<00:20:15.000> call<00:20:15.160> PPG.

00:20:15.640 --> 00:20:18.840
Basically<00:20:16.000> it's<00:20:16.160> a<00:20:16.800> it's<00:20:17.000> a<00:20:17.120> light<00:20:17.520> signal<00:20:17.920> from<00:20:18.160> your<00:20:18.240> body.

00:20:18.840 --> 00:20:22.480
We<00:20:19.040> reflect<00:20:19.800> share<00:20:20.040> a<00:20:20.120> light<00:20:20.400> on<00:20:20.520> your<00:20:20.680> vessel<00:20:21.120> and<00:20:21.320> get<00:20:21.480> a<00:20:21.520> reflection<00:20:22.160> on<00:20:22.240> that.

00:20:22.480 --> 00:20:25.800
We<00:20:22.560> measure<00:20:22.840> that.<00:20:23.440> And<00:20:23.560> this<00:20:23.760> is<00:20:23.840> continuous.<00:20:24.360> You<00:20:24.440> don't<00:20:24.640> need<00:20:24.840> to<00:20:25.320> do<00:20:25.480> anything.

00:20:25.800 --> 00:20:27.760
Just<00:20:26.040> wearable.<00:20:26.760> Wear<00:20:27.080> a<00:20:27.160> mobile<00:20:27.440> device.

00:20:27.760 --> 00:20:30.480
Like<00:20:27.960> you<00:20:28.080> have<00:20:28.280> a<00:20:28.480> Apple<00:20:28.800> Watch,<00:20:29.040> you<00:20:29.160> probably<00:20:29.480> have<00:20:29.640> that<00:20:29.880> too.

00:20:30.480 --> 00:20:38.720
So,<00:20:30.800> you<00:20:30.920> measure<00:20:31.200> the<00:20:31.320> signal<00:20:31.760> and<00:20:32.120> we<00:20:32.200> try<00:20:32.360> to<00:20:32.480> use<00:20:32.720> that<00:20:32.880> signal<00:20:33.760> to<00:20:34.040> generate<00:20:34.760> the<00:20:35.120> electric<00:20:35.600> signal<00:20:36.360> at<00:20:36.440> the<00:20:36.520> same<00:20:36.720> time<00:20:37.120> and<00:20:37.240> then<00:20:37.320> combine<00:20:37.760> the<00:20:37.880> two<00:20:38.480> to

00:20:38.720 --> 00:20:44.880
measure<00:20:39.000> your<00:20:39.160> blood<00:20:39.400> pressure.<00:20:40.080> So,<00:20:40.400> and<00:20:40.640> we<00:20:40.720> did<00:20:40.920> a<00:20:40.960> very<00:20:41.160> good<00:20:41.360> job<00:20:41.800> and<00:20:42.320> get<00:20:42.520> very<00:20:42.920> amazing<00:20:43.640> results<00:20:44.240> right<00:20:44.440> now.

00:20:44.880 --> 00:20:49.280
That's<00:20:45.120> all<00:20:45.520> some<00:20:45.760> is<00:20:45.960> a<00:20:46.040> little<00:20:46.320> detail,<00:20:47.080> but<00:20:47.320> I<00:20:47.680> I<00:20:47.760> would<00:20:47.880> say<00:20:48.080> is<00:20:48.160> that<00:20:48.320> it<00:20:48.400> kind<00:20:48.520> of<00:20:48.640> data<00:20:48.880> problem.

00:20:49.280 --> 00:20:52.920
How<00:20:49.440> do<00:20:49.560> you<00:20:49.640> get<00:20:50.120> generate<00:20:50.440> different<00:20:50.800> the<00:20:50.880> modality<00:20:51.360> of<00:20:51.520> it<00:20:51.720> and<00:20:51.960> get<00:20:52.120> things<00:20:52.360> there.

00:20:52.920 --> 00:20:56.560
<00:20:53.151> Yeah,<00:20:53.382> no,<00:20:53.612> that's<00:20:53.843> great.<00:20:54.074> So,<00:20:54.305> Matt,<00:20:54.535> I<00:20:54.766> wanted<00:20:54.997> to<00:20:55.228> jump<00:20:55.458> back<00:20:55.689> to<00:20:55.920> you.

00:20:56.560 --> 00:20:58.600
So,<00:20:56.760> Peng<00:20:56.960> Fei,<00:20:57.320> he's<00:20:57.480> got<00:20:57.640> a<00:20:57.680> lot<00:20:57.840> going<00:20:58.120> on.

00:20:58.600 --> 00:21:06.920
We've<00:20:58.760> got<00:20:58.920> multiple<00:20:59.320> researchers.<00:21:00.840> I<00:21:00.920> like<00:21:01.160> to<00:21:01.280> hear<00:21:01.480> more<00:21:01.800> about<00:21:02.800> the<00:21:02.880> cross-functional<00:21:04.240> collaboration,<00:21:05.440> which<00:21:05.560> I<00:21:05.600> think<00:21:05.720> it's<00:21:05.880> really<00:21:06.160> underrated.

00:21:06.920 --> 00:21:11.240
I<00:21:06.960> think<00:21:07.120> it's<00:21:07.280> easy<00:21:07.600> to<00:21:07.720> say<00:21:07.880> that<00:21:08.120> and<00:21:08.200> much<00:21:08.400> harder<00:21:08.640> to<00:21:08.800> do,<00:21:09.320> especially<00:21:09.720> at<00:21:09.840> the<00:21:09.920> university<00:21:10.440> level.

00:21:11.240 --> 00:21:17.960
And<00:21:11.800> Adrian<00:21:12.600> hinted<00:21:12.880> on<00:21:13.040> it<00:21:13.120> earlier,<00:21:13.680> everything<00:21:14.080> from<00:21:14.640> governance<00:21:15.720> to<00:21:16.480> we<00:21:16.600> think<00:21:16.760> about<00:21:17.160> researchers.

00:21:17.960 --> 00:21:21.080
I<00:21:18.000> was<00:21:18.120> talking<00:21:18.360> about<00:21:18.560> UC<00:21:18.800> Santa<00:21:19.040> Barbara,<00:21:19.480> UCSB<00:21:20.040> before<00:21:20.360> this.

00:21:21.080 --> 00:21:28.400
And<00:21:22.080> you<00:21:22.720> you<00:21:22.800> can't<00:21:23.040> just<00:21:23.400> hand<00:21:23.920> a<00:21:24.040> researcher<00:21:24.560> a<00:21:24.600> laptop<00:21:25.240> or<00:21:25.440> any<00:21:25.600> device<00:21:26.120> and<00:21:26.240> go,<00:21:26.720> "All<00:21:26.800> right,<00:21:27.480> do<00:21:27.600> whatever<00:21:27.840> you<00:21:27.920> want."

00:21:28.400 --> 00:21:35.960
There<00:21:28.640> needs<00:21:28.880> to<00:21:28.960> be<00:21:29.120> some<00:21:29.560> You<00:21:29.680> just<00:21:29.840> maybe<00:21:30.040> talk<00:21:30.320> about<00:21:31.280> the<00:21:31.400> collaboration<00:21:32.280> of<00:21:32.760> how<00:21:32.960> the<00:21:33.080> two<00:21:33.240> of<00:21:33.360> you<00:21:33.480> get<00:21:33.680> on<00:21:33.840> the<00:21:33.960> same<00:21:34.280> page<00:21:34.760> or<00:21:34.840> the<00:21:35.040> two<00:21:35.120> departments<00:21:35.640> get<00:21:35.800> on<00:21:35.880> the

00:21:35.960 --> 00:21:38.920
same<00:21:36.380> page<00:21:36.800> between<00:21:37.220> research<00:21:37.640> and<00:21:38.060> <00:21:38.480> Sure.

00:21:38.920 --> 00:21:47.280
We<00:21:39.120> begin<00:21:39.520> by<00:21:40.360> actually<00:21:41.120> taking<00:21:41.480> advantage<00:21:42.040> of<00:21:42.240> the<00:21:42.400> whole<00:21:42.760> infrastructure,<00:21:43.480> larger<00:21:44.040> IT<00:21:44.320> infrastructure<00:21:45.160> that<00:21:45.520> the<00:21:45.560> university<00:21:46.120> provides<00:21:46.760> to<00:21:46.800> us.

00:21:47.280 --> 00:21:54.160
Okay,<00:21:47.440> so<00:21:47.760> we<00:21:47.920> have<00:21:48.640> Pitt<00:21:48.840> Digital<00:21:49.240> here<00:21:49.840> who<00:21:50.240> will<00:21:50.440> take<00:21:50.680> care<00:21:51.080> of<00:21:51.680> making<00:21:52.000> sure<00:21:52.200> that<00:21:52.360> the<00:21:52.400> environment<00:21:52.960> is<00:21:53.040> secure.

00:21:54.160 --> 00:22:00.160
And<00:21:54.240> we<00:21:54.360> have<00:21:54.600> firewalls,<00:21:55.680> that<00:21:56.160> that<00:21:56.760> network<00:21:57.480> is<00:21:57.680> fast<00:21:58.160> and<00:21:58.240> is<00:21:58.360> accessible<00:21:59.040> to<00:21:59.200> everybody.

00:22:00.160 --> 00:22:03.000
So<00:22:00.360> this<00:22:00.640> is<00:22:00.760> the<00:22:00.880> larger<00:22:01.320> IT<00:22:01.600> here<00:22:01.960> within<00:22:02.280> the<00:22:02.360> university.

00:22:03.000 --> 00:22:08.880
And<00:22:03.440> they<00:22:03.560> do<00:22:03.800> a<00:22:03.960> very<00:22:04.600> like<00:22:04.840> if<00:22:04.920> you<00:22:05.000> see<00:22:05.080> the<00:22:05.200> size<00:22:05.560> of<00:22:05.640> their<00:22:05.760> operations,<00:22:06.520> it's<00:22:06.720> a<00:22:06.880> jaw-dropping<00:22:08.000> kind<00:22:08.200> of<00:22:08.280> thing.

00:22:08.880 --> 00:22:14.080
My<00:22:09.120> team<00:22:09.480> here<00:22:09.920> will<00:22:10.120> then<00:22:10.520> make<00:22:10.920> the<00:22:11.040> bridge<00:22:11.640> between<00:22:12.000> the<00:22:12.160> larger<00:22:13.000> with<00:22:13.160> the<00:22:13.280> local.

00:22:14.080 --> 00:22:22.160
And<00:22:14.480> that's<00:22:14.800> the<00:22:14.960> part<00:22:15.480> that<00:22:16.000> the<00:22:16.120> researcher<00:22:17.040> gets<00:22:17.440> to<00:22:18.000> work<00:22:18.280> with<00:22:18.480> us<00:22:18.800> not<00:22:19.040> only<00:22:19.320> in<00:22:19.520> one<00:22:19.760> project,<00:22:20.600> but<00:22:20.800> over<00:22:21.120> the<00:22:21.280> years<00:22:21.840> they're<00:22:21.960> going<00:22:22.080> to

00:22:22.160 --> 00:22:30.480
be<00:22:22.360> working<00:22:22.880> with<00:22:23.080> us.<00:22:23.760> And<00:22:24.600> sometimes<00:22:25.280> there<00:22:25.440> are<00:22:25.520> cases<00:22:25.880> that<00:22:26.160> because<00:22:26.520> we<00:22:26.680> work<00:22:27.160> with<00:22:27.680> basically<00:22:28.520> the<00:22:28.640> like<00:22:28.920> all<00:22:29.080> the<00:22:29.200> researchers<00:22:29.800> here<00:22:29.960> in<00:22:30.200> within

00:22:30.480 --> 00:22:38.840
the<00:22:30.600> school,<00:22:31.520> we<00:22:31.680> have<00:22:31.920> we<00:22:32.200> my<00:22:32.440> team<00:22:32.800> will<00:22:32.920> have<00:22:33.480> maybe<00:22:33.760> we'll<00:22:33.880> have<00:22:34.040> information<00:22:34.800> that<00:22:35.240> we<00:22:35.800> learned<00:22:36.560> from<00:22:36.800> working<00:22:37.040> with<00:22:37.280> some<00:22:37.440> other<00:22:37.680> PI<00:22:38.600> and

00:22:38.840 --> 00:22:41.840
that<00:22:39.000> can<00:22:39.120> help<00:22:39.560> with<00:22:39.880> things<00:22:40.360> pink<00:22:40.520> face<00:22:40.920> research.

00:22:41.840 --> 00:22:48.720
Not<00:22:42.000> only<00:22:42.200> that,<00:22:42.760> we<00:22:43.320> we<00:22:43.520> are<00:22:43.800> in<00:22:44.360> really<00:22:44.640> close<00:22:45.160> contact<00:22:45.640> with<00:22:46.120> the<00:22:46.160> university<00:22:46.800> like<00:22:47.000> with<00:22:47.400> Pitt<00:22:47.600> Digital<00:22:48.040> here.

00:22:48.720 --> 00:22:51.600
So<00:22:49.160> we<00:22:49.360> know<00:22:49.840> what<00:22:50.320> what<00:22:50.520> they<00:22:50.640> can<00:22:50.920> offer.

00:22:51.600 --> 00:22:56.560
We<00:22:51.880> sometimes<00:22:52.280> because<00:22:52.720> not<00:22:53.240> it's<00:22:53.480> not<00:22:53.680> always<00:22:53.960> the<00:22:54.040> case<00:22:54.400> that<00:22:54.560> we<00:22:54.640> should<00:22:55.000> do<00:22:55.200> things<00:22:55.480> locally<00:22:56.000> here,<00:22:56.280> right?

00:22:56.560 --> 00:23:04.720
We<00:22:56.680> have<00:22:57.280> our<00:22:57.480> center<00:22:57.920> for<00:22:58.240> research<00:22:58.760> and<00:22:58.840> computing<00:22:59.600> and<00:22:59.760> data<00:23:00.160> that<00:23:00.520> that<00:23:00.640> has<00:23:01.240> much<00:23:01.560> more<00:23:02.120> way<00:23:02.400> better<00:23:02.920> tooling<00:23:03.440> that<00:23:03.640> a<00:23:03.720> local<00:23:04.280> IT<00:23:04.680> uh

00:23:04.720 --> 00:23:12.960
uh<00:23:04.880> our<00:23:05.080> local<00:23:05.400> IT<00:23:05.520> department<00:23:05.960> will<00:23:06.080> have.<00:23:06.640> But<00:23:07.120> having<00:23:07.800> in<00:23:08.000> possession<00:23:08.480> of<00:23:08.680> this<00:23:08.880> information<00:23:10.000> is<00:23:10.160> what<00:23:10.360> allows<00:23:10.800> us<00:23:11.000> to<00:23:11.560> help<00:23:12.320> to<00:23:12.520> aid<00:23:12.800> the

00:23:12.960 --> 00:23:16.800
PI<00:23:13.400> to<00:23:13.600> make<00:23:13.840> better<00:23:14.080> decisions,<00:23:15.120> to<00:23:15.400> also<00:23:15.840> support<00:23:16.400> them.

00:23:16.800 --> 00:23:25.040
We<00:23:17.360> the<00:23:17.480> other<00:23:17.680> day<00:23:17.920> we<00:23:18.040> had<00:23:18.440> here<00:23:18.920> a<00:23:19.000> PhD<00:23:19.520> student<00:23:19.960> who<00:23:20.120> was<00:23:20.240> looking<00:23:20.560> for<00:23:21.280> a<00:23:21.720> an<00:23:22.040> LLM<00:23:22.480> model<00:23:23.280> and<00:23:23.680> it<00:23:23.840> turned<00:23:24.120> out<00:23:24.360> that<00:23:24.800> he

00:23:25.040 --> 00:23:33.440
had<00:23:25.280> spent<00:23:25.560> a<00:23:25.600> lot<00:23:25.760> already<00:23:26.080> like<00:23:26.280> about<00:23:26.520> a<00:23:26.600> week<00:23:27.240> looking<00:23:27.560> for<00:23:27.800> something<00:23:28.120> that<00:23:28.240> would<00:23:28.480> fit<00:23:29.000> his<00:23:29.240> research<00:23:30.000> thesis<00:23:30.800> and<00:23:31.720> it<00:23:31.840> turned<00:23:32.080> out<00:23:32.200> that<00:23:32.360> we<00:23:32.480> had<00:23:33.160> worked

00:23:33.440 --> 00:23:38.240
with<00:23:33.800> them<00:23:34.040> for<00:23:34.600> creating<00:23:34.920> an<00:23:35.120> environment<00:23:35.480> for<00:23:35.720> a<00:23:35.760> course<00:23:36.280> where<00:23:36.600> we<00:23:36.720> were<00:23:36.840> teaching<00:23:37.240> here<00:23:37.440> in<00:23:37.520> the<00:23:37.600> school.

00:23:38.240 --> 00:23:41.960
It<00:23:38.360> was<00:23:38.840> a<00:23:38.920> matter<00:23:39.200> of<00:23:39.600> simply<00:23:39.960> him<00:23:40.280> like<00:23:40.480> walking<00:23:40.800> up<00:23:41.000> to<00:23:41.080> my<00:23:41.240> door.

00:23:41.960 --> 00:23:44.800
I<00:23:42.000> was<00:23:42.120> like,<00:23:42.280> "Have<00:23:42.480> you<00:23:42.560> tried<00:23:43.000> this?"<00:23:43.520> And<00:23:43.600> he<00:23:43.640> said,<00:23:43.840> "Oh,<00:23:44.080> actually<00:23:44.520> no.

00:23:44.800 --> 00:23:50.040
I'll<00:23:44.920> give<00:23:45.120> this<00:23:45.280> a<00:23:45.360> try."<00:23:46.120> And<00:23:46.760> it<00:23:46.880> was<00:23:47.160> a<00:23:47.240> couple<00:23:47.520> days<00:23:47.760> later<00:23:48.000> he<00:23:48.120> came<00:23:48.280> back<00:23:48.520> saying,<00:23:48.840> "Oh,<00:23:49.120> thank<00:23:49.360> you<00:23:49.480> so<00:23:49.760> much.

00:23:50.040 --> 00:23:58.480
That<00:23:50.160> was<00:23:50.400> exactly<00:23:51.080> what<00:23:51.280> I<00:23:51.360> needed."<00:23:52.040> So<00:23:52.200> this<00:23:52.480> is<00:23:52.560> how<00:23:53.280> being<00:23:53.720> we<00:23:53.840> have<00:23:54.080> this<00:23:54.720> really<00:23:55.080> close<00:23:55.880> being<00:23:56.160> in<00:23:56.520> close<00:23:56.800> proximity<00:23:57.480> even<00:23:57.880> with<00:23:58.360> with

00:23:58.480 --> 00:24:01.560
the<00:23:58.560> PIs<00:23:59.040> here<00:23:59.280> within<00:23:59.560> the<00:23:59.640> school.<00:24:00.400> We<00:24:00.480> know<00:24:00.680> each<00:24:01.000> other.

00:24:01.560 --> 00:24:09.440
This<00:24:01.760> relationship<00:24:02.360> with<00:24:02.480> develop<00:24:02.840> with<00:24:02.960> them<00:24:03.160> like<00:24:03.360> this<00:24:03.720> in<00:24:03.880> my<00:24:04.040> opinion<00:24:04.760> priceless<00:24:05.640> and<00:24:05.760> it's<00:24:05.920> hard<00:24:06.360> and<00:24:06.440> very<00:24:06.720> hard<00:24:07.040> or<00:24:07.320> impractical<00:24:08.000> to<00:24:08.120> replicate<00:24:08.920> at<00:24:09.040> a<00:24:09.120> larger

00:24:09.440 --> 00:24:13.320
scale.<00:24:09.760> So<00:24:09.920> that's<00:24:10.160> why<00:24:10.360> we're<00:24:10.560> very<00:24:11.200> successful<00:24:11.760> in<00:24:11.800> collaborating<00:24:12.400> with<00:24:12.520> the<00:24:12.600> PIs.

00:24:13.320 --> 00:24:15.120
Yeah,<00:24:13.400> that's<00:24:13.560> got<00:24:13.680> to<00:24:13.720> be<00:24:13.800> a<00:24:13.840> lot<00:24:14.000> of<00:24:14.080> fun.<00:24:14.400> It's<00:24:14.520> interesting<00:24:14.840> too.

00:24:15.120 --> 00:24:21.600
I<00:24:15.600> there's<00:24:15.800> a<00:24:15.840> book<00:24:16.120> called,<00:24:16.920> you<00:24:17.000> don't<00:24:17.120> even<00:24:17.240> have<00:24:17.360> to<00:24:17.440> read<00:24:17.640> it,<00:24:18.200> the<00:24:18.320> title<00:24:18.600> says<00:24:18.800> everything,<00:24:19.520> who<00:24:20.040> who<00:24:20.200> not<00:24:20.480> how,<00:24:21.120> right?

00:24:21.600 --> 00:24:24.840
I<00:24:21.640> think<00:24:21.800> a<00:24:21.840> lot<00:24:22.000> of<00:24:22.080> times<00:24:22.560> we<00:24:22.640> spend<00:24:22.840> a<00:24:22.880> lot<00:24:23.000> of<00:24:23.080> time<00:24:23.200> like,<00:24:23.320> "Hey,<00:24:23.480> how<00:24:23.640> am<00:24:23.760> I<00:24:23.840> going<00:24:23.960> to<00:24:24.040> do<00:24:24.200> this?"

00:24:24.840 --> 00:24:30.120
And<00:24:24.960> a<00:24:25.000> week<00:24:25.200> goes<00:24:25.440> by<00:24:25.680> and<00:24:25.760> you're<00:24:25.840> like,<00:24:26.080> "I<00:24:26.160> don't<00:24:26.320> know."<00:24:26.440> And<00:24:26.520> then<00:24:26.640> finally<00:24:26.920> you<00:24:27.040> ask<00:24:27.200> somebody<00:24:27.640> and<00:24:28.360> they<00:24:28.600> then<00:24:28.880> become<00:24:29.200> my<00:24:29.440> who.

00:24:30.120 --> 00:24:32.440
They<00:24:30.400> figure<00:24:30.760> it<00:24:30.840> out,<00:24:30.960> right?<00:24:31.480> So<00:24:31.600> I<00:24:31.680> love<00:24:31.880> that.

00:24:32.440 --> 00:24:40.920
So<00:24:33.360> as<00:24:33.520> we<00:24:33.640> start<00:24:33.960> to<00:24:34.880> turn<00:24:35.160> the<00:24:35.280> corner<00:24:36.160> towards<00:24:36.920> wrapping<00:24:37.280> up<00:24:37.360> the<00:24:37.440> podcast<00:24:38.240> in<00:24:38.360> the<00:24:38.440> next<00:24:38.920> 10<00:24:39.120> or<00:24:39.200> so<00:24:39.360> minutes,<00:24:40.000> there's<00:24:40.200> a<00:24:40.240> lot<00:24:40.400> of<00:24:40.480> technology

00:24:40.920 --> 00:24:44.800
going<00:24:41.200> on.<00:24:41.760> There's<00:24:41.880> a<00:24:41.920> lot<00:24:42.040> of<00:24:42.160> innovation.<00:24:42.920> It's<00:24:43.080> a<00:24:43.120> fun<00:24:43.360> time<00:24:43.560> to<00:24:43.640> be<00:24:43.760> alive.

00:24:44.800 --> 00:24:53.720
I<00:24:45.000> mainly<00:24:45.440> use<00:24:46.240> and<00:24:46.360> when<00:24:46.480> I<00:24:46.560> say<00:24:46.800> AI,<00:24:47.320> I'm<00:24:47.480> mainly<00:24:48.160> referring<00:24:48.560> to<00:24:48.680> generative<00:24:49.160> AI<00:24:49.480> for<00:24:49.600> myself,<00:24:50.200> but<00:24:50.360> I<00:24:50.440> also<00:24:50.720> realize<00:24:51.320> that<00:24:51.520> there<00:24:51.760> are<00:24:52.360> lots<00:24:52.640> of<00:24:52.760> different<00:24:53.360> types

00:24:53.720 --> 00:24:57.200
out<00:24:53.880> there.<00:24:54.160> We<00:24:54.480> you<00:24:54.600> mentioned<00:24:55.000> earlier<00:24:55.440> Peng<00:24:55.640> Fei,<00:24:55.840> I<00:24:56.160> you<00:24:56.240> said<00:24:56.440> deep<00:24:56.680> learning,<00:24:57.040> right?

00:24:57.200 --> 00:25:02.960
That's<00:24:57.320> another<00:24:57.600> one.<00:24:57.960> I<00:24:58.040> think<00:24:58.240> even<00:24:58.440> too,<00:24:58.640> I<00:24:58.720> think<00:24:59.200> early<00:24:59.520> on<00:24:59.840> and<00:24:59.960> still<00:25:00.120> a<00:25:00.160> lot<00:25:00.320> of<00:25:00.400> people<00:25:00.680> confuse<00:25:01.320> machine<00:25:01.840> learning<00:25:02.240> with<00:25:02.440> AI.

00:25:02.960 --> 00:25:09.040
But,<00:25:03.120> I<00:25:03.200> was<00:25:03.480> really<00:25:03.760> curious<00:25:04.200> around<00:25:04.960> where<00:25:05.480> are<00:25:05.800> you<00:25:05.960> going<00:25:06.920> to,<00:25:07.640> you<00:25:07.760> know,<00:25:07.880> find<00:25:08.200> new<00:25:08.280> information?

00:25:09.040 --> 00:25:12.480
What<00:25:09.240> research<00:25:09.720> are<00:25:09.840> you<00:25:10.000> reading?<00:25:10.560> What<00:25:10.800> articles<00:25:11.280> are<00:25:11.400> you<00:25:11.560> reading?

00:25:12.480 --> 00:25:17.520
I<00:25:12.600> would<00:25:12.800> let's<00:25:13.680> have<00:25:13.880> a<00:25:14.000> brief<00:25:14.720> I<00:25:14.800> have<00:25:15.080> a<00:25:15.240> little<00:25:15.600> bit<00:25:15.760> of<00:25:15.840> discussion<00:25:16.400> on<00:25:16.560> that<00:25:16.760> part.

00:25:17.520 --> 00:25:21.360
So,<00:25:17.680> AI<00:25:17.960> is<00:25:18.160> a<00:25:18.640> is<00:25:19.520> the<00:25:19.640> full<00:25:19.800> name<00:25:19.960> is<00:25:20.200> artificial<00:25:20.640> intelligence.

00:25:21.360 --> 00:25:24.600
So,<00:25:21.520> it's<00:25:21.680> a<00:25:21.760> very<00:25:22.160> subjective<00:25:23.360> word,<00:25:24.160> right?

00:25:24.600 --> 00:25:31.160
It's<00:25:24.760> not<00:25:25.120> I'll<00:25:25.240> strictly<00:25:25.640> define<00:25:26.080> what<00:25:26.200> is<00:25:26.440> AI,<00:25:26.640> but<00:25:27.040> it's<00:25:27.640> the<00:25:27.760> way<00:25:28.720> we<00:25:29.040> interpret<00:25:29.840> the<00:25:30.080> real<00:25:30.360> world,<00:25:30.920> right?

00:25:31.160 --> 00:25:38.200
The<00:25:31.240> traditional<00:25:31.680> machine<00:25:31.920> learning<00:25:32.520> that<00:25:32.880> I<00:25:32.920> would<00:25:33.080> say<00:25:33.320> the<00:25:33.480> AI<00:25:33.720> today<00:25:34.280> people<00:25:34.640> take<00:25:34.960> for<00:25:35.080> granted<00:25:35.560> the<00:25:35.680> AI<00:25:36.000> is<00:25:36.160> referring<00:25:36.720> to<00:25:37.360> deep<00:25:37.560> learning.

00:25:38.200 --> 00:25:41.240
Deep<00:25:38.440> learning<00:25:38.680> is<00:25:38.840> a<00:25:39.040> way<00:25:39.480> to<00:25:39.720> realize<00:25:40.200> actually,<00:25:41.000> right?

00:25:41.240 --> 00:25:49.360
The<00:25:41.360> deep<00:25:41.560> learning<00:25:41.800> basically<00:25:42.120> means<00:25:42.440> we<00:25:42.640> have<00:25:42.880> a<00:25:42.960> very<00:25:43.640> complicated<00:25:44.400> structure<00:25:44.880> of<00:25:45.080> network<00:25:45.600> new<00:25:45.880> networks<00:25:46.640> of<00:25:47.200> model,<00:25:47.960> and<00:25:48.200> then<00:25:48.440> we<00:25:49.000> learn<00:25:49.240> the

00:25:49.360 --> 00:25:57.760
knowledge<00:25:50.200> from<00:25:50.440> the<00:25:50.520> real<00:25:50.720> world<00:25:50.880> data<00:25:51.640> and<00:25:52.160> using<00:25:52.520> this<00:25:52.720> model<00:25:53.480> to<00:25:54.120> generate<00:25:54.560> something<00:25:55.120> we<00:25:55.280> call<00:25:55.920> like<00:25:56.480> artificial<00:25:56.960> intelligence.

00:25:57.760 --> 00:26:02.280
That's<00:25:58.000> basically<00:25:58.360> my<00:25:58.520> understanding<00:25:58.960> of<00:25:59.080> it.<00:25:59.560> So,<00:25:59.760> maybe<00:26:00.040> in<00:26:00.160> the<00:26:00.240> future<00:26:00.560> we<00:26:00.680> don't<00:26:00.920> use<00:26:01.120> deep<00:26:01.320> learning<00:26:01.640> to<00:26:01.760> do<00:26:01.920> AI.

00:26:02.280 --> 00:26:05.680
We<00:26:02.440> use<00:26:02.640> some<00:26:02.800> other<00:26:03.040> magical<00:26:03.880> thing<00:26:04.200> magical<00:26:04.840> tool<00:26:05.120> to<00:26:05.240> do<00:26:05.440> that.

00:26:05.680 --> 00:26:11.840
Maybe<00:26:05.960> that's<00:26:06.120> possible<00:26:06.440> in<00:26:06.520> the<00:26:06.600> future,<00:26:07.240> but<00:26:07.400> right<00:26:07.600> now<00:26:07.960> everything<00:26:08.840> like<00:26:09.200> works<00:26:09.440> amazing<00:26:10.160> is<00:26:10.320> built<00:26:10.680> with<00:26:10.920> deep<00:26:11.120> learning.

00:26:11.840 --> 00:26:18.800
All<00:26:11.880> right.<00:26:12.360> And<00:26:12.600> also<00:26:12.880> use<00:26:13.040> that<00:26:13.160> synthetic<00:26:13.760> structure<00:26:14.240> from<00:26:14.440> your<00:26:14.520> human<00:26:14.800> brain<00:26:15.080> because<00:26:15.360> your<00:26:15.480> brain<00:26:15.880> works<00:26:16.160> like<00:26:16.960> the<00:26:17.000> structure<00:26:17.400> of<00:26:17.480> your<00:26:17.600> brain<00:26:18.160> neurons<00:26:18.600> in<00:26:18.680> your

00:26:18.800 --> 00:26:21.000
brain<00:26:19.160> is<00:26:19.320> connected<00:26:19.840> in<00:26:20.040> a<00:26:20.080> similar<00:26:20.400> way.

00:26:21.000 --> 00:26:24.120
And<00:26:21.320> we<00:26:21.640> mimic<00:26:22.080> that<00:26:22.320> structure<00:26:22.880> you<00:26:23.080> in<00:26:23.280> deep<00:26:23.480> learning,<00:26:23.960> right?

00:26:24.120 --> 00:26:31.520
That's<00:26:24.400> my<00:26:24.560> understanding.<00:26:25.480> And<00:26:25.600> the<00:26:25.720> other<00:26:25.920> thing<00:26:26.120> is<00:26:26.280> about<00:26:26.760> the<00:26:27.160> craft<00:26:27.520> the<00:26:27.600> problem<00:26:28.160> over<00:26:28.320> the<00:26:28.440> craft<00:26:28.920> and<00:26:29.320> tackle<00:26:29.840> looking<00:26:30.200> to<00:26:30.360> different<00:26:30.640> problems<00:26:31.080> in<00:26:31.240> here.

00:26:31.520 --> 00:26:35.240
I<00:26:31.640> read<00:26:31.960> everything<00:26:32.360> basically.<00:26:32.960> I<00:26:33.120> like<00:26:33.360> to<00:26:33.520> read<00:26:33.840> I<00:26:33.960> like<00:26:34.400> articles.

00:26:35.240 --> 00:26:38.040
I<00:26:35.360> read<00:26:35.880> research<00:26:36.280> papers.<00:26:36.960> I<00:26:37.160> watch<00:26:37.480> videos.

00:26:38.040 --> 00:26:41.320
I<00:26:38.240> watch<00:26:38.920> Basically,<00:26:39.280> I<00:26:39.760> like<00:26:40.240> read<00:26:40.520> everything.

00:26:41.320 --> 00:26:46.520
I<00:26:41.440> don't<00:26:41.920> just<00:26:42.080> specifically<00:26:42.640> rely<00:26:43.040> on<00:26:43.320> on<00:26:43.480> research<00:26:43.840> papers<00:26:44.360> to<00:26:44.520> find<00:26:44.800> my<00:26:44.960> next<00:26:45.480> research<00:26:45.800> topic.

00:26:46.520 --> 00:26:50.440
But,<00:26:46.720> they<00:26:47.120> also<00:26:47.440> I<00:26:47.560> read<00:26:47.800> different<00:26:48.160> things<00:26:48.520> they<00:26:48.720> serve<00:26:49.040> a<00:26:49.120> different<00:26:49.480> purpose.

00:26:50.440 --> 00:26:58.040
And<00:26:51.160> basically,<00:26:51.600> I<00:26:51.720> find<00:26:52.160> problems<00:26:52.880> by<00:26:53.120> reading<00:26:54.040> newspapers,<00:26:55.560> watching<00:26:55.880> videos,<00:26:56.840> and<00:26:57.000> talk<00:26:57.240> to<00:26:57.360> people.

00:26:58.040 --> 00:27:03.320
It's<00:26:58.280> especially<00:26:58.840> talk<00:26:59.080> to<00:26:59.160> people<00:26:59.480> in<00:26:59.600> different<00:26:59.920> domain,<00:27:00.480> which<00:27:00.640> is<00:27:00.760> very<00:27:01.280> helpful<00:27:02.120> to<00:27:02.240> find<00:27:02.520> a<00:27:02.600> real<00:27:02.840> problem.

00:27:03.320 --> 00:27:09.600
Just<00:27:03.560> like<00:27:03.880> how<00:27:04.040> do<00:27:04.200> you<00:27:04.480> how<00:27:04.720> we<00:27:04.840> did<00:27:05.360> decided<00:27:05.960> to<00:27:06.360> tackle<00:27:06.600> the<00:27:06.680> problem<00:27:07.080> in<00:27:07.200> the<00:27:07.760> cardiovascular<00:27:08.480> disease<00:27:08.960> domain.

00:27:09.600 --> 00:27:17.840
And<00:27:10.080> once<00:27:10.320> I<00:27:10.440> have<00:27:10.680> the<00:27:10.800> problem,<00:27:11.600> then<00:27:12.000> I<00:27:12.200> will<00:27:12.360> refer<00:27:12.720> to<00:27:13.120> the<00:27:13.560> research<00:27:13.960> papers<00:27:14.760> and<00:27:15.200> what<00:27:15.360> we<00:27:15.440> have<00:27:15.640> done<00:27:15.840> before<00:27:16.600> or<00:27:16.840> models<00:27:17.320> we<00:27:17.440> have<00:27:17.640> there

00:27:17.840 --> 00:27:20.480
in<00:27:18.080> from<00:27:18.320> research<00:27:18.680> papers.<00:27:19.360> And<00:27:19.520> then<00:27:19.680> solve<00:27:19.920> the<00:27:20.000> problem.

00:27:20.480 --> 00:27:22.600
So,<00:27:20.640> you<00:27:20.840> can<00:27:21.120> use<00:27:21.240> a<00:27:21.280> different<00:27:22.120> stage.

00:27:22.600 --> 00:27:29.920
Find<00:27:22.840> the<00:27:22.880> problems<00:27:23.640> across<00:27:24.080> the<00:27:24.160> broader<00:27:24.480> domain<00:27:25.000> and<00:27:25.280> tackle<00:27:25.560> the<00:27:25.680> problem<00:27:26.520> in<00:27:26.640> your<00:27:26.760> specific<00:27:27.280> knowledge<00:27:27.960> using<00:27:28.200> a<00:27:28.280> specific<00:27:29.000> technology.

00:27:29.920 --> 00:27:37.760
Yeah,<00:27:30.080> so<00:27:30.400> how<00:27:30.560> we<00:27:30.680> do<00:27:30.880> things<00:27:31.360> and<00:27:31.800> I<00:27:31.880> believe<00:27:32.680> I<00:27:32.800> would<00:27:32.960> say<00:27:33.080> my<00:27:33.240> research<00:27:33.680> is<00:27:34.000> like<00:27:34.320> application<00:27:34.920> oriented<00:27:35.560> and<00:27:35.760> in<00:27:35.960> some<00:27:36.160> case<00:27:36.480> problem<00:27:37.000> oriented.

00:27:37.760 --> 00:27:40.640
So,<00:27:38.160> I<00:27:38.240> try<00:27:38.440> to<00:27:38.600> solve<00:27:38.840> problem,<00:27:39.280> not<00:27:39.520> to<00:27:39.600> make<00:27:39.800> a<00:27:39.840> problem.

00:27:40.640 --> 00:27:43.520
Just<00:27:41.040> Yeah,<00:27:41.240> that's<00:27:41.480> my<00:27:42.000> my<00:27:42.120> understanding<00:27:42.880> of<00:27:43.000> it.

00:27:43.520 --> 00:27:46.400
That<00:27:43.600> was<00:27:44.200> the<00:27:44.400> end<00:27:44.640> piece<00:27:44.880> and<00:27:44.960> that<00:27:45.080> was<00:27:45.240> really<00:27:45.480> great,<00:27:45.760> right?

00:27:46.400 --> 00:27:54.360
A<00:27:46.440> lot<00:27:46.600> of<00:27:46.680> times<00:27:46.920> we<00:27:47.080> either<00:27:47.320> imagine<00:27:47.840> a<00:27:47.880> problem<00:27:48.600> or<00:27:48.840> we<00:27:49.040> want<00:27:49.280> to<00:27:49.400> make<00:27:49.680> up<00:27:49.800> a<00:27:49.880> problem,<00:27:50.640> but<00:27:50.800> like<00:27:51.040> actually<00:27:51.440> solving<00:27:51.880> a<00:27:51.960> real<00:27:52.240> problem<00:27:53.120> a<00:27:53.200> lot<00:27:53.400> more<00:27:53.560> difficult.

00:27:54.360 --> 00:27:59.280
Yes,<00:27:55.000> and<00:27:55.120> because<00:27:55.480> the<00:27:55.560> real<00:27:55.760> problem<00:27:56.160> is<00:27:56.200> hard<00:27:56.440> to<00:27:56.520> solve,<00:27:57.120> to<00:27:57.240> be<00:27:57.360> honest,<00:27:58.200> it's<00:27:58.400> really<00:27:58.680> hard.

00:27:59.280 --> 00:28:06.600
But<00:27:59.640> although<00:27:59.880> it's<00:28:00.040> hard,<00:28:00.320> we<00:28:00.440> are<00:28:00.520> trying<00:28:00.920> to<00:28:01.320> if<00:28:02.000> it<00:28:02.240> is<00:28:02.680> worth<00:28:02.920> make<00:28:03.240> worth<00:28:03.520> doing,<00:28:04.240> even<00:28:04.480> if<00:28:04.680> you<00:28:04.840> just<00:28:05.080> make<00:28:05.240> a<00:28:05.320> dent<00:28:05.600> on<00:28:05.760> it,<00:28:06.080> right?

00:28:06.600 --> 00:28:13.360
It's<00:28:06.880> because<00:28:07.160> it's<00:28:07.240> a<00:28:07.280> real<00:28:07.480> problem.<00:28:08.160> Okay,<00:28:08.400> so<00:28:08.640> I<00:28:08.720> love<00:28:08.880> that<00:28:09.000> you<00:28:09.080> said<00:28:09.280> just<00:28:09.400> make<00:28:09.560> a<00:28:09.640> dent<00:28:09.920> because<00:28:11.200> AI<00:28:11.520> has<00:28:11.640> been<00:28:11.760> around<00:28:12.080> for<00:28:12.200> a<00:28:12.240> while,<00:28:12.960> right?

00:28:13.360 --> 00:28:17.560
You<00:28:13.400> go<00:28:13.520> through<00:28:13.680> the<00:28:13.760> history<00:28:14.600> and<00:28:14.760> everyone's<00:28:15.480> been<00:28:15.880> making<00:28:16.240> a<00:28:16.320> dent<00:28:16.680> on<00:28:16.880> it,<00:28:17.200> right?

00:28:17.560 --> 00:28:25.920
As<00:28:17.680> we<00:28:17.800> wrap<00:28:18.080> this<00:28:18.360> up,<00:28:19.000> there's<00:28:19.160> going<00:28:19.280> to<00:28:19.360> be<00:28:19.400> a<00:28:19.480> great<00:28:19.720> conference<00:28:20.640> Perk,<00:28:21.160> the<00:28:21.280> Practice<00:28:21.960> and<00:28:22.760> Experience<00:28:23.520> in<00:28:23.680> Advanced<00:28:24.200> Research<00:28:24.720> and<00:28:24.880> Computing<00:28:25.800> in

00:28:25.920 --> 00:28:29.600
Minneapolis.<00:28:27.120> I<00:28:27.200> think<00:28:27.400> it's<00:28:27.520> next<00:28:27.760> month,<00:28:28.240> so<00:28:28.360> it's<00:28:28.480> coming<00:28:28.680> up<00:28:28.800> fast.

00:28:29.600 --> 00:28:33.680
I<00:28:29.760> always<00:28:30.000> love<00:28:30.160> conferences.<00:28:30.760> I<00:28:30.800> think<00:28:31.080> this<00:28:31.280> is<00:28:31.360> a<00:28:31.400> great<00:28:31.680> way<00:28:31.960> to<00:28:32.160> generate<00:28:32.640> serendipity.

00:28:33.680 --> 00:28:37.360
Dell's<00:28:34.040> going<00:28:34.200> to<00:28:34.280> be<00:28:34.440> there.<00:28:35.160> I<00:28:35.200> think<00:28:35.440> Pitt's<00:28:35.680> going<00:28:35.800> to<00:28:35.880> have<00:28:36.080> a<00:28:36.160> booth<00:28:36.480> there.

00:28:37.360 --> 00:28:43.240
As<00:28:37.760> we<00:28:37.920> round<00:28:38.160> out<00:28:38.280> the<00:28:38.360> podcast,<00:28:39.160> when<00:28:39.360> you<00:28:39.520> go<00:28:39.720> to<00:28:39.840> conferences<00:28:40.520> like<00:28:40.760> this,<00:28:41.520> Matt,<00:28:41.880> you're<00:28:41.960> coming<00:28:42.200> from<00:28:42.320> the<00:28:42.440> IT<00:28:42.680> side.

00:28:43.240 --> 00:28:46.640
Pengfei,<00:28:43.600> you're<00:28:43.720> coming<00:28:43.960> from<00:28:44.080> the<00:28:44.160> research<00:28:44.560> side.<00:28:45.320> What<00:28:45.480> are<00:28:45.600> you<00:28:45.720> looking<00:28:46.000> to<00:28:46.120> grab?

00:28:46.640 --> 00:28:49.320
Is<00:28:46.760> it<00:28:46.920> new<00:28:47.080> information?<00:28:48.160> Is<00:28:48.320> it<00:28:48.440> connection?

00:28:49.320 --> 00:28:53.960
Are<00:28:49.440> you<00:28:49.560> trying<00:28:49.920> to<00:28:50.000> figure<00:28:50.240> out<00:28:50.360> what<00:28:50.600> other<00:28:50.840> colleagues<00:28:51.400> are<00:28:51.520> doing<00:28:52.120> at<00:28:52.280> other<00:28:52.520> universities?

00:28:53.960 --> 00:28:56.640
And<00:28:54.080> then<00:28:54.200> Adrian,<00:28:54.520> same<00:28:54.640> thing<00:28:54.800> for<00:28:54.920> you.<00:28:55.120> What<00:28:55.280> are<00:28:55.360> you<00:28:55.480> looking<00:28:55.800> for?

00:28:56.640 --> 00:28:59.800
And<00:28:56.760> Matt,<00:28:57.080> we'll<00:28:57.200> kick<00:28:57.400> off<00:28:57.560> with<00:28:57.760> you<00:28:58.000> and<00:28:58.160> then<00:28:58.440> we'll<00:28:58.560> take<00:28:58.760> it<00:28:58.920> we'll<00:28:59.080> take<00:28:59.240> it<00:28:59.320> home.

00:28:59.800 --> 00:29:08.920
We<00:28:59.960> are<00:29:00.240> trying<00:29:00.640> to<00:29:00.800> collect<00:29:01.240> like<00:29:01.400> new<00:29:01.600> trends<00:29:02.320> and<00:29:02.720> bring<00:29:03.280> innovation<00:29:04.160> home,<00:29:04.920> but<00:29:05.120> also<00:29:06.080> to<00:29:06.240> capture<00:29:06.720> more<00:29:07.200> subtle<00:29:08.160> things

00:29:08.920 --> 00:29:13.240
like<00:29:09.480> maybe<00:29:10.000> the<00:29:10.120> general<00:29:10.440> perception,<00:29:11.520> sentiment<00:29:12.160> about<00:29:12.480> things.

00:29:13.240 --> 00:29:21.880
I<00:29:13.320> think<00:29:13.560> it<00:29:13.960> you<00:29:14.080> can<00:29:14.240> get<00:29:14.440> a<00:29:14.520> lot<00:29:15.200> of<00:29:15.840> this<00:29:16.040> kind<00:29:16.240> of<00:29:16.360> events<00:29:17.360> without<00:29:18.000> just<00:29:18.800> observing<00:29:19.280> what's<00:29:19.560> on<00:29:19.720> the<00:29:19.800> surface,<00:29:20.320> all<00:29:20.480> that<00:29:20.760> behind<00:29:21.520> not

00:29:21.880 --> 00:29:31.240
looking<00:29:22.320> into<00:29:22.760> just<00:29:23.000> like<00:29:23.160> the<00:29:23.280> data,<00:29:23.880> the<00:29:24.000> flashy<00:29:24.480> PowerPoints,<00:29:25.560> but<00:29:25.720> also<00:29:26.240> what<00:29:26.440> are<00:29:26.560> actually<00:29:26.920> people<00:29:27.280> talking<00:29:27.840> about<00:29:28.480> when<00:29:28.720> they<00:29:28.960> leave<00:29:29.560> the<00:29:29.800> the<00:29:29.880> presentation.

00:29:31.240 --> 00:29:34.680
This<00:29:31.400> kind<00:29:31.560> of<00:29:31.640> thing<00:29:31.840> is<00:29:32.360> really<00:29:32.720> what<00:29:33.320> interests<00:29:33.720> me<00:29:33.920> the<00:29:34.040> most.

00:29:34.680 --> 00:29:39.640
Peng<00:29:34.880> Fei,<00:29:35.120> what<00:29:35.280> conferences<00:29:36.320> when<00:29:36.480> you<00:29:36.560> go<00:29:36.680> to<00:29:36.800> a<00:29:36.880> conference,<00:29:37.360> what<00:29:37.520> are<00:29:37.600> you<00:29:37.720> looking<00:29:37.960> to<00:29:38.080> learn<00:29:38.400> or<00:29:38.520> glean<00:29:38.920> from<00:29:39.080> there?

00:29:39.640 --> 00:29:42.600
I<00:29:39.760> was<00:29:40.200> I<00:29:40.360> went<00:29:40.560> to<00:29:40.720> two<00:29:40.960> different<00:29:41.400> kind<00:29:41.640> of<00:29:41.760> conferences.

00:29:42.600 --> 00:29:44.720
And<00:29:42.720> normally<00:29:43.000> I<00:29:43.080> went<00:29:43.280> to<00:29:43.400> a<00:29:43.600> academia<00:29:44.080> conference,<00:29:44.520> right?

00:29:44.720 --> 00:29:48.600
We<00:29:45.000> there's<00:29:45.360> a<00:29:45.480> presentation<00:29:46.080> about<00:29:46.360> new<00:29:46.560> technology,<00:29:47.320> new<00:29:47.600> research<00:29:47.960> part.

00:29:48.600 --> 00:29:56.520
For<00:29:48.720> that<00:29:48.920> kind<00:29:49.160> conference,<00:29:49.560> basically<00:29:50.040> what<00:29:50.280> I<00:29:50.400> do<00:29:50.600> is<00:29:50.760> that,<00:29:51.400> okay,<00:29:51.960> because<00:29:52.520> although<00:29:52.800> I'm<00:29:53.000> working<00:29:53.280> in<00:29:53.400> this<00:29:53.560> area,<00:29:53.880> AIoT<00:29:54.520> area,<00:29:54.800> but<00:29:55.320> that<00:29:55.600> AI<00:29:55.840> is<00:29:56.080> we<00:29:56.160> have<00:29:56.360> so

00:29:56.520 --> 00:29:59.280
many<00:29:56.800> different<00:29:57.440> topics<00:29:58.080> and<00:29:58.240> different<00:29:58.520> technology<00:29:59.000> in<00:29:59.080> there.

00:29:59.280 --> 00:30:03.480
I<00:29:59.360> don't<00:29:59.600> know<00:29:59.800> everything.<00:30:00.640> So,<00:30:01.240> I<00:30:01.360> just<00:30:01.600> want<00:30:01.760> to<00:30:01.880> show<00:30:02.080> how<00:30:02.240> people<00:30:02.600> play<00:30:02.840> with<00:30:03.080> it.

00:30:03.480 --> 00:30:10.960
For<00:30:03.600> example,<00:30:04.200> how<00:30:04.360> do<00:30:04.520> you<00:30:04.640> play<00:30:05.000> you<00:30:05.120> have<00:30:05.280> large<00:30:05.520> language<00:30:05.840> model,<00:30:06.640> which<00:30:06.840> is<00:30:06.960> a<00:30:07.000> very<00:30:07.320> big,<00:30:08.000> and<00:30:08.240> you<00:30:08.360> have<00:30:08.520> a<00:30:08.600> small<00:30:08.880> model<00:30:09.320> running<00:30:09.640> on<00:30:09.800> your<00:30:09.920> mobile<00:30:10.200> device.

00:30:10.960 --> 00:30:13.520
And<00:30:11.080> now<00:30:11.360> is<00:30:11.600> there<00:30:11.760> a<00:30:11.840> way,<00:30:12.120> for<00:30:12.240> example,<00:30:12.720> to<00:30:12.840> combine<00:30:13.160> the<00:30:13.280> two?

00:30:13.520 --> 00:30:18.120
Basically<00:30:13.920> I<00:30:14.160> want<00:30:14.360> to<00:30:14.920> see<00:30:15.040> how<00:30:15.280> people<00:30:15.680> play<00:30:15.920> with<00:30:16.120> it<00:30:16.560> with<00:30:16.760> these<00:30:17.000> technologies.

00:30:18.120 --> 00:30:27.280
And<00:30:18.840> the<00:30:19.000> other<00:30:19.160> part<00:30:19.600> is<00:30:19.960> different<00:30:20.280> kind<00:30:20.440> of<00:30:20.600> conference<00:30:21.120> that<00:30:21.360> is<00:30:21.520> a<00:30:21.560> showcase<00:30:22.160> what<00:30:23.200> is<00:30:23.480> a<00:30:23.960> broader<00:30:24.480> community<00:30:25.520> in<00:30:25.880> industry,<00:30:26.720> different

00:30:27.280 --> 00:30:30.880
departments,<00:30:28.120> or<00:30:28.320> maybe<00:30:28.600> some<00:30:28.800> government<00:30:29.560> or<00:30:29.800> a<00:30:29.880> research<00:30:30.280> part.

00:30:30.880 --> 00:30:36.360
That<00:30:31.520> for<00:30:31.680> that<00:30:31.880> part<00:30:32.160> I<00:30:32.280> was<00:30:32.600> most<00:30:32.800> of<00:30:32.920> time<00:30:33.280> I<00:30:33.400> was<00:30:33.640> learning<00:30:34.440> what<00:30:34.720> are<00:30:34.840> the<00:30:35.000> real<00:30:35.200> problems<00:30:35.840> there.

00:30:36.360 --> 00:30:39.360
And<00:30:36.640> talk<00:30:36.880> to<00:30:37.000> them<00:30:37.760> to<00:30:38.200> gather<00:30:38.520> some<00:30:38.760> details.

00:30:39.360 --> 00:30:46.000
I<00:30:39.440> believe<00:30:39.760> details<00:30:40.200> is<00:30:40.320> a<00:30:40.400> key.<00:30:41.040> When<00:30:41.240> you<00:30:41.360> see<00:30:41.520> the<00:30:41.720> detail,<00:30:42.480> then<00:30:42.760> you<00:30:42.880> know,<00:30:43.040> okay,<00:30:43.680> from<00:30:44.320> you<00:30:44.440> see<00:30:44.600> the<00:30:44.720> problem<00:30:45.240> is<00:30:45.400> a<00:30:45.440> big<00:30:45.640> problem.

00:30:46.000 --> 00:30:54.040
It's<00:30:46.120> a<00:30:46.200> problem.<00:30:46.560> But<00:30:47.040> from<00:30:47.280> my<00:30:47.480> perspective,<00:30:48.200> I<00:30:48.280> want<00:30:48.520> to<00:30:48.640> solve<00:30:48.920> somehow<00:30:49.320> solve<00:30:49.560> the<00:30:49.640> problem<00:30:50.600> at<00:30:50.720> least<00:30:50.960> push<00:30:51.200> forward<00:30:51.520> the<00:30:51.600> problem<00:30:52.320> a<00:30:52.400> little<00:30:52.680> bit<00:30:52.920> using<00:30:53.200> technology.

00:30:54.040 --> 00:30:59.360
Then<00:30:54.240> you<00:30:54.320> get<00:30:54.480> to<00:30:54.560> the<00:30:54.680> details.<00:30:55.480> And<00:30:55.720> then<00:30:55.920> when<00:30:56.040> you<00:30:56.160> see<00:30:56.320> the<00:30:56.440> details,<00:30:57.200> basically<00:30:57.520> you<00:30:57.560> can<00:30:57.720> tell,<00:30:58.000> okay,<00:30:58.280> whether<00:30:58.560> I<00:30:58.640> can<00:30:58.800> do<00:30:58.960> it.

00:30:59.360 --> 00:31:06.160
Adrian,<00:30:59.800> as<00:30:59.920> you<00:31:00.040> close<00:31:00.280> this<00:31:00.480> out,<00:31:00.760> when<00:31:00.920> you<00:31:01.000> go<00:31:01.080> to<00:31:01.200> conferences,<00:31:01.960> what<00:31:02.120> are<00:31:02.200> you<00:31:02.320> looking<00:31:02.600> for,<00:31:02.880> whether<00:31:03.160> it's<00:31:03.280> at<00:31:03.400> Educause<00:31:04.120> or<00:31:04.280> more<00:31:04.520> of<00:31:04.600> an<00:31:04.680> academic<00:31:05.160> conference,

00:31:06.160 --> 00:31:14.200
what<00:31:06.360> are<00:31:06.440> you<00:31:06.560> looking<00:31:06.840> to<00:31:06.960> glean?<00:31:07.560> To<00:31:07.680> answer<00:31:08.000> that<00:31:08.240> question,<00:31:08.800> I<00:31:08.880> have<00:31:09.160> to<00:31:09.520> call<00:31:09.960> Matt<00:31:10.320> and<00:31:10.440> Peng<00:31:10.680> Fei<00:31:10.840> out<00:31:10.960> a<00:31:11.000> little<00:31:11.280> bit<00:31:11.600> because<00:31:12.280> a<00:31:12.400> lot<00:31:12.960> of<00:31:13.120> researchers<00:31:14.040> and

00:31:14.200 --> 00:31:17.320
departments<00:31:14.800> come<00:31:15.040> to<00:31:15.120> conferences<00:31:16.240> looking<00:31:16.520> for<00:31:16.680> funding.

00:31:17.320 --> 00:31:19.560
So,<00:31:18.000> yes,<00:31:18.320> you're<00:31:18.440> looking<00:31:18.760> for<00:31:18.920> ideas.

00:31:19.560 --> 00:31:28.160
Yes,<00:31:19.840> you're<00:31:19.960> looking<00:31:20.320> to<00:31:20.440> test<00:31:20.760> your<00:31:20.920> own<00:31:21.200> and<00:31:21.320> to<00:31:21.440> showcase<00:31:21.920> things,<00:31:22.600> but<00:31:22.720> that's<00:31:23.440> some<00:31:23.760> of<00:31:24.400> why<00:31:24.680> I<00:31:24.760> think<00:31:25.520> we're<00:31:25.720> there<00:31:26.280> in<00:31:26.480> person<00:31:27.200> is<00:31:27.480> to<00:31:27.720> build

00:31:28.160 --> 00:31:35.440
a<00:31:28.200> human<00:31:28.560> connection<00:31:29.120> with<00:31:29.280> our<00:31:29.400> customers<00:31:30.040> because<00:31:30.360> it's<00:31:30.520> very<00:31:30.720> difficult,<00:31:31.640> especially<00:31:32.040> in<00:31:32.080> these<00:31:32.200> budget-constrained<00:31:32.880> environments,<00:31:33.560> to<00:31:33.920> to<00:31:34.160> know<00:31:34.840> who<00:31:35.080> are<00:31:35.280> your

00:31:35.440 --> 00:31:38.440
partners,<00:31:35.920> where<00:31:36.120> might<00:31:36.400> I<00:31:36.480> go,<00:31:36.800> who<00:31:37.040> has<00:31:37.360> resources.

00:31:38.440 --> 00:31:45.560
And<00:31:38.600> so,<00:31:38.720> if<00:31:38.880> you<00:31:39.000> could<00:31:39.240> strike<00:31:40.000> up<00:31:40.080> a<00:31:40.120> conversation<00:31:40.720> because<00:31:41.040> the<00:31:41.120> person<00:31:41.520> sitting<00:31:41.800> next<00:31:42.120> to<00:31:42.200> you<00:31:42.360> and<00:31:42.560> watching<00:31:43.000> that<00:31:43.200> presenter<00:31:43.640> has<00:31:44.080> like-minded<00:31:44.920> interests<00:31:45.400> as

00:31:45.560 --> 00:31:54.080
you,<00:31:46.160> it<00:31:46.880> reduces<00:31:47.400> some<00:31:47.600> of<00:31:47.760> those<00:31:48.000> barriers<00:31:48.760> to<00:31:49.040> get<00:31:49.280> to<00:31:49.360> the<00:31:49.440> very<00:31:49.640> sensitive<00:31:50.000> topics<00:31:50.440> like<00:31:50.840> I'm<00:31:51.160> looking<00:31:51.440> for<00:31:51.680> XYZ<00:31:52.240> resources,<00:31:52.800> whether<00:31:53.040> it's<00:31:53.480> building<00:31:53.800> human

00:31:54.080 --> 00:32:01.560
capacity,<00:31:54.720> like<00:31:54.880> you're<00:31:55.000> building<00:31:55.320> out<00:31:55.440> a<00:31:55.520> team<00:31:55.960> and<00:31:56.080> you're<00:31:56.240> looking<00:31:56.560> maybe<00:31:56.840> for<00:31:57.440> engineers<00:31:58.120> from<00:31:58.320> a<00:31:58.360> partner<00:31:58.760> like<00:31:59.000> Dell<00:31:59.320> to<00:31:59.480> come<00:31:59.680> on<00:31:59.880> site<00:32:00.240> and<00:32:00.400> be<00:32:00.520> involved,<00:32:01.280> like

00:32:01.560 --> 00:32:04.360
physically<00:32:02.080> in<00:32:02.200> a<00:32:02.280> location<00:32:02.880> with<00:32:03.000> you<00:32:03.120> because<00:32:03.400> that<00:32:03.560> is<00:32:03.680> something<00:32:04.040> we<00:32:04.160> do.

00:32:04.360 --> 00:32:12.080
We<00:32:04.480> do<00:32:04.640> that<00:32:04.800> through<00:32:04.960> our<00:32:05.120> office<00:32:05.480> of<00:32:05.600> the<00:32:05.800> CTO,<00:32:06.720> where<00:32:06.840> we<00:32:06.960> have<00:32:07.120> embedded<00:32:07.480> engineers<00:32:08.040> on<00:32:08.160> projects<00:32:08.760> like<00:32:08.880> shoulder<00:32:09.200> to<00:32:09.320> shoulder<00:32:09.680> doing<00:32:10.200> co-research<00:32:11.120> creation<00:32:11.680> together,

00:32:12.080 --> 00:32:19.360
intellectual<00:32:12.600> property<00:32:12.960> development<00:32:13.440> together,<00:32:14.200> or<00:32:14.400> it<00:32:14.480> might<00:32:14.640> be<00:32:14.800> that<00:32:14.960> you're<00:32:15.120> looking<00:32:15.440> for<00:32:16.120> physical<00:32:16.480> resources,<00:32:17.000> like<00:32:17.200> you<00:32:17.280> need<00:32:17.520> devices<00:32:18.080> or<00:32:18.240> hardware<00:32:18.800> or<00:32:18.920> software

00:32:19.360 --> 00:32:27.520
licenses.<00:32:20.000> And<00:32:20.160> so,<00:32:20.720> coming<00:32:21.000> into<00:32:21.240> a<00:32:21.320> space<00:32:21.720> where<00:32:21.840> you<00:32:22.040> have<00:32:22.400> a<00:32:22.480> lot<00:32:22.840> of<00:32:23.000> different<00:32:23.480> technology<00:32:24.680> vendors<00:32:25.120> and<00:32:25.240> partners<00:32:25.720> there<00:32:26.240> and<00:32:26.600> asking<00:32:26.960> them<00:32:27.120> about<00:32:27.440> the

00:32:27.520 --> 00:32:35.200
affordances<00:32:28.200> of<00:32:28.400> one<00:32:28.800> solution<00:32:29.320> to<00:32:29.480> another<00:32:29.920> and<00:32:30.040> you<00:32:30.160> can<00:32:30.280> compare<00:32:30.720> them<00:32:31.320> literally<00:32:31.920> they're<00:32:32.080> next<00:32:32.400> to<00:32:32.520> each<00:32:32.720> other,<00:32:32.960> so<00:32:33.080> you<00:32:33.200> can<00:32:33.360> really<00:32:33.600> have<00:32:33.800> some<00:32:34.000> very<00:32:34.200> deep<00:32:34.480> conversations,

00:32:35.200 --> 00:32:41.840
very<00:32:35.360> deep<00:32:35.640> technical<00:32:36.160> conversations.<00:32:37.160> And<00:32:37.240> then<00:32:37.360> the<00:32:37.440> thing<00:32:37.680> I<00:32:37.760> like,<00:32:38.120> and<00:32:38.200> it's<00:32:38.360> the<00:32:38.400> most<00:32:38.680> fun<00:32:38.920> in<00:32:39.040> my<00:32:39.200> job<00:32:39.480> and<00:32:39.600> it's<00:32:39.720> where<00:32:39.960> this<00:32:40.200> acceleration<00:32:40.960> pilot<00:32:41.320> generated

00:32:41.840 --> 00:32:45.960
from<00:32:42.080> is<00:32:42.520> there<00:32:42.680> aren't<00:32:43.200> as<00:32:43.360> many<00:32:43.640> feedback<00:32:44.320> back<00:32:44.640> loops<00:32:44.880> as<00:32:45.040> I<00:32:45.160> wish<00:32:45.400> we<00:32:45.600> had.

00:32:45.960 --> 00:32:54.240
And<00:32:46.080> so<00:32:46.240> we<00:32:46.400> have<00:32:46.640> advisory<00:32:47.120> boards<00:32:47.520> and<00:32:47.680> steering<00:32:48.040> committees<00:32:48.640> and<00:32:49.120> we<00:32:49.280> participate<00:32:49.880> with<00:32:50.040> our<00:32:50.200> high<00:32:50.400> ed<00:32:50.600> customers<00:32:51.400> on<00:32:51.640> those<00:32:52.160> where<00:32:52.760> we're<00:32:52.880> there<00:32:53.440> on<00:32:53.640> campus<00:32:54.120> or

00:32:54.240 --> 00:33:01.800
meeting<00:32:54.560> on<00:32:54.680> a<00:32:54.720> regular<00:32:55.160> cadence<00:32:55.640> to<00:32:55.760> talk<00:32:55.960> about<00:32:56.200> these<00:32:56.360> very<00:32:56.600> challenging<00:32:57.400> issues<00:32:57.920> and<00:32:58.280> technology<00:32:58.840> developments<00:32:59.560> and<00:33:00.080> experimental<00:33:00.880> ideas.

00:33:01.800 --> 00:33:05.480
Or<00:33:02.200> it's<00:33:02.480> vice<00:33:02.720> versa<00:33:03.000> where<00:33:03.160> we<00:33:03.360> want<00:33:03.560> you<00:33:03.960> to<00:33:04.000> partner<00:33:04.200> with<00:33:04.360> us<00:33:04.560> and<00:33:04.680> spend<00:33:05.040> time<00:33:05.160> with<00:33:05.320> us.

00:33:05.480 --> 00:33:09.080
And<00:33:05.600> so<00:33:05.720> a<00:33:05.800> conference<00:33:06.200> gives<00:33:06.400> a<00:33:06.440> lot<00:33:06.600> of<00:33:06.760> foray<00:33:07.160> into<00:33:08.040> the<00:33:08.120> army<00:33:08.440> of<00:33:08.560> the<00:33:08.680> willing.

00:33:09.080 --> 00:33:15.840
Who<00:33:09.240> would<00:33:09.400> like<00:33:09.640> to<00:33:09.720> be<00:33:09.880> on<00:33:10.000> these<00:33:10.240> boards<00:33:10.680> or<00:33:10.760> these<00:33:11.000> committees<00:33:11.520> or<00:33:11.640> these<00:33:11.840> steering<00:33:12.280> groups<00:33:12.800> and<00:33:13.200> what<00:33:13.400> might<00:33:13.560> our<00:33:13.680> work<00:33:13.880> product<00:33:14.280> look<00:33:14.520> like<00:33:14.840> and<00:33:15.000> how<00:33:15.160> can<00:33:15.320> we<00:33:15.440> create

00:33:15.840 --> 00:33:19.640
a<00:33:15.880> community<00:33:16.400> of<00:33:16.520> practice<00:33:16.960> together?<00:33:17.680> My<00:33:17.800> background<00:33:18.240> is<00:33:18.520> in<00:33:18.960> academics.

00:33:19.640 --> 00:33:27.360
I<00:33:19.760> spent<00:33:20.200> 10<00:33:20.440> years<00:33:20.720> at<00:33:20.840> an<00:33:20.960> R1<00:33:21.360> institution<00:33:22.320> doing<00:33:22.600> just<00:33:22.800> that,<00:33:23.040> like<00:33:23.240> looking<00:33:23.640> for<00:33:24.000> who<00:33:24.360> were<00:33:24.560> my<00:33:24.760> allies,<00:33:25.280> who<00:33:25.520> were<00:33:25.680> the<00:33:25.800> people<00:33:26.040> that<00:33:26.200> were<00:33:26.400> interested<00:33:26.880> in<00:33:26.960> the<00:33:27.040> same

00:33:27.360 --> 00:33:29.360
types<00:33:27.600> of<00:33:27.720> problems<00:33:28.120> I<00:33:28.240> was<00:33:28.400> interested<00:33:28.920> in.

00:33:29.360 --> 00:33:35.680
And<00:33:29.480> conferences<00:33:30.080> are<00:33:30.160> a<00:33:30.200> good<00:33:30.400> way<00:33:30.480> to<00:33:30.600> align<00:33:30.960> yourself<00:33:31.840> with<00:33:32.040> others<00:33:32.360> that<00:33:32.520> want<00:33:32.640> to<00:33:32.720> do<00:33:32.840> the<00:33:32.960> same<00:33:33.200> kind<00:33:33.440> of<00:33:33.520> difficult<00:33:34.040> work<00:33:34.320> and<00:33:34.440> really<00:33:34.640> get<00:33:34.800> in<00:33:34.920> there<00:33:35.160> with<00:33:35.480> you.

00:33:35.680 --> 00:33:43.440
And<00:33:35.880> so<00:33:36.160> that's<00:33:36.320> the<00:33:36.360> benefit<00:33:36.920> I<00:33:36.960> have<00:33:37.040> seen<00:33:37.680> with<00:33:37.840> both<00:33:38.040> Peng<00:33:38.240> Fei<00:33:38.400> and<00:33:38.560> Matt<00:33:38.960> and<00:33:39.280> the<00:33:39.440> appetite<00:33:39.880> at<00:33:39.960> University<00:33:40.440> of<00:33:40.520> Pittsburgh<00:33:41.000> was<00:33:41.680> they<00:33:41.840> wanted<00:33:42.240> us<00:33:42.480> to<00:33:42.800> create<00:33:43.360> a

00:33:43.440 --> 00:33:46.600
regular<00:33:43.920> cadence<00:33:44.440> to<00:33:44.560> spend<00:33:44.880> time<00:33:45.120> together<00:33:45.480> to<00:33:45.640> really<00:33:45.840> get<00:33:46.040> to<00:33:46.160> know<00:33:46.360> them.

00:33:46.600 --> 00:33:50.800
And<00:33:46.920> in<00:33:47.080> doing<00:33:47.440> that,<00:33:48.040> now<00:33:48.240> you're<00:33:48.400> sharing<00:33:48.760> a<00:33:48.840> risk<00:33:49.280> as<00:33:49.440> much<00:33:49.640> as<00:33:49.760> you're<00:33:49.880> sharing<00:33:50.280> a<00:33:50.320> reward.

00:33:50.800 --> 00:33:56.280
And<00:33:51.000> I<00:33:51.160> feel<00:33:51.400> like<00:33:51.640> for<00:33:51.760> especially<00:33:52.240> what<00:33:52.440> Peng<00:33:52.640> Fei<00:33:52.840> is<00:33:53.000> studying,<00:33:53.840> like<00:33:54.000> that's<00:33:54.240> a<00:33:54.320> reward<00:33:55.160> for<00:33:55.320> society<00:33:55.800> at<00:33:55.920> large.

00:33:56.280 --> 00:33:59.440
Like<00:33:56.480> when<00:33:56.680> he<00:33:57.080> and<00:33:57.280> his<00:33:57.560> research<00:33:58.080> team<00:33:58.360> wins,<00:33:58.800> we<00:33:58.960> all<00:33:59.160> win.

00:33:59.440 --> 00:34:04.200
And<00:33:59.560> that's<00:33:59.880> definitely<00:34:00.320> an<00:34:00.480> easy<00:34:00.800> for<00:34:01.080> us<00:34:01.400> as<00:34:01.600> a<00:34:01.640> vendor<00:34:02.040> to<00:34:02.200> say,<00:34:02.400> "Yep,<00:34:02.680> I<00:34:02.760> want<00:34:02.920> to<00:34:02.960> get<00:34:03.120> behind<00:34:03.440> that<00:34:03.680> one."

00:34:04.200 --> 00:34:07.560
because<00:34:04.400> it's<00:34:04.600> something<00:34:04.920> that<00:34:05.160> we<00:34:05.280> can<00:34:05.480> see<00:34:05.760> has<00:34:06.160> a<00:34:06.240> globalized<00:34:06.960> benefit.

00:34:07.560 --> 00:34:15.720
So<00:34:08.040> that's<00:34:08.320> the<00:34:08.440> fun<00:34:08.720> I<00:34:08.800> think<00:34:09.040> of<00:34:09.480> aside<00:34:09.800> from<00:34:09.919> getting<00:34:10.159> to<00:34:10.240> go<00:34:10.360> to<00:34:10.480> exotic<00:34:10.919> places<00:34:11.320> like<00:34:11.480> Peru<00:34:12.440> and<00:34:12.600> Minneapolis,<00:34:13.760> you<00:34:13.840> have<00:34:14.040> a<00:34:14.120> chance<00:34:14.760> to<00:34:14.919> really<00:34:15.440> get<00:34:15.639> to

00:34:15.720 --> 00:34:21.399
spend<00:34:16.000> time<00:34:16.240> with<00:34:16.440> each<00:34:16.639> other<00:34:16.879> in<00:34:17.000> person<00:34:17.600> and<00:34:17.800> I<00:34:17.879> think<00:34:18.080> that's<00:34:18.399> the<00:34:18.520> community<00:34:19.000> community<00:34:19.480> building<00:34:19.840> aspect<00:34:20.320> that's<00:34:20.520> very<00:34:20.720> important.

00:34:21.399 --> 00:34:24.080
And<00:34:21.600> it's<00:34:21.760> a<00:34:21.800> research<00:34:22.520> that's<00:34:22.800> the<00:34:22.879> thing<00:34:23.080> with<00:34:23.240> research<00:34:23.600> communities.

00:34:24.080 --> 00:34:29.360
It's<00:34:24.200> already<00:34:24.520> a<00:34:24.600> community.<00:34:25.200> You're<00:34:25.440> in<00:34:25.639> this<00:34:26.120> high-level<00:34:26.679> echelon<00:34:27.159> with<00:34:27.320> the<00:34:27.399> subject<00:34:27.760> matter<00:34:28.000> expertise<00:34:28.520> that<00:34:28.679> you<00:34:28.800> have.

00:34:29.360 --> 00:34:33.200
There's<00:34:29.600> very<00:34:29.840> few<00:34:30.040> people<00:34:30.320> to<00:34:30.440> dinner<00:34:30.720> party<00:34:31.080> that's<00:34:31.320> going<00:34:31.440> to<00:34:31.520> understand<00:34:32.080> what<00:34:32.240> you're<00:34:32.360> talking<00:34:32.720> about.

00:34:33.200 --> 00:34:40.520
So,<00:34:33.320> sometimes<00:34:33.800> it's<00:34:33.919> nice<00:34:34.200> for<00:34:34.320> us<00:34:34.440> to<00:34:34.600> get<00:34:34.879> together<00:34:35.600> and<00:34:35.800> have<00:34:36.000> a<00:34:36.080> beverage<00:34:36.520> with<00:34:36.720> each<00:34:36.919> other<00:34:37.200> because<00:34:37.560> then<00:34:37.720> you're<00:34:37.840> not<00:34:38.080> spending<00:34:38.440> half<00:34:38.679> your<00:34:38.800> conversation<00:34:39.480> explaining

00:34:40.520 --> 00:34:46.560
the<00:34:40.600> vocabulary<00:34:41.280> that<00:34:41.440> you're<00:34:41.600> using.<00:34:41.879> It's<00:34:42.040> really<00:34:42.320> nice<00:34:42.720> to<00:34:42.840> be<00:34:42.960> around<00:34:43.240> people<00:34:43.560> that<00:34:44.080> just<00:34:44.280> get<00:34:44.520> you<00:34:44.720> and<00:34:44.840> they're<00:34:44.960> excited<00:34:45.399> about<00:34:45.600> the<00:34:45.679> same<00:34:45.879> things<00:34:46.080> you're<00:34:46.200> excited

00:34:46.560 --> 00:34:50.840
about.<00:34:47.000> Matt's<00:34:47.280> smiling,<00:34:47.879> Peng<00:34:48.080> Fei's<00:34:48.360> smiling,<00:34:48.800> I<00:34:48.879> think<00:34:49.120> I'm<00:34:49.240> at<00:34:49.360> least<00:34:49.560> hitting<00:34:49.800> the<00:34:49.879> mark<00:34:50.200> somewhat.

00:34:50.840 --> 00:34:56.240
<00:34:51.049> Just<00:34:51.257> waiting<00:34:51.466> for<00:34:51.675> us<00:34:51.883> to<00:34:52.092> tell<00:34:52.301> us<00:34:52.509> whenever<00:34:52.718> you're<00:34:52.927> back<00:34:53.135> in<00:34:53.344> Pittsburgh<00:34:53.552> and<00:34:53.761> then<00:34:53.970> we<00:34:54.178> can<00:34:54.387> go<00:34:54.596> out<00:34:54.804> together<00:34:55.013> and<00:34:55.222> talk,<00:34:55.430> for<00:34:55.639> sure.

00:34:56.240 --> 00:35:01.640
<00:34:56.625> I<00:34:57.009> love<00:34:57.394> how<00:34:57.778> you<00:34:58.163> just<00:34:58.548> put<00:34:58.932> the<00:34:59.317> whole<00:34:59.702> ecosystem<00:35:00.086> together<00:35:00.471> really<00:35:00.855> nicely,<00:35:01.240> Adrienne.

00:35:01.640 --> 00:35:08.560
I<00:35:01.680> thought<00:35:01.840> that<00:35:01.960> was<00:35:02.120> great.<00:35:02.480> It<00:35:02.680> takes<00:35:03.680> a<00:35:03.800> village<00:35:04.480> to<00:35:04.760> really<00:35:05.160> get<00:35:05.440> stuff<00:35:06.160> launched,<00:35:06.800> to<00:35:06.920> actually<00:35:07.400> make<00:35:07.640> things<00:35:07.880> happen.

00:35:08.560 --> 00:35:10.720
We've<00:35:08.760> actually<00:35:09.120> already<00:35:09.360> been<00:35:09.560> on<00:35:09.760> for<00:35:09.880> 90<00:35:10.240> minutes.

00:35:10.720 --> 00:35:13.560
We've<00:35:10.920> talked<00:35:11.160> before<00:35:11.960> and<00:35:12.120> now<00:35:12.360> we've<00:35:12.480> had<00:35:12.600> the<00:35:12.720> podcast.

00:35:13.560 --> 00:35:22.320
But,<00:35:13.680> this<00:35:13.840> is<00:35:13.920> why<00:35:14.080> actually<00:35:14.400> getting<00:35:14.640> together<00:35:15.560> in<00:35:15.760> person<00:35:16.200> is<00:35:16.400> so<00:35:16.600> valuable,<00:35:17.120> too,<00:35:17.360> because<00:35:18.360> y'all<00:35:18.720> three<00:35:19.040> might<00:35:19.280> actually<00:35:19.600> just<00:35:19.840> go<00:35:20.080> to,<00:35:20.840> wait<00:35:21.080> for<00:35:21.360> it,<00:35:22.000> Dave

00:35:22.320 --> 00:35:26.920
and<00:35:22.440> Andy's.<00:35:23.320> I<00:35:23.400> didn't<00:35:23.600> want<00:35:23.720> to<00:35:23.800> get<00:35:23.920> that<00:35:24.080> wrong,<00:35:24.400> so<00:35:24.480> I<00:35:24.520> had<00:35:24.600> to<00:35:24.680> scroll<00:35:24.880> back<00:35:25.120> all<00:35:25.200> the<00:35:25.280> way<00:35:25.360> through<00:35:25.480> my<00:35:25.600> notes<00:35:25.800> to<00:35:25.880> the<00:35:25.960> beginning<00:35:26.280> of<00:35:26.360> this<00:35:26.520> episode.

00:35:26.920 --> 00:35:30.480
But,<00:35:27.153> y'all<00:35:27.387> might<00:35:27.620> go<00:35:27.853> to<00:35:28.087> Dave<00:35:28.320> and<00:35:28.553> Andy's.<00:35:28.787> <00:35:29.020> Who<00:35:29.253> brought<00:35:29.487> up<00:35:29.720> that?

00:35:30.480 --> 00:35:37.160
<00:35:30.751> Yeah,<00:35:31.023> exactly.<00:35:31.294> Build<00:35:31.565> those<00:35:31.837> relationships<00:35:32.108> and<00:35:32.379> I<00:35:32.650> love<00:35:32.922> what<00:35:33.193> you<00:35:33.464> said,<00:35:33.736> Adrienne,<00:35:34.007> you<00:35:34.278> understand<00:35:34.550> the<00:35:34.821> vocabulary<00:35:35.092> a<00:35:35.363> bit<00:35:35.635> better,<00:35:35.906> which<00:35:36.177> is<00:35:36.449> really<00:35:36.720> great.

00:35:37.160 --> 00:35:42.320
Cuz<00:35:37.320> if<00:35:37.480> I<00:35:37.680> I<00:35:37.800> meet<00:35:38.400> Peng<00:35:38.600> Fei<00:35:38.760> for<00:35:38.880> the<00:35:38.960> first<00:35:39.240> time,<00:35:39.520> he's<00:35:39.680> like,<00:35:39.920> "This<00:35:40.120> guy<00:35:40.320> is<00:35:40.520> really<00:35:41.320> high-energy.

00:35:42.320 --> 00:35:44.440
We're<00:35:42.480> trying<00:35:42.720> to<00:35:42.800> figure<00:35:43.000> out<00:35:43.120> what<00:35:43.280> words<00:35:43.680> mean,<00:35:44.200> right?

00:35:44.440 --> 00:35:49.480
We're<00:35:44.600> connecting."<00:35:45.280> Same<00:35:45.560> thing<00:35:45.720> with<00:35:45.880> Matt.<00:35:46.600> Adrienne's<00:35:47.000> still<00:35:47.160> trying<00:35:47.360> to<00:35:47.400> connect<00:35:47.680> with<00:35:47.800> me<00:35:47.960> after<00:35:48.240> Educause<00:35:48.720> last<00:35:49.080> year.

00:35:49.480 --> 00:35:57.960
And<00:35:49.680> so,<00:35:49.920> no,<00:35:50.080> I<00:35:50.160> think<00:35:50.360> it's<00:35:50.480> a<00:35:50.600> really<00:35:50.920> great<00:35:51.600> bow<00:35:52.280> on<00:35:53.240> it<00:35:53.400> just<00:35:53.720> really<00:35:54.040> takes<00:35:54.360> a<00:35:54.400> village<00:35:55.200> to<00:35:55.720> really<00:35:56.000> drive<00:35:56.400> innovation<00:35:57.120> and<00:35:57.440> not<00:35:57.720> just

00:35:57.960 --> 00:36:00.360
one<00:35:58.240> silo<00:35:58.720> department<00:35:59.320> that's<00:35:59.480> going<00:35:59.600> to<00:35:59.680> make<00:35:59.880> it<00:36:00.000> happen.

00:36:00.360 --> 00:36:07.680
So,<00:36:01.000> I<00:36:01.040> know<00:36:01.200> we<00:36:01.280> could<00:36:01.400> keep<00:36:01.600> going.<00:36:02.160> Maybe<00:36:02.440> you<00:36:02.520> come<00:36:02.680> back<00:36:02.880> on<00:36:02.960> the<00:36:03.080> podcast<00:36:03.720> for<00:36:03.880> a<00:36:03.920> different<00:36:04.240> session,<00:36:04.640> but<00:36:05.040> I<00:36:05.080> really<00:36:05.360> appreciate<00:36:06.120> everyone<00:36:06.480> coming<00:36:06.720> on<00:36:06.840> the<00:36:06.920> show

00:36:07.680 --> 00:36:09.440
and<00:36:07.940> thank<00:36:08.200> you<00:36:08.460> all.<00:36:08.720> <00:36:08.980> Thank<00:36:09.240> you.

00:36:09.440 --> 00:36:13.240
<00:36:09.640> Thank<00:36:09.840> you,<00:36:10.040> Joe,<00:36:10.240> and<00:36:10.440> thanks,<00:36:10.640> Matt.<00:36:10.840> Thanks,<00:36:11.040> Peng<00:36:11.240> Fei,<00:36:11.440> for<00:36:11.640> sharing<00:36:11.840> the<00:36:12.040> work<00:36:12.240> that<00:36:12.440> you're<00:36:12.640> doing<00:36:12.840> with<00:36:13.040> us.

00:36:13.240 --> 00:36:16.120
I<00:36:13.320> really<00:36:13.600> appreciate<00:36:14.120> it.

Up next

All episodes

Video Stop Testing Your Recovery for Success — University of Wyoming, Grand Valley State & Commvault

Amy McLaughlin, Miloš Topić, and Jared Whitehurst on telling campus AI was coming before picking a tool, earning trust before asking for it, and proving your backups are clean before you need them.

Joe Toste

Video #244: Orange County, NC — The AI Idea That Built a Tax Calculator in 1 Day

Discover how Orange County, NC, built a 100% accurate tax calculator in just one day by empowering staff with a secure AI sandbox, and learn how they are bridging the digital divide with a $10M broadband initiative.

Joe Toste

Video #243: CalSTRS & California DMV — Your Risk Is My Risk

Discover how the California DMV and CalSTRS are redefining IT modernization. Learn how deep trust, customer-centric processes, and cutting-edge AI labs are transforming public sector services.

Joe Toste