►
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
So
this
slide
summarizes
the
current
status
with
the
different
color
codings.
So
red
means
that
those
items
we
have
not
started
working
on
yet
and
the
orange
ones
are
some
items
that
you're
making
progress
and
the
green
ones
are
either
done
or
we're
getting
close
to
done.
Since
we're
now
working
on
the
onyx
1.9
release
that
that
will
include
some
of
these
features.
A
A
The
sig
has
taken
a
look
at
this
and
the
recommendation,
as
the
next
step
is
to
decide
on
the
specific
list
of
operators
that
stick
would
like
to
replace
with
functions
and
once
those
are
identified,
we'll
like
to
get
more
contributions
from
the
community
to
drive
making
more
progress
on
this
area
on
the
unified
operator
interface
style,
the
goal
was
to
prepare
a
style
guide
which
describes
expected
behavior
of
typical
properties
of
operators
such
as
data
layout
exit
specifications
attribute
namings
things
like
that.
A
We
want
to
enforce
this
style,
then
all
new
operators,
as
well
as
the
existing
ops,
so
one
example,
may
be
the
negative
values
for
x's.
So
the
sig
is
working
on
this
goal.
They
are
reviewing,
is
existing
office
and
comparing
against
numpy
convention
and
they'll,
be
working
on
outlining
the
needed
changes
to
prepare
and
also
prepare
pr
with
the
non-prior
updates.
A
This
will
help
with
the
simplifying
function
definition
as
well
as
adding
test
cases
on
the
zoo
side,
we're
making
progress
here
as
well.
So
there
are
prs
that
is
covering
this
expand
model
test
to
all
models
on
model
zoo,
as
well
as
improving
tutorials
on
model
zoo.
So
there's
ongoing
pr
with
the
review
on
the
quantized
models.
A
There's
some
suggestions
from
the
community
that
where
we
are
expecting
some
contributions
into
the
model
zoo
and
the
siege
is
happy
to
work
with
the
the
contributors
to
unload
more
models
that
includes
the
quantized
models
on
the
architecture
and
infrastructure
side
we're
working
on
the
improving
support
for
the
large
models.
A
We
fixed
some
of
the
external
data
handling
issues
in
1.8.1
about
fixed
release,
as
well
as
there's
some
improvements
in
the
apis
for
converting
models
with
external
data.
That's
coming
in
the
1.9
release
on
the
ship
inference
side.
The
the
one
of
the
thing
that
was
crossed
out
here
is
detecting
error
via
model
checker.
A
A
We
didn't
work
on
this
real
for
easier,
debugging
and
testing
there,
but
there
are
some
improvements
on
the
shape
inference,
such
as
a
symbolic
shape,
inference
that's
coming
in
the
onyx
1.9.
A
On
the
improving
error,
handling
and
exception
free,
we
are
also
making
some
card
that
was
updated
with
regards
to
error
handling
in
1.8.1
and
then
there's
a
pr
in
progress
for
no
exception.
Build
for
onyx.
A
So
with
that,
our
next
upcoming
release
of
onyx
is
version
1.9,
this
time,
mikhail
from
intel
volunteered
to
be
a
release
manager.
So
thanks
thanks
a
lot
for
michael
for
driving
this
and
there's
a
lot
of
new,
exciting
features
in
this
upcoming
release.
So
I
mentioned
some
improvements
in
the
symbolic
shape.
In
first,
we
also
are
removing
some
of
the
still
codebase,
so
we're
removing
optimizers
from
the
rx
packages
and
updates
to
the
external
data
helpers.
A
That's
related
to
the
large
model
inference,
and
we
are
also
enabling
selected
loading
of
alex
schema
by
a
specific
offset
version,
and
we
also
are
introducing
a
text-based
onyx
parser,
which
will
simplify
function,
definitions
and
test
cases,
and
there
is
a
new
offset
version
14..
Some
of
these
includes
the
updated
ops
as
well
as
two
new
ops.
One
is
the
trial
new
and
then
hard
switch
function.