►
From YouTube: ONNX Edge WG meeting 20190724
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Basically,
I'm
gonna,
officially
close
this
issue
after
this
meeting
and
based
on
this
discussion.
Here,
everybody
replied:
yes,
yes,
yes,
so
officially
I
think
we
accepted
this
document
to
be
published.
So
what
I'm
gonna
do
I'm
gonna
move
this
document
and
associated
pictures
or
drawings
into
the
artifact
folder?
Alright,
so
that
the
I
think
we
agreed
that
that
is
the
folder
where
we
gonna
be
published
whatever
we
we
decide
to
publish
so
copy
them
from
the
discussion
material
into
the
into
the
artifacts
folder
and
make
it
that
way.
A
Yeah
we
have
this,
we
know
we
are
gonna,
go
through
the
prototype
profile
or
in
the
proposal
on
for
profile.
Definitions
should
look
like,
and
you
know
what
the
information
should
it
contain,
and
you
know
in
potentially
have
that
as
a
template
that
we
can
use
for
other
profiles
right
so
in
general
today
that
is
gonna
be
dominant
or
main
discussion
overall
drive
with
some
prototype
profile
definition.
He
has
and
then
we'll
talk
about
it
and
see
why
you
know
where
we
end
up
and
in
about
next
steps.
After
we
finish,
today's
meeting
sounds
good.
A
A
A
B
B
A
B
So
as
I'm
going
so
describing
the
PO
fun,
I
think
one
of
the
things
that
we
should
kind
of
think
awful
comment
on
is
as
a
template
does
this
thing
looks
good.
We
missing
additional
chapters
if
the
existing
chapter
looks
okay,
so
what
I
try
to
do
I
try
to
describe
there
is
an
IOT
device
that
is
stationary,
meaning
it's
not
moving
and
it
has
input
and
output
of
audio
and
video.
B
A
B
B
A
A
B
B
So
I
thought
that
it
should
start
with
a
short
description,
a
high
heaven
description
of
what
this
profile
is
trying
to
describe
in
very
general
terms.
What's
the
family
of
devices
that
this
profile
is
trying
to
cover,
you
know
more
than
they
four
or
five
lines
that
describe
the
profile.
This
is
the
description
of
the
profile
in
a
few
sentences,
so.
B
B
B
B
So
this
next
section
is
giving
a
few
examples
and
I
think
based
on
the
examples
you
can
get
a
better
understanding
of
what
stay
Assaf
occation
of
devices
that
I
try
to
capture,
so
the
first
device
is
an
IP
security
camera.
This
is,
of
course,
usually
a
stationary
stationary
device
fixed
to
a
wall
or
placed
on
some
furniture
or
whatever
it
has
a
video
input.
Web
connectivity
concern
about
it
connected
to
a
power
source.
B
When
we
talk
about
a
low
quality
of
data,
so
IP
security
camera
is
broadcasting
back
as
far
as
I
know,
pictures
short
video
sequences,
but
it
doesn't
podcast
continuously
the
video
Steinbach.
This
is
I
think
the
there
used
to
be
a
period
of
time
in
the
history.
The
type
Econoline
was
just
taking
the
video
compressing
it
to
digital
format
and
sending
it
over
IP.
What
are
they
doing
today?
B
B
Another
example
to
this
family
is
a
small
speaker,
think
of
an
X
cycle
or
Google
home,
and
the
failed
example
is
a
small
display
which
is
the
same
family
of
devices,
but
has
a
video
input
and
output,
both
small
speaker
and
small
display
I'll
construct.
We
connected
to
the
web
and
they're
different
from
IP
security
camera,
as
they
have
usually
have
a
highboy
processing
model.
B
B
So
these
are
examples
to
this
profile
things
that
I
don't
wanted
to
cover
our
devices,
which
are
ok,
so
another
aspect
of
this
profile.
These
devices
are
usually
small
and
low
in
energy,
so
this
profile
is
not
trying
to
cover
some
kind
of
an
infrastructure,
edge,
silver
or
not,
trying
to
cover
mobile
for
both
of
the
power
requirements,
memory
requirements
and
then
I
stopped
eating.
Oh,
but
the
mobile
phone
is.
These
are
more
simplified
devices.
B
A
Okay,
I
am
you
know
in
general,
I
guess
in
agreement.
This
is
something
that
we
need
to
decide
exactly:
what
kind
of
families
or
what
kind
of
composite,
because
this
is
also
a
composite
device
and
it
has
multiple
capabilities
and
we
need
to
dial
in
I
think
on
to
the
granularity
of
these
profiles
right,
how
we're
going
to
group
them
right.
So
for
one
for
now
it
seems
okay,
I
mean
the
only
thing
is
that
should
be.
Maybe
that's
like
no
to
ourselves.
B
I'm,
just
if
you
look
at
the
list
of
modems,
for
example,
then
yeah
it
security
camera
is
definitely
not
going
to
pass
a
the
nnp
modems
and
that
you're
going
to
give
it
so
and
small
speaker
cannot
do
classification
of
video.
So
if
you
think
of
it
in
terms
of
profile,
is
mapped
to
a
list
of
networks
that
it
has
to
pass,
then
I
agree.
B
B
So
QC,
is
it
challenging
a
challenging
section?
Cuz
I
wanted
maybe
to
open
it
up
for
a
short
discussion.
Accuracy
is
going
to
talk
about.
First
of
all,
it's
going
to
talk
about
the
models
that
we
want
this
device
to
answer
so
I
was
asking
myself:
should
the
accuracy
section
contain
a
table
that
kind
of
goes
or
the
moderns
a
list
of
models
and
for
each
modern
gives
accuracy
looks
to
me
that
that
should
be
the
approach.
B
A
A
B
A
A
B
Have
a
general
sentence
that
says
something
like
for
80%
of
the
tested
models
to
allow
some
deviation
accuracy.
So
we
said
that
the
measure
the
metrics
are
top
1
to
5
in
map.
This
is
good
for
video
I.
Don't
know
we
need
to
think
of
I,
don't
know.
What's
the
metric
for
audio
right
now,
top
of
my
head
I
recall
there
is
a
metric
for
hold.
You
separated
metric
for
MP.
A
A
B
A
I
was
that's
why
we
started
saying
that
we
did
discuss
having
a
document
about
compliance,
but
then
again,
if
he
define
these
profiles-
and
we
can
mean
technically,
you
know
you
could
define
parameters
of
compliance
right
here.
You
know
if
we
are
already
spelling
out
models
that
we
want
to
kind
of
require
as
supported
models
right
so
I
mean
he
came
from
one
language
to
actually
I
was
I.
Was
thinking
option
one,
maybe
whether
we
have
a
table
just
say
min
Max
right
and
which
type
of
accuracy-
and
you
know
maybe
just
simpler.
A
Well,
no,
in
that
case,
yeah
I
was
thinking
we
will
have.
We
would
you
the
define
specific
models
here
you
know
in.
If
we
go
with
the
option
one
table
and
specify,
then
it
has
to
be
like
specific
right
for
which
model.
In
that
case,
we
combine
the
profile
definition
where
they
also
compliance
met.
You
know
compliance
parameters,
I
mean
not
fully,
because
we
are
defining
just
the
models
and
expected
metrics.
You
need
to
define
sort
of
the
you
know,
compliance
framework,
maybe
that's
a
separate
document
that
needs
to
be
happen.
A
A
B
A
A
A
B
B
Okay,
okay,
so
this
is
accuracy,
so
example
full-size,
so
the
minimum
this
is
kind
of
laying
out
the
minimum
requirements
of
size
is
to
have
2
gigawatts
of
DRAM
and
8
gigabytes
of
storage
home
surprising.
To
me,
by
the
way
this
is
the
spec
of
Fae
I,
think
quanity,
either
Amazon
echo
or
Google
home
speaker.
This
is
what
they
have
so
it's
kind
of
a
realistic,
ok,
the
size.
B
B
A
You're
saying
latency
of
the
network
inference
oh
well,
there
is
a
you
know:
I
guess
there
is
a
surrounding
around
the
inference
like
USB,
no
pre-processing,
post-processing
and
all
that
stuff.
So
we
are
not
gonna.
We
should
not
try
to
accommodate.
For
that.
I
mean
you
know.
You're
saying
here
is
less
than
33
15
30
frames
to
strike
on,
but
then
end
to
end.
If
you
wish
frames
per
second,
maybe
less
than
that
because
of
the
flip
processing
and
post
processing
aspects
right,
but
so.
B
We
can
reduce
the
number
to
25
and
say
that
it
fits
30
FPS
pass
over
it,
yeah
I'm
just
trying
to
explain
it.
The
the
latency
number,
in
my
view,
should
come
form
like
when
we
described
the
latency.
We
should
kind
of
say:
why
do
we
do?
We
chose
a
say
that,
given
a
specific
number
now
just
say:
oh,
it's
15
milliseconds,
just
because.
B
And
you
know
this
is
the
case
that
you
can
actually
see
that
there
is
different
requirement
for
input
in
video
versus
input
of
audio
and
I
guess
accuracy
will
have
the
same,
which
is
more
driving
to
what
you
mentioned
earlier,
that
maybe
we
should
separate
it
to
separate
it
or
fangs.
It's
possible
yeah
power
consumption.
So.
B
B
B
The
idea
is
to
say
Therese:
we
expect
a
certain
amount
of
the
models
to
be
within
some
envelope
and
we're
now
a
maximum,
so
there
might
be
some
modern
that
causes
that
device
to
go
above
this
typical
power
consumption,
but
it
shouldn't
go
above
the
maximum
and
the
motivation
here
is
to
you
know:
we
talked
about
it
that
if
we
require
some
accuracy,
sighs
Nathan
say
all
of
these
also
comes
into
power
consumption.
Of
course,
I
can
meet
a
very
low
latency
with
the
device
that
consumes
10,
but
Oh
25
or
100.
B
B
A
B
B
B
A
A
A
A
A
A
So
we
were
talking
about
some,
what
about
how
to
structure
these
profile
definitions,
and
should
we
go
by
hierarchy
hierarchical
so
that
you
have
the
top-level
profile
family?
And
then
you
have
sub
profiles
or
levels
underneath
or
should
be
our
key
of
what
of
edge
device
profiles,
for
example,
for
example,
you
have
even
in
this
example,
you
have
the
profile
that
describes
the
family
of
product
family
of
devices.
Technically
speaking,
I
mean
it
can.
A
You
know
it
combines
a
variety
of
use,
cases
and
models
and
audio
and
video
together,
and
you
know,
data
locality
in
terms
of
processing
locally
versus
locally
and
on
the
weak
in
the
cloud.
So
this
is
all
currently
kind
of
described
in
this
one
on
profile,
so
we
were
talking
about.
Maybe
this
profile
definition,
it's
really
top
level
family
edge
device,
and
then
you
have
a
sub
profiles
that
fit
or
break
it
down
into
more
kind
of
specialized
use
cases
of
that
family.
Oh
yeah,
yeah,
I,
agree.
B
A
B
Just
have
never
won
that,
for
example,
never
one
has
just
motion
the
basic
motion,
detection
kind
of
thing,
and
he
sends
most
of
the
processing
back
and
nothing
as
a
segmentation
and
object
some
some
level
of
classification.
You
main
call
something
and
Neven
three
is
doing
something
more
complex,
combines
audio.
B
Okay,
good,
so
just
to
finish
that
document,
so
the
previous
section
was
about
four
or
five
attributes
and
now
there's
addition
on
two
sections:
one
of
them
is
a
list
of
require
networks.
This
is
kind
of
I,
just
put
a
placeholder
there,
and
now
that
we
talked
about
Nevins,
then
of
course
that
would
be
broken
down
to
mavens,
but
the
idea
is
to
provide
a
list
of
which
networks
and
this
network
has
to
come
from
onyx
or
than
zoom
I.
B
B
Cool
things
that
we
should
probably
talk
about
is
that
we
try
to
as
much
as
possible
provide
fingers
out
part
of
the
modern
so
that
I'll
suitable
to
the
devices.
If
we
find
that
we
need
another
model,
that
means
it
need
to
be
added
to
the
zoo,
I
think.
As
a
guideline,
we
shouldn't.
B
B
B
Okay,
so
the
neonics
operations
will
be
the
operation.
Not
operations
is
kind
of
derivative
from
the
previous
section,
sir.
Oh,
it's
more
of
a
summary
list
for
convenience,
so
that
if
someone
reads
the
profile,
he
would
understand
which
operations
need
to
be
supported,
operations
and
attributes
of
the
operations
covered
by
the
networks
that
needs
to
be
passed.
So
this
is,
you
can
think
of
it.
B
B
A
A
A
A
So
maybe
you
have
a
few
more
minutes
and
I
have
to
kind
of
finish
five
minutes
before,
because
I
have
to
free.
I
should
have
said
that
before
I
need
to
get
into
the
other
meeting,
but
the
thing
is
so
action
items
right
and
the
next
step,
so
I
guess
we
want
to
put
this
into
the
discussion
material
right
mm-hmm
as
a
document
we
discussed,
and
we
can
also
further
comment
on.
A
So
that's,
let's
that
will
be
action
item.
One
action
item
two
started
thinking
about
when
we
start
talking
about
this
levels
and
how
do
we
fire
our
key
and
all
that
stuff
and
so
I
was
wondering?
Would
it
be
beneficial
that
we
start
try
to
define
this?
So
this
is
a
template,
for
individual
profile
could
be
should
least
try
to
define
top
level
map
of
sort
of
okay.
A
Here's
the
family
we
want
to
have-
and
here
are
the
levels
of
that
family
and
have
this
kind
of
top
level
view
of
the
type
of
devices
and
use
case
she's
been
caught
to
cover
in
general.
So
this
discussion
today
is
about
the
template,
which
is
very
valuable,
but
then
also
we
need
to
decide
what
other
what
other
profiles
we
want
to
do
right
and-
and
so
that's
why
I
was
thinking,
maybe
that
that
kind
of
top-level
map
might
be
useful
for
us
mm-hmm.
B
And
so
maybe
when
you
want
to
create
this
kind
of
top-level
map,
you
have
a
sewing.
You
have
an
another
document
that
just
takes
these
first
two
chapters,
the
introduction
and
of
an
example,
and
just
put
one
of
these
for
each
poor.
Fine,
so
I
have
a
profile
and
I'm
giving
the
examples
under
this
offer.
Not
the
funda
now
yeah
that.
A
A
A
A
Here,
I
guess,
but
then
you
know
audio/video
capabilities
and
all
that
stuff
right
I
mean
you
could
have
that
in
a
car.
You
could
have
that
in
a
laptop.
You
could
have
that
actually
in
a
smart
phone.
So
all
this
really
I
mean
if
you
think
about
the
use
case.
What
are
the
differences?
You
have
stationary
versus
non
stationary
right.
The
offenses.
B
A
B
Not
asking
an
IP
camera
to
do
something
that
this
smartphone
can
do,
because
when
I
become
allies,
cost
$50
and
the
smartphone
costs
more
and
I
become
her,
has
fixed
power,
supply
and
fixed
a
network
connection
and
a
mobile
device.
Dozens
mobile
is
a
problem.
Mobile
can
do
anything,
yeah
difference
between
it
alone
and
then
I
become
a
innocence.
A
There
is
there
is,
but
each
of
them
have
technically
because
they
have
video
capabilities
or-
and
you
know
they
have
classification
use
cases,
object.
Detection
use
cases
that
apply
to
all
them
right.
Car
has
logic,
affection,
drone
has
a
detection,
you
know
whatever
IP
camera
has
okay
effects.
So
all
these
have
objects
that
actually
use.
A
A
Note
I
would
say,
tried
and
they
have
a
document
proposing
this
high-level
top
level
map
of
the
profiles
in
how,
in
some
levels
and
and
all
that
so
I
will
I
will
I
will
take
that
action
item
on
myself
to
to
have
something
for
next
time
to
discuss,
and
hopefully
with
that
and
maybe
with
further
discussion
on
a
template
and
a
profile
definition.
We
could
start
having
people
filling
the
blanks
so
to
speak.
Okay,.