►
From YouTube: NUG monthly meeting June 2021
Description
Our topic of the day was GPU Programming Models and Interoperability - GPU experts from NERSC's Advanced Technologies and Application Performance groups joined for a discussion about GPU programming models and interoperability, also our regular sections includng soem handy tips about how to find your screen session on Cori
A
A
A
A
Component
of
the
meeting
is
to
show
off
an
achievement
or
shout
out
somebody
else's
achievement,
and
so
it
can
be.
It
can
be
something
small.
It
can
be
something
big
you
may
have
had
a
paper
accepted.
You
might
have
solved
the
bugs
that
have
been
giving
you
grief
for
a
little
while
or
that
had
something
particularly
interesting
or
challenging
about
it.
You
know,
especially
if
it's
something
that
can
be
a
good
tip
for
for
other
nurse
users.
A
C
C
C
A
So
I
guess
on
outside,
in
the
in
the
last
month,
next
exciting
news,
which
will
be
the
promoter
dedication,
which
is
sort
of
a
important
step
towards
promoting
becoming
available
for
users,
we're
still
in
the
process
of
the
getting
it
getting
the
environment
ready
for
early
access
users
to
come
on.
But
that
should
happen.
A
A
That
you
know
might
might
be
beneficial
also
for
other
users
to
hear
about,
and
this
can
be
something
that
didn't
work.
You
know
we
we
do
research,
often
cutting
edge
stuff,
and
that
does
always
carry
a
risk
that
you
know
we
try
something
and
it
turns
out
that
it
doesn't
work
and
it's
sort
of
an
important
element
of
the
science
discovering
what
doesn't
work
as
well
as
what
does
and
learning
from
that
as
well
as
that,
it
can
be
just
something
interesting
that
you
came
across.
A
Yes,
there
is
a
what
you
call
a
less
public
address
for
each
login
node,
although
in
most
cases,
if
you
need
to
get
to
a
specific
login
node,
probably
the
easiest
way
to
do
it
is
to
you
know,
to
log
in
as
normal
and
then
from
the
login
node.
You
can
also
just
ssh
choreo
4,
for
instance,
that
can
be
useful
if
you're,
for
instance,
running
screen
in
the
background
was
a
william.
Was
there
a
particular
use
case
that
you
had
where
the
the
224
address.
A
A
So
something
that
I
discovered
in
the
last
month
was
somewhere
between
a
today
I
learned
and
oh,
that
was
a
riverwind,
was
using
shifter
to
do
things
that
are
easy
in
ubuntu,
but
not
necessarily
easy
on
a
system
like
corey
this
particular
example.
Whereas
there
was
a
question
about
running
later-
and
you
know
typically
that's
something
that
you
would
do
on
on
a
home
system,
but
yeah,
there
are
certain
use
cases,
whereas
it's
handy
to
be
able
to
run
it
on
cory.
A
A
A
A
All
right
announcements
and
calls
for
participation,
so
we
have
a
a
few
and
the
details
of
these
can
be
found
in
the
weekly
email
from
this
week.
Some
of
them,
I
think,
may
also
have
individual
emails
send
around
one
kind
of
important
one
coming
up,
but
still
it's
still
a
few
weeks
away,
but
there
will
be
a
power
outage
at
nurse
on
the
weekend
of
july
9
through
12,
and
it's
essentially
it's
a
tri-annual
every
every
few
years.
We
need
to
do
some
maintenance
on
the
on
the
power
system.
A
Server
at
lbl,
and
this
particular
maintenance
this
year
or
in
july,
will
impact
the
building
that
that
hosts
nurse
and
holds
things
like
cory
and
a
lot
of
nurse
systems,
so
we're
anticipating
that
our
backup,
power
and
cooling
should
be
able
to
keep
most
of
the
auxiliary
systems
running,
but
corey
will
be
down
during
that
weekend
and
we'll
piggyback
cory's
regular
maintenance.
On
top
of
that,
so
that
the
maintenance
for
july
will
be
shifted
to
kind
of
happen
in
tandem
with
that
power
outage.
So
you
can
check
the
weekly
email
for
details.
A
A
So
just
a
heads
up
that
to
be
aware
of
that.
Another
important
heads
up
is
that
we
will
in
the
next
few
months-
and
I
think
that
august
is
the
target
need
to
update
corey's
operating
system,
and
it's
a
it's
a
it's
a
medium
scale
update.
We
anticipate
that
executables
that
are
statically
linked
will
need
to
be
re-linked,
for
you
know:
newer,
correct
versions
of
static
libraries,
stuff
that's
dynamically
linked,
should
just
work
so
yeah,
that's
preparing
for
that
as
well.
A
B
A
So-
and
I
think
in
that
email
that
mentioned
that,
so
if
you're
already
part
of
a
new
set
project,
that's
that's
kind
of
already
worked
out.
There's
a
email-
maybe
maybe
you
can
correct
me
from
wrong
kevin-
is
requesting
applications
for
early
access
to
call
matter
outside
of
you
know,
lisa
and
I
think
maybe
ucp
so
yeah.
B
A
C
Was
there
any
other
announcements
that
somebody
wanted
to
make?
I
think
I
saw
somebody
hi
steve.
It's
rob
ryan.
I
just
wanted
to
ask
you
how,
regarding
the
parallel
applications
workshop
alternatives
to
mpi
plus
x,
do
you
know?
Do
people
ever
discuss
coral
reef
iv
at
these
workshops?
It's
it's
an
alternative
to
mpi
plus
six.
I'm
just
curious
because
I
tried
it
for
the
first
time
and
it
found
it
kind
of
quite
useful.
C
A
I
don't
think
I've
actually
been
to
the
poor
etm
workshop
in
the
past,
so
I
haven't
scanned
through
the
list,
but
that
does
sound
like
within
within
scope,
because
it's
yeah,
it's
it's
parallel.
It's
corey
fortran,
I
think,
is
part
of
the
fortran
standard.
Now
it's
reasonably
well
supported
or
somewhat
somewhat
supported,
at
least
so
yeah.
I
I
would
anticipate
that.
The
answer
is
yes.
B
It's
it's
definitely
possible.
It
really
depends
on
what
the
topics
are
that
year.
So
if
there's
a
heavy
thing
say
on
you
know
gpus,
then
they
might
not
talk
much
about
fortran,
so
you
might
want
to
look
at
the
a
little
bit
more
detail
on
what
that
workshop
is
doing
this
year
and
what
their
plan
is.
It's
definitely
in
the
purview,
but
it's
hit
or
miss
as
to
whether
cora
ray's
come
up.
Okay,
all
right
thanks.
E
So
this
is
cheyenne
from
pn
annual,
so
I
have,
I
usually
attend
this
workshop
and
there
is
always
discussion
on
corey
fortran,
because
damien
rousen
usually
attends
it
and-
and
I
remember
a
couple
of
years
back-
there
was
a
very
lively
discussion
on
coding,
fortran
saying
that
you
know
so
yeah
I
mean
there
is
always
some
discussion
on
cafe
and
there
are
caf
people
who
usually
attend.
I
think
and
as
you
know,
damien
drousson
is,
I
guess
he
has
recently
joined
lvl.
I
guess
so.
I
think
there
would
be
participation.
B
A
Interesting
things
on
it:
it's
quite
the
competition
for
attention
there,
so
we
have
a
few
training
events
coming
up
as
well.
Next
week
on
on
june,
22
we'll
have
a
session
on
elmob
for
perlmutter,
so
you
may
have
used
elmwood
before
on
a
different
system.
It's
kind
of
the
follow
on
from
the
environment
modules,
which
is
tcl
based
that
we
use
on
quarry
and
so
on,
perlmutter
we're
going
to
shift
to
using
elmore,
but
for
the
most
part
it's
it's
the
same.
A
It's
the
same
user
experience,
you
type
module
load,
you
get
a
module
modular
veil,
module
unload,
but
there's
a
few
little
differences
in
how
it
works
to
be
useful,
to
know
about,
and
also
a
few
extra
capabilities
that
are,
that
are
quite
helpful.
So
we'll
have
a
training
session
on
that
next
week.
Also,
in
a
couple
of
weeks
time,
we
have
a
training
session
scheduled
for
ci
at
nurse.
B
A
Have
some
tips
about
that
coming
up,
there's
a
ecp
ideas,
webinar
also
coming
up
in
a
couple
of
weeks
time
this.
This
can
be
really
interesting,
for
you
know,
picking
up
tips
and
tricks
about
kind
of
achieving
things
in
software
and
scientific
software
development
there's
also
a
cuda
multi-threading,
with
streams
workshop
hosted
by
or
presented
by
nvidia
coming
up
really
soon.
A
E
A
A
A
Let's
see
we
should
have,
I
think,
ronnie
who's
part
of
our
application
performance
group,
and
I
think
chris
is
also
on
who's
part
of
our
advanced
technologies
group
and
they
have
a
good
bit
of
experience
with
with
some
of
the
different
gpu
models.
I
think
there's
a
couple
of
other
nurse
people
as
well
and
we're
very
interested
in
the
input
and
experiences
from
the.
B
A
Other
nurse
users
in
the
in
the
room
here
so
we'll
go
through
a
quick
overview
here
and
then
we'll
go
into
a
discussion
section
so
right
up
front
between
different
programs.
Improv
interoperability
tends
to
be
sort
of
limited
and
difficult,
and-
and
this
is
not
just
for
gpus-
this
is
for
everything.
So
if
you're,
using
a
c
library,
you're
calling
a
c
library
or
working
in
c,
things
are
kind
of
relatively
easy
c
has
a
pretty
universal
api,
and
so
your
c
libraries
tend
to
be
able
to
be
used.
A
You
know
from
from
any
compiler,
you
know
in
any
programming.
Environment,
yeah
fortran,
for
instance,
uses
special
name
mangling
rules,
and-
and
there
are
there's
a
standard,
bind
c
to
map
for
you
for
a
given
fortran
implementation,
the
correct
binding
to
to
get
between
c
routines
quantum
routines-
and
you
know
c,
plus
plus,
strokes
to
see
fairly
negatively
so
calling
stuff.
That's
in
c
is
reasonably
easy
beyond
that,
though,
going
across
programs
tends
not
to
be
straightforward.
A
Both
c
plus,
plus
and
fortran
use
the
particular
apis
and
name
mangling
rules
that
are
implementation,
specific,
so
code,
c,
plus
plus
code
compiled
with
one
compiler
or
programming
environment,
probably
can't
talk
to
c
plus
plus
code
compiled
with
a
different
one.
So
just
as
a
as
a
general
rule
for
the
you
know,
these
higher
level
languages
sticking
to
one
programming
environment
is
generally
the
best.
A
A
A
So
your
code
will
need
for
the
cpu
code
as
well,
will
also
need
to
be
able
to
be
built
with
the
nvidia
stack,
and
you
know
it
is
possible
that
other
compiler
suites
that
might
give
better
performance
for
the
cpu
code.
We
sort
of
anticipate.
You
know,
particularly
in
phase
one,
the
fellmatter,
which
is
very,
very
gpu,
oriented
that
the
gpu
code
will
be
doing
the
other
block
of
the
heavier
lifting
in
terms
of
the
computational
work.
So
so
for
most
cases
we
expect
that
programming
video
will
be
the
one
to
use.
A
A
So
when
you,
when
you
module,
load
the
program,
you
kind
of
get
everything
built
in
so
you
you've
got
cuda
support.
You've
got
standard
fortran,
which
has
got
things
like
you
know,
duke
and
and
coerry
for
tran
you've
also
got
open,
acc
and
openmp
support
yeah
that
extends
to
gp
gpu
offload,
as
well
as
the
more
traditional
openmp
for
multi-threading.
A
A
A
A
A
That's
not
nvidia
cuda's
not
built
into
the
environment,
so
there'll
be
a
separate
module
load,
good
toolkit
that
you'll
need
to
do
to
get
access
to
the
girder
libraries,
and
so
you
know
the
image
looks
a
little
bit
similar,
but
a
little
bit
different,
so
you've
got
you
know
an
extra
step
here
for
gnu
to
get
cuda
and
you've
still
got
access
to
kind
of
the
same
things
and
again,
you've
still
got
your
higher
level.
Libraries
like
cocos
and
raja,
which
can
compile
down
to
these
things.
A
A
All
right
so
as
a
summary
interoperability
is
possible,
but
we
don't
recommend
relying
on
it
as
as
much
as
you
can.
Keeping
within
one
programming
model
is
is
generally
a
good
tip
and
the
the
higher
level
frameworks
are
worth
looking
into
yeah,
particularly
if
you
know
if
your
code
is
c
plus
plus
so
you're
doing.
You
know
new
development
take
a
look
at
things
like
cocos
and
raja.
A
A
H
H
So
I
mean
here
at
nurse
we're
we're
big
advocates
for
things
like
openmp
target
offload,
which
will
be
portable
across
all
doe
machines,
yeah
and
if
you
have
particular
use
interoperability,
use
cases
that
are
important
to
you.
I
mean
please
let
us
know,
and
then
we
can
actually
speak
with
the
vendors
directly
to
ensure
that
they
are
supported
and
because
yeah
there's
in
a
way
there's
like
a
million
different
interoperability
use
cases.
You
could
imagine
so
it's
very
helpful
for
us
to
prioritize
things.
I
Yeah,
I
think
just
one
other
thing-
I
guess
yeah,
so
the
optimal
use
cases
well,
the
most
performant
use
case.
You
would
see
it
if
you're
sticking
to
one
program
model
by
one
programming
environment,
which
is,
I
think,
what
chris
was
leading
to
as
well.
So
unless
you
need
to
do
not
like
mix
things,
we
will
have,
we
might
end
up
having
different
cuda
versions
that
are
more
latest
than
what's
in,
let's
say
the
programming
environment
nvidia
that
what
steve
showed
before.
I
So,
if
you
want
to
do
that,
yeah
sure
go
ahead
and
it
would
still
work.
There
won't
be
any
problems
there,
but
there
can
be
some
performance
hits.
But
if
you
feel
like
there
is
a
use
case,
please
let
us
know
and
that's
how
we'll
be
able
to
alleviate
some
of
that.
I
can
take
two
of
the
things
that
question
I
think
came
up
as
well
and
might
be
related
whether
it
is
cuda
aware
mpi.
I
I
We'll
know
that
it
will
be,
you
know,
built
in
and
provided
right
yeah.
We
will
not
have
an
open
mpi
build,
but
you
will
you're
more
than
welcome
to
have
your
own
we're
going
to
be
able
to
assist.
You
did
not
quite
understand
the
question
where
the
problem
are
having
hit
hip
is
mostly
used
on
the
for
the
gpu
side
of
things
for
amd.
I
I
That's,
I
think,
that's
a
fair
point,
but
at
the
same
time
I
think
it
is
also
like
hip
is
currently
developed
by
amd.
So
like
there
are
performance
implications.
I
mean
when,
even
if
you're
using
hip
to
run
it
on
an
nv,
nvidia
gpu,
which
is
what
like
like
all
cf,
is
doing
right.
You
can.
You
can
run
that
on
summit
and
you
can
run
it
on
frontier
as
well,
but
but
I
agree
that
having
that
option
would
be
something
nice,
but
I
don't
believe
at
this
point.
F
H
H
A
Yeah
in
in
a
way,
I
guess,
chip
and
cuda
are
both
fairly
low
level
programming
models,
so
so
there's
sort
of
a
lot
to
be
said
for
using
higher
level
ones
if
you're,
if
you're
starting
a
new
project
and
deciding
whether
to
use
hip
or
cuda.
Maybe
it's
worth
considering
using
neither
and
using
perhaps
openmp
target
offloading
or
kokos
or
raja.
E
E
D
A
A
A
Yeah,
I
don't
recall
off
the
of
the
top
of
my
head,
whether
the
caveat
with
the
with
the
cray
compiler
was
was
for
single
source
file
or,
for
you
know,
even
across
source
files,
but
it
was
about
the
the
data
location
rather
than
mixing
the
you
know,
openmp
and
acc
directives
for
actually
you're
doing
the
offloading
we're
going
to
turn
the
kernel
into
a
so
yeah.
I
guess
the
the
summary
version
is
interoperability
might
be
possible,
but
it's
not
trivial,
so
yeah,
avoiding
it
where
you
can.
H
A
G
A
G
A
Had
possible
to
do
so,
yeah,
I
don't
remember
if
we
have
any
kind
of
you
know
really
ready
tests
for
that,
but
it's
definitely
one
to
keep
in
mind
so
we're
getting
we're
getting
close
to
the
top
of
the
hour
and
it
sounds
like
the
the
rate
of
questions
and
comments
is
slowing
down.
Does
anybody
have
any
final
questions,
comments
or
tips
before
we
move
on
to
our
next
section.
A
So
flipping
back
through
to
our
last
couple
of
sessions
coming
up
we're
always
looking
for
topic,
requests,
topic
suggestions
even
better.
If
you'd
like
to
show
off
your
work,
this
is
a
good
forum
for
it.
You
know
10
or
15
minute
slot
time
for
some
q
a
time
for
a
quick
overview
of
what
you're
using
nurse
for
and
tips
and
tricks
that
you've
learned
or
you
know
gotchas
that
might
help
or
you
know,
simply
interest
other
nurse
users.
A
That
so
our
final
section
is
a
quick
look
over
last
month's
numbers,
so
for
may,
we
had
generally
generally
pretty
high
availability.
We
did
have
a
couple
of
unscheduled
adages,
due
in
one
case
to
a
essentially
a
hardware
issue
with
the
power
supply
and
another
brief
outage.
While
due
to
some
luster
issues,
the
user
experience
was
scratch
hanging.
We
had
a
normal
scheduled
maintenance
other
than
that
things
kind
of
ran
reasonably
smoothly.
A
So
we
tell
you
really
large-scale
stuff
and
we've
seen
that
quite
high,
actually
for
for
quite
a
while
now
inquiry,
it's
been
sitting
up
over
over
30,
for
I
think
at
least
the
last
year,
our
ticket
incoming
and
outgoing
rates
seems
to
be
sitting
reasonably
steady,
they're
going
out
at
about
the
the
same
rate
that
they're
coming
in.
They
have
a
current
backlog,
a
little
over
or
somewhat
somewhat
over
400
tickets.
A
So
that's
our
current
state
and
all
that
we
have
for
today's
meeting.
Thank
you
all
for
joining
continue
the
chat
in
the
webinars
channel,
I'll
capture,
the
chat
on
zoom
and
post
a
few
of
the
links
that
people
posted
there.
I
think
there's
some
some
good
tips
and
the
recording
should
arrive
and
have
a
link
to
it
from
the
from
the
meeting
website
fairly
soon.