►
From YouTube: NUG meeting, Feb 2022
Description
NUG meeting, Feb 2022
A
So
welcome
to
the
february
monthly
meeting.
Thank
you
all
for
for
joining
us.
The
usual
sort
of
housekeeping
to
begin
with
this
is
this
is
intended
to
be
a
pretty
interactive.
You
know
not
overly
formal
meeting,
so
please
participate.
You
know
your
way
of
handling
or
just
speak
up.
There's
a
small
enough
group
of
us
today.
I
think
that
we
can
freely
talk.
A
So
our
first
item
is
win
of
the
month.
This
is
an
opportunity
to
show
off
an
achievement.
Shout
out
somebody
else's
achievement.
It
can
be
bigger.
It
can
be
small
like
just
something
that
makes
you
feel
good,
that
yeah
yeah.
That
has
happened
in
the
last
month,
but
yeah
interesting
for
the
rest
of
us
to
hear
as
well.
Yeah
things
like
have
a
paper
accepted
or
solve
something
challenging.
A
A
Maybe
we'll
jump
across
two
or
combine
this
with
the
sort
of
the
flip
side
of
that
which
is
today.
I
learned
this
is
a
good
time
to
talk
about
also
yeah,
well
things,
the
things
that
you
learned,
because
you
stumbled
across
them
and
and
interesting
for
other
users,
but
also
things
that
are
bad,
challenging
and
difficult,
something
you
got
stuck
on.
B
So
every
now
and
then
I
don't
know
if
it's
a
version,
change
an
anaconda
or
something
it
might
say
things
like.
Oh,
I
can't
build
mpi
for
pi
and
it
and
it
shows
a
path
to
a
linker
there,
that's
clearly
in
a
conda
directory
and
the
the
lesson
there
is,
if
you
see
that
one
way
to
solve
that
problem,
but
it's
more
of
a
hack
really
is
to
move
it
to
separate
locations
so
that
the
system
uses
the
linker
that's
in
the
normal
system
path.
A
A
A
D
A
B
B
That's
to
say
the
new
way
to
do
it
is
to
use
a
a
system
that
doesn't
clobber
your
settings.
So
there's
that
so
there's
there's
still
some
outputs
in
conda
that
use.
That
kind
of
linkage
and
and
the
other
thing
that
is
worth
pointing
out,
is
you
have
something
like
a
conda
site
configuration
it's
your
dot,
con.rc
file
and
that
will
like.
D
D
B
Yeah
yeah
yeah,
I
was,
I
was
helping
a
user,
they
had
an
install
script
and
I
was
installing
everything
it
worked
fine
and
they
were
installing
something
and
crashed.
And
then,
in
this
case
it
turned
out
that
they
had
a
conda,
a
c
file
and
I
hadn't
no.
I
had
no
idea
to
look
for
it
because
you
also
have
the
conda
init
script
that
lands
in
your
bash
rsc
file.
So
that's
what
I
looked
for,
but
so
yeah.
A
B
Yeah,
if
someone
here
knows
a
tool
that
I
can
just
like
run-
and
it
says
you
know
I
on
this
in
this
environment-
I'm
config
figured
like
this
like
similar
to
like
python
dash
and
site,
and,
and
it
tells
you
these
are
the
paths
I
know
and
and
these
are
the
environment
variables
that
influence
those.
If,
if
we
had
something
like
that
for
for
like
conda,
that
would
be
brilliant.
That
would
make
diagnosing
these
things
so
much
faster.
E
B
A
B
A
A
It's
a
it's
a
it's
a
necessary
upgrade
and
it
changes
a
few
things
kind
of
underneath
in
there
in
the
linux
system.
That
means
that
you
know
all
a
lot
of
things
will
just
continue
to
work.
Some
may
not,
and
in
particular
I
think,
there's
a
new
version
of
glibc
so
we'll
need
to
re-link
things
the
things
that
are
dynamically
linked
kind
of
get
this
automagically.
E
A
It's
probably
a
good
excuse
to
rebuild
them
with
newer,
compilers,
newer
libraries
and
so
on.
Like
that
another
one
looks
like
I
missed
the
balding
on
this
summer.
Internship
time
is
not
quite
upon
us
yet,
but
the
the
point
in
the
process
where
interns
are
applying
for
positions
and
and
organizations
like
nurse
go
looking
for
interns
is
upon
us
and
nurse
actually
has
a
whole
bunch
of
projects
listed
on
this
web
page
here
yeah
as
proposed
intern
projects
that
we're
looking
looking
for
summer
interns
to
come
and
join
with.
A
There's
a
couple
of
training
and
sort
of
workshops
coming
up
so
in
about
a
week's
time,
there's
an
nvidia
performance
tools
for
a100s:
that's
our
gpu
on
perlmutter
training,
so
it's
february
23rd,
which
is
right
about
this
time.
Next
week
we
have
a
introduction
to
programming
with
sickle
on
pearl
mudder
and
beyond
on
march
1st
and
not
so
much
hosted
by
nurse,
but
but
that
we
are
aware
of-
and
these
tend
to
be
interesting,
there's
an
ideas.
A
A
B
B
It's
good
yeah.
I
don't
hear
any
complaints
so
yeah.
So
if,
if
we
looked
at
our
documentation
the
route
of
our
documentation,
you
basically
would
be
greeted
with
this
screen
and
there's
actually
now
a
new
page,
a
new
top-level
page
called
contributed
tips
and
tricks,
and
if
you
go
there,
you
are
actually
sort
of
pointed
at
this.
B
B
B
Just
you
know
the
common
issues
that
you
might
have
when
writing
the
markdown
format
for
the
the
documentations
page
so,
for
example,
how
to
make
a
link
with
relative
path
and
absolute
well,
don't
use
but
yeah
how
to
create
linking
using
relative
paths
how
to
include
code,
those
sort
of
things
now
I
thought
it
might
be
nice
just
to
to
show
you
how
this
works
in
action,
so
I'm
risking
a
live
demo.
Now
it's
probably
gonna
fail,
but
but
I
thought
it
might
still
be
instructive.
B
B
B
B
Here's
our
repo,
the
first
thing
that
that
you
might
want
to
do
is
create
a
way
for
you
to
be
able
to
synchronize
your
local
fork
with
the
main
fork
that
that
actually
is
part
of
our
documentation.
So
the
first
thing
what
we
want
to
do
is
we
want
to
go,
get
remote,
add
upstream,
and,
of
course,
you
need
to
know
the
url
of
the
upstream
repo.
So
I'm
going
to
go
back,
I'm
going
to
go
and
oops.
This
is
still
my
my
one
yeah.
This
is
the
right
one.
B
Okay,
so
now,
if,
if
I
went
get
remote
oops
remote
minus
v,
it
shows
you
that
the
origin
of
this
local
copy
is
my
personal
fork,
and
then
I
have
an
upstream
remote.
That
is
the
the
upstream
gitlab.
So
you
would
for,
for
instance,
say
get
called
upstream
main
and
that
will
get
you
the
the
latest
version
that
that
we
are
currently
having
in
production
at
nurse.
It's
always
helpful
to
do
this
before
you
start,
making
a
merge
request
to
just
make
sure
that
your
merge
request
is
based
on
the
latest
version.
All
right.
B
The
next
thing
is,
you
might
want
to
prototype
locally.
That's
pretty
easy
too,
because
we
have
a
requirements
text,
so
you
can
go
pip,
install
mine's
our
requirements
and
that
will
go
through
and
try
and
find
okay.
So
I
mean
I
had
most
of
these
things
installed
already,
but
but
you
would
probably
see
some
things
being
installed
and
now
you
actually
have
all
the
tools
that
you
need
to
actually
build
the
documentation
locally.
So
if
you
look
at.
B
B
B
Where
is
this
file,
and
so
the
easiest
way
to
find
out
where
this
particular
file
is
located
in
on
gitlab
is
to
click
on
this
gray,
pencil
or
pen
icon
up
here,
and
it
will
actually
redirect
you
to
the
markdown
file
that
that
that
page
was
rendered
from,
and
so
you
can
see
the
path
of
stocks
analytics,
desktop,
md
and
and
gitlab
shows
you
its
own
impression
of
how
this
is
rendered.
But
let's,
let's
go
back
to
our
build
okay,
so
it
builds
our
documentation.
B
B
B
And
that
is
now
a
local
version,
so
let's
say
you
want
to
make
a
change
and
a
really
quick
change
that
I
can
already,
and
that
already
noticed
here
is
maybe
I
want
this
here
to
not
say,
contributed
tips
and
tricks,
but
contribute
tore
tips
and
tricks.
I'm
not
saying
that
we
actually
want
to
put
this
into
production,
but
I
don't
know
maybe
I'm
nitpicking,
but
maybe
I
want
to
change
this
this
title.
This
also
indicates
another
aspect
of
macdocs.
B
I
haven't
actually
tried
this
change,
so
this
is
really
going
to
be.
What
is
it?
Live
live
production,
so
I'm
just
going
to
go
and
open
a
new
channel.
Excuse
me
whoa.
This
is
this
is
hard
I'm
not
used
to
working
at
this
resolution.
There
we
go.
So
let's
go
back
to
our
repo
okay,
there's.
Actually
one
thing
that
you
might
need
to
keep
in
mind,
and
that
is
these
things
here,
these
menu
items
they
are
actually
defined
in
a
yaml
file.
B
B
B
B
B
B
B
Local
preview,
what
you
need
to
do
is
you
need
to
somehow
tell
us
that
you
would
like
to
make
this
change
and
the
way
that
I
recommend
you
do.
It
is,
first
of
all
you
you,
let's
have
a
look
where
we
are
well.
We
are
on
the
main
branch.
So,
first
of
all,
I
recommend
that
you
go
get
check
out
minus
b
and
then
a
name
for
your
branch.
So
let's
go
jpb.
I
always
like
to
append
my
initials,
but
that's
just
it's
not
necessary
menu
change.
B
Now,
I'm
in
the
menu
change
branch
I
can
now
go.
We
look
at
what
files
have
changed.
Yes,
this
is
the
file
I
want
to
add
by
the
way,
if
you
here's
a
little
git
trick,
if
you
don't,
if
you
want
to
add
all
changed
files-
and
you
don't
want
to
go
and
type
in
the
filenames
of
all
the
files
that
we've
changed-
let's
go
add
dash
minus
use,
so
those
are
all
the
updated
files
hit
commit
suggest
this
section.
B
Okay,
that's
still
not
enough
to
actually
tell
us
so
now
you
want
to
go
get
push,
but
the
thing
is:
this
branch
doesn't
exist
on
your
local
gitlab.
So
let's
push
it.
Let's
just
follow
this
git
instruction
here.
This
will
make
the
put
the
change
in
origin
and
by
the
way,
if
you
go
get
remote
minus
v,
you
see
that
origin
is
your
version,
so
so
there's
no
harm
in
actually
pushing
it
to
this
location
and
there
it
is
now.
B
It
notices
that
your
you
have
made
a
change
to
your
local
branch,
so
so
you've
made
a
change
to
a
branch
in
your
local
fork.
Right
so
and
it's
it's
saying
well,
this
is
a
forked
repo.
So
so
do
you
want
to
actually
create
a
merge
request,
so
it
actually
recommends
it
as
sort
of
a
tooltip
here
go
here
and
then
you
would,
for
instance,
fill
in
a
title
and
a
description
here.
There
is
a
template.
A
B
Yeah,
I
would
have
thought
that
it
inherits
the
the
templates
I
at
this
point.
For
the
sake
of
of
gravity,
I
would
say
that
we
want
to
make.
We
have
some
templates
for
these
things.
I
I
can't
find
them
right
now,
but
I'm
gonna
move
on
and
at
some
point
those
templates
might
appear
here
and
and
I'll
revisit
it.
If
we
have
a
moment
at
the
end,
because
there's
still
two
more
things,
I
want
to
talk
about.
A
B
B
B
B
B
And
then
we
can
go,
compare
branches
and
continue
there.
It
is
there
we
go
and
then
also
fills
in
this
little
template
for
your
for
the
text
for
your
merge
request.
So
your
suggests
that
you
put
a
descriptive
title
and
then
you
look
at
at
each
of
these
things
that
you
should
check
off
here.
So,
for
example,
we
know
it
renders
correctly,
so
you
put
an
x
there
and
I
didn't
change
it.
B
B
B
D
B
Okay,
and
and
the
like,
all
the
information
is
available
in
the
in
this
contributing
dot
md
file,
I
don't
think
it
says
to
keep
and
watch
out
for
the
for
the
template,
but
it
does
tell
you
how
to
create
a
merge
request,
and
so
you
it's
it's
a
it's
a
little
bit
of
a
workflow
that
that
requires
getting
used
to.
But
it's
not
an
unusual
get
workflow
so
yeah
anyway.
B
A
B
Yes,
okay,
that's
a
good
point,
so
I
think
yeah
I
haven't,
have
a
look
at
the
signing
reviewers
that
that
is
always
a
way
to
get
attention,
but
and
that's
what
steve
just
said,
I
just
I'll
demonstrate
it
now.
If
I
act
and
then,
for
example,
I
can
add
steve
league
now.
This
would
at
this
point,
when
you
hit
submit
steve,
would
get
an
email
or
and
if
he's
turned
it
off
he's
watching
the
his
notifications,
he'll
get
notified,
and
so
that
is
the.
B
So
if
you,
for
example,
I've
been
in
this
situation
before,
where
someone
opens
a
ticket
and
says
how
about
changing
the
documentation,
and
I
recommend
that
they
do
it
themselves.
This
would
be
really
good,
because
then
you
can
point
back
to
that
nurse
staff.
Member
that
encouraged
you
to
make
this
change.
They
already
know.
What's
going
on
all
right
and-
and
just
I
think,
the
last
point
I
wanted
to
make
about
editing
this-
this
documentation
is:
let's
say
you
want
to
make
a
fairly
minor
change
like
this
one.
B
Now
it's
been
what
I
did.
There
was
pretty
involved
right,
like
you,
make
a
local
clone
and
edit
a
file
and
preview
it
locally.
So
let's
I'm
not
going
to
make
this
merge
request,
because
you
know
I'm
not
actually
that
persnickety
about
titles,
but
let's
say
we
want
to
do
the
same
thing.
Let's
make.
Let's
say
we
want
to
make
that
change
to
desk.
B
B
B
B
Remember
stocks,
jobs,
examples
index
right,
so,
let's
go
to
to
the
same
yeah,
docs
jobs,
examples
index,
so
so
this
is
the
same
file,
but
but
it's
now
the
local
fork,
sorry
that
your
own
fork
rather
than
nurse
production
version,
and
then
you
can
click
on
the
web
ide
and
that
will
open
up
an
ide
for
you.
You
can
even
preview
markdown
by
switching
the
tab
up
here.
B
This
is
this:
is
gitlab
markdown
not
make
docs
markdown,
so
there
will
be
differences,
but
so
I
still
recommend
and
to
use
the
local
copy
with
a
preview
with
mac
docs
for
larger
changes.
But
let's
say
you
have
a
typo
here.
I
don't
know,
I
actually
don't
know
of
any
typos,
so
I'm
going
to
introduce
a
typo.
B
E
B
And
you
have
the
same
template
again
so
so,
basically,
now
you've
seen
two
approaches.
One
is
a
little
bit
more
involved
for
larger
changes
and
if
you
spot
a
typo-
or
you
know
like
like
very
quick
change
to
some
text,
you
can
always
use
the
web
id
all
right.
I've
been
talking
for
ages,
I'm
gonna
stop
now.
A
B
B
A
Make
this
a
little
bit
smaller
so
sometimes
when
you've
got
a
chip,
it's
yeah,
it's
fairly
easy
to
find
where
it
belongs.
So
so,
for
instance,
if
you've
got
an
example
that
you
you
spot
something
here,
that's
or
something.
That's
not
here!
That's
useful!
This
is
a
good
page
to
add
it
to
if
you've
got.
A
B
A
A
A
First
of
all,
coming
up
one
that
maybe
next
month
or
maybe
the
month
after,
but
I
I
suspect
this
will
be
interesting
to
some
people.
Is
our
annual
user
survey
closed
recently
and
we're
looking
through
the
results
now
and
assembling
our
our
nurse
annual
report
that
uses,
amongst
other
things,
the
information
that
that
we
learned
in
this
survey
and
yeah?
A
We
might
do
a
little
bit
of
an
overview
of
some
some
themes
that
we
discovered
looking
through
what
what
people
have
replied
in
the
survey
we
are
also,
we
had
a.
We
had
a
really
really
great
talk
from
koichi
last
month
about
the
work
he's
doing
and
using
the
the
queue
system
to
optimize
this
whole
throughput,
not
just
the
immediate
job
and
yeah
sort
of
yeah,
really
interesting
and
prompted
some
sort
of
discussion
and
further.
You
know
collaborations
and
interactions
later
and
yeah.
A
I
think
this
is
a
really
good
thing
to
have
in
these
meetings.
So
if
you
have
something
that
you'd
like
to
tell
us
about
or
alternatively,
if
there's
a
topic
you'd
like
to
hear
about
that,
yeah
you
just
like
to
propose-
is
that
can
we
have
this?
As
a
topic
that
you're
not
necessarily
the
one
to
present,
let
us
know
about
it
so
to
make
it
easier
to
let
us
know
about
it.
A
We've
got
this
format
now
that
you
can
fill
in
it's
a
it's
a
pretty
simple
form.
It's
really
just
a
place
to
put
your
your
ideas
in
a
contact
point,
so
I've
just
put
the
link
in
the
chat,
click
on
it
and
yeah.
Let
us
know
if
you've
got
something
something
to
present
as
a
topic
of
the
day
or
or
something
that
you'd
be
interested
in
us
discussing.
A
A
A
A
For
availability,
I've
been
kind
of
exploring
some
of
the
different.
You
know
chart
tools
that
we've
got
for
this
and
it's
it's
a
little
bit
different
to
see
the
you
know
the
variation,
but
I
think
what
this
does
show
is
that
it's
very
close
to
100
percent.
It's
up
yeah
so
last
month
for
knl
nodes
availability
was,
you
know,
99
and
a
bit
percent
and
then
the
that's
the
scheduled
availability
and
the
overall
availability.
You
include
the
times
that
it
was
down
for
schedule,
maintenance.
A
A
Yeah,
so
it's
a
little
hard
to
see
here,
but
that's
100
down
here-
and
this
is
90
down
here,
so
so
guess
what
maybe?
What
the
shade
is
useful
for
is
kind
of
to
draw
the
eye
to
where
the
interesting
data
is
it
would.
It
would
be
interesting
if
we
had
a
great
dipping
me
in
the
availability
that
happened
somewhere,
that
you
know
what
what
would
the
gradient
do
there?
Would
it
go
down.
A
So
we
have
our
capability
metric,
which
is
that
yeah
systems
like
corey
nurse
systems
are
very
you
know.
Large
cutting
edge
kind
of
systems
and
part
of
the
the
motivation
for
having
these
systems
is
to
have
a
system
that
can
be
used
for
work
that
just
can't
be
done
on
a
smaller
cluster
and
yeah
as
part
of
making
sure
that
we're
actually
achieving
that.
One
of
the
the
metrics
that
we
report
is
how
many
jobs
used
more
than
a
certain
fraction
of
the
machine.
A
So
I
think
our
number
is
more
than
1024
nodes
on
on
corey
and
we
yeah.
We
aim
to
have
certain
like
25
of
the
work
on
corey,
being
this
really
large
scale
difficult
to
do
anywhere
else
kind
of
work
and
in
december,
actually
it
was.
It
was
quite
high.
Nearly
70
percent
of
the
work
on
corey
was
up
and
over
that
threshold
our
open
ticket
seems
to
be
sitting
pretty
steadily
the
incoming
rate
and
the
outgoing
rate
is
about
the
same
so
hooked
up
a
little
bit
around
the
end
of
january.