►
From YouTube: NUG Monthly Meeting 16 Dec 2021
Description
Recording of the NUG Monthly meeting on Dec 16, 2021
A
A
A
We've
got
about
20
people,
so
I
think
when
you've
got
something
to
say
just
unmute
and
say
it
and
you
know
if
it
gets
too
noisy,
we'll
go
to
like
a
hands
up
or
something
but
keep
it,
keep
it
fairly,
informal
and
and
free
flowing
for
the
moment,
if
you're
not
already,
please
join
the
nurse
user
slack.
It's
a
really
good
forum,
for
you
know,
discussing
with
other
users
and
and
nurse
staff
who
are
sort
of
on
a
bit
of
an
occasional
basis.
A
A
You
know,
keeping
you
giving
giving
you
grief
for
a
little
bit
to
having
a
paper
accepted
somewhere,
something
significant
that
you
achieved.
You
know
when
you're
in
your
normal
work
that
might
be
a
candidate
for
a
award
at
nurse
high
impact,
scientific
achievement
or
innovative
use
of
high
performance
computing
award.
C
A
A
B
C
A
B
B
E
E
E
A
B
E
B
Yes,
I
mean
petsy
has
to
be
petsy
hyper
cuda,
so
that's
kind
of
the
main
thing
yeah
and
worked
with
mark
adams,
and
I
have
been
working
on
that
for
quite
a
bit
and
some
people
in
the
hyper
team,
so
yep,
but
it's
using
the
gpus
using
them
pretty
efficiently.
I
might
add,
okay,
that
seems
to
be
for
the
initials
for
these
initial
scaling
tests.
That's
like
the
first
initial
scaling
test.
That's
not
even
that's
without
any
optimization
on
pearl
motor
itself.
A
B
A
A
C
A
A
E
A
A
A
A
I
think
we
do
have
some
information
about
that.
Actually,
in
last
month,
no
the
month
before
in
october's
monthly
meeting
clayton
went
through
did
a
bit
of
a
walk
through
perk
up
and
sort
of
you
know
preparing
for
for
next
year,
and
one
of
the
slides
that
he
had
was
talking
about
that
you
know,
estimating
and
and
so
yeah
translating
their
scours
for
the
different.
A
You
know
for
the
various
resources
available
next
year,
so
that
slide
deck
should
be
available
on
the
the
webinar
site
from
it,
and
I
think
it's
also
somewhere
in
our
docs.
Although
I
don't
remember
exactly
where
to
look
that
up,
but
yeah
there
is
some.
There
is
some
guidance
about
that.
If
you
take
a
look
in
october's
meetings.
D
D
F
A
A
And
if
not,
we
can
hop
across
to
the
next
side
of
the
the
other
side
of
the
coin,
which
is
you
know
today.
I
learned
and
here
we're
interested
in
hearing
stories
of
something
that
surprised
you
that
might
benefit
others
to
learn
about,
and
this
can
be.
This
can
be
either
something
that
you
you
stumbled
across
or,
or
you
know,
learned
about
your
ways
of
using
the
system
that
improve
things,
but
it
can
also
be
you
know
something
that
tripped
you
up.
A
You
know
this
is
we
we
do
research,
we're
discovering
new
things
and
learning
things
the
hard
way,
all
the
time-
and
you
know,
rather
than
kind
of
being
you
know,
put
off
for
or
wanting
to
to
hide
the
things
that
didn't
work,
yeah,
there's
a
lot
of
benefit
in
actually
making
noise
about
the
things
that
didn't
work,
and
you
know
here's
what
didn't
work
and
here's
how
I
fixed
it
or
I
don't
know
how
to
fix
it.
Yet
maybe
somebody
else
does.
A
C
A
So
it
was
it
was
it
was
reading.
You
know
a
few
hundred
megabytes
of
file,
but
moving
several
gigabytes
backwards
and
forwards,
and
and
doing
you
know
millions
of
io
calls
and
so
yeah,
with
a
little
bit
of
digging
around
we're
able
to
establish.
That
was
that
it
was
using
a
list
directed,
I
o
in
fortran,
to
read
in
a
text
file
and
when
fortran
does
list
directed
io.
A
So
it
was
reading
132
bytes
at
a
time,
and
you
know
fetching
that
in
many
many
small
and
operations
and
of
course,
each
operation
actually
fetches
a
bigger
block
than
what
it's
reading
so
there's
a
whole
lot
of
operations
there
and
by
just
setting
an
environment
variable
and
the
intel
compiler
kind
of
has
some
environment
variables
for
runtime
behavior.
We're
able
to
greatly
reduce
the
number
of
reads
and
yeah
in
that
you
greatly
reduce
the
yeah.
A
The
overall
amount
of
time
spent
by
io
in
this
job-
and
you
know
the
whole
thing-
ran
a
whole
lot
faster.
So
it
was
a
really
interesting
thing
to
learn
using
using
darchan
to
sort
of
discover
what
it
was
that
was
going
on,
and
we
have
some
notes
about
that,
one
in
our
web
page
as
well,
and
there's
kind
of
a
little
script
it's
enabled
by
default.
So
you
know
most
code
that
you
build
unless
you've
explicitly
switched
it
off
will
be
collecting
this
io
data.
It
uses
the
mpi
layer.
A
A
A
Or
reuse
or
what
yeah
so
in
so
in
this
case
it
was
about
buffering.
So
so
the
file
was
being
read
from
the
community
file
system,
which
is
a
you
know.
It's
like
a
network
attached
file
system,
it's
not
it's
not
on
the
node
and
so
each
time
it
does
a
read
it.
It
features
kind
of
a
at
the
lower
level.
It's
fetching
a
bigger
block.
A
E
E
A
Oh
so
this
is
actually
using
in
inside
in
memory
in
the
fortran
runtime
library,
oh
okay,
so
when,
when
it
comes
down
to
the
posix,
read
calls
that
it's
doing
so
so
you
know
it
at
the
fortran
level,
you're
you're
doing
fortran
code,
but
underneath
it's
calling
these
system,
posix
kind
of
calls
and
each
list
directed
I
o
was-
was
essentially
calling
read
with
a
132
byte
buffer
to
read
into
and
so
by
changing
changing
this
environment
variable.
We
turn
it
into
like
a
10
megabyte
buffer.
A
A
And
if
you
do
a
module
list,
when
you
log
into
corey
you'll,
see
one
of
the
default
modules
is
darshan
and
what
having
that
module
loaded
will
do
is
when
you
compile
a
code,
it
the
compiler
wrappers
the
create
compiler
wrappers,
automatically
link
in
the
darshan
library.
If
the
module
is
loaded
and
then
at
runtime,
if
the
module
is
loaded,
it
will
collect
the
io
data
and
it's
basically
edge
each
time
it
does
a
posix
read,
call
or
an
mpi
io,
so
project
read
or
wrap
mpio
called
it
collects
information
about.
A
You
know
the
the
call
the
time
spent
in
the
amount
of
data
moved
and
it
puts
it
in
a
location
on
scratch
that
you
can
read
and
in
the
docs.
If
you
do
a
search
for
darshan
in
our
in
our
docs
you'll
find
some
notes
on
it
and
there's
a
script
there
that
you
can
basically
generate
a
pdf
of
the
kind
of
the
the
report
and
it's
kind
of
just
a
high
level
summary
report
of
things
like
the
other
bio.
A
E
A
A
And
if
not,
we'll
move
on
to
our
next
block
of
things,
which
is
announcements
and
calls
for
participation,
and
this
month
we
have
quite
a
few.
There
are
several
that
in
your
weekly
emails,
you
can
go
back
and
and
look
that
up
some
reminders
of
important
ones.
Alccc
pre-proposals
are
due
this
week
this
friday,
which
is
to
say
tomorrow
you
may
have
noticed,
particularly
if
you're
logging
in
from
lbl.
We
now
have
a
federated
id
pilot
and
what
federated
id
does
is.
A
Allow
you
to
use
your
own
institution
login
to
log
in
to
nurse.
You
can
link
them
together.
So
so
the
pilot
is
just
for
lbl
users.
So
if
you're,
if
you're
a
part
of
berkeley
lab,
you
should
be
able
to
or
when
you,
when
you
log
into
certain
nurse
things
like
you
know,
help.nurse
get
help.nurse.gov,
irs
and
so
on.
Have
the
opportunity
to
kind
of
link
your
if
your
lbl
account
to
your
nurse
account
and
then
you'll
be
able
to
log
into
those
nurse
services
with
your
lbl
login.
A
Heads
up
that
the
winter
holiday
is
coming
up
and
nurse
services
will
be
particularly
consulting
service
and
so
on
will
be
shut
down
during
it.
So
so
there'll
be
no
consulting
between
december
24
and
january
3
and
there'll
be
much
more
limited
account
support
than
usual.
The
systems
will
still
be
up
just
that
getting
getting
help
may
take
a
little
longer
and
of
course,
the
big
one
that
helen's
going
to
tell
us
about
in
in
much
more
detail
in
a
few
moments
is
that
the
allocation
year
transition
is
happening
on
january
19th.
A
I
see
there's
a
question
from
g
in
the
chat.
When
would
the
award
decision
of
2022
allocation
be
announced?
Oh,
I
think
that's
this
week
as
well
check
check
the
weekly
email
in
your
inbox.
I
think
there's
a
note
about
it,
but
I
think
that
that
one
is
planned
for
this
week
or,
if
not
then
next
week,
so
that's
coming
up
very
soon.
A
Hello
might
know
in
more
detail
a
few
announcements
about
goal
matter,
so
we
have
a
user
training
for
perlmutter
on
january
five
to
seven
there's
a
link
to
a
web
page
here,
we'll
post
these
slides
on
the
on
the
meeting
web
page.
So
you
can
just
click
on
that
link,
but
you'll
also
be
able
to
find
them
fairly
easily.
A
A
Other
people
might
have
news:
if
you're,
if
you
have
a
gpu
ready
workload,
you
can
get
early
access
to
palmata,
so
it's
still
not
open
in
a
general
sense,
it's
still
in
its
sort
of
early
access
phase,
but
we
have
a
access
request,
form
that
you
can
get
to
by
clicking
on
this
link.
Put
the
slides
up
shortly
for
gpu
ready
codes.
Also,
there's
a
few
kind
of
things
to
remember
when
you're,
using
both
palmata
and
cory
is
that
home
is
shared
on
both
systems.
A
Yet
more
announcements,
the
annual
nurse
annual
user
survey
is
currently
open.
I
know
we've
had
quite
a
good
number
of
responses,
but
not
as
many
as
we
would
like.
So
please,
if
you
haven't
participated
in
the
survey,
yet
please
do
so.
You
should
find
a
personalized
link
in
your
email
within
a
couple
of
weeks
ago.
Now
it
will
have
come
from
an
address
nurse
mbi,
mbri
research,
dot,
com
and
yeah.
Following
that
link
should
take
you
through
to
the
survey.
A
I
guess,
if
you
can't
find
it
in
your
email,
there's
a
chance
it
might
be
in
spam.
It's
worth
checking
that,
but
the
annual
survey
is
kind
of
really
valuable
for
nurse
on
on
sort
of
two
fronts.
One
is
that
it
helps
us
to
identify
areas
that
you
know
what
we're
doing
well
and
and
what
we
want
to
focus
on
for
improving
for
the
next
year
and
also
it's
very
valuable
in
our
reporting
back
to
doe,
which
you
know
affects
our
funding,
which
affects
resources
available
to
everybody.
A
F
F
Allocation
year,
2022
range
from
starts
from
january
19th.
It's
normally.
We
do
this
on
the
third
wednesday
of
january
and
until
the
so
tuesday
of
january
in
the
next
year.
The
make
sure
you
understand
that
the
last
year's
allocation
hours
do
not
carry
over
the
award.
Emails
will
go
out
this
week,
and
this
year
we
have
separate
cpu
and
gpu
awards.
The
cpu
awards
can
be
used
for
query
and
promoter
cpu
and
the
gpu
allocation
can
be
used
for
the
parameter
gpu.
F
F
F
Then
the
computational
systems
need
to
sync
up
with
this
active
database
and
we
need
to
clean
up
old
batch
jobs
that
are
do
not
have
the
allocation
continuing
and
we
sometimes
do
system
maintenance
on
the
day
as
well,
and
we
will
have
some
new
policies,
new
software
at
the
ui
transition,
so
there's
a
whole
web
page
and
you
can
read
more
about
it
and
also.
I
will
talk
briefly
today
as
well.
F
F
Doe
also
needs
to
validate
them,
so
no
user,
new
user
account
creation
or
validation
for
that
week
and
after
shortly
after
you
receive
the
your
awarded
projects
allocation,
then
the
pis
need
to
do
something
you
have
a
month
or
so
to
do
that
and
last
deadline
is
the
last
day
of
the
ay21,
the
pis
or
proxies
you
have
to
nominate
which
users
in
your
project
will
continue,
and
you
also
have
to
decide
which
user
will
have
premium.
Qos
access,
there's
an
api
in
iris
in
your
project
and
then
go
to
the
rows.
F
Tab
you'll
see
two
additional
columns.
It'll
only
exist
for
this
muscle,
so
duration
in
irs,
and
then
pis
can
go
in
and
check
box
for
of
your
users.
You
want
to
continue
and
enable
premium
and
there's
also
a
recommended
recommendation
for
pi's
users
to
check
your
premium
jobs
currently
in
the
queue,
and
maybe
you
want
to
update
them
to
regular
since
there's
a
chance
that
those
jobs,
if
they
didn't
run
now
and
they
start
to
run
next
year,
they
might
be.
F
F
On
the
start,
date
of
the
ay
2022,
it's
january
19th
in
the
morning
seven
o'clock,
the
irs
database
will
be
doing
the
new
transition
of
of
updating
to
all
the
new
allocation,
your
data,
so
if
you
usually
already
logged
into
that
to
ios
during
that
time,
you
need
to
log
out
and
back
log
back
in
to
see
the
new
data
we'll
have
a
scheduled
maintenance
for
corey.
On
that
day
and
for
perimeter
we
have
decided
not
to
do
a
downtime
this
week.
F
There
is
actually
one
maintenance
with
this
two
maintenance
one
week
before
and
one
week
after
for
more
unsubstantial
system
upgrades,
but
during
this
transition
day
on
this
day,
and
the
only
thing
we
need
to
do
is
these
learn.
This
learn
database,
sync
with
iris
and
while
doing
this
live,
you
may
experience
a
very
short
period
of
slowness
other
than
that
system
actually
will
appear
to
be
on
up
and
the
other
system
services
will
be
up
on
that
day
as
well.
F
Also
on
this
ay
start
day,
we
will
process
some
and
delete
some
old
jobs
that
are
no
longer
no
longer
valid
for
the
new
year,
for
example,
jobs
associated
with
non-continuing
projects,
jobs
with
with
the
continuing
project,
but
the
user
is
no
longer
a
member
for
the
project.
This
can
happen.
If
your
pi
forget
to
renew
this
users,
they
have
premium
jobs,
you
not
have
access
to
the
premium
qrs
or
the
overrun
jobs.
Is.
F
F
Charging
factor
for
promoter
gpu
is
also
one,
and
if
you
want
to
convert
a
new
and
old
hours,
we
used
to
do
cpu
we
used
on
cpu
only
for
corey,
for
example.
Here
we
have
unit
of
nurse
hours,
which
is
based
on
hopper
cpu
hours
now
to
do
the
based
on
the
capacity
and
performance
we
decided
this.
The
equivalent
factor
is
one
new
parameter.
Cpu
node
hour
is
the
equivalent
of
400
node
hours
on
hopper.
F
So
here
is
a
table
that
you
can
see
for
for
first
charging
unit.
You
can
see
the
the
unit
here
and
a
house
wall
in
ay
2021,
the
charting
factor
was,
is
140
divided
by
400,
and
the
new
charging
factor
would
be
0.34
and
k.
L,
a
the
original
80,
the
chinese
factor
of
80
divided
by
400,
is
0.2,
so
you
might
see
a
small
number
of
allocations
and
don't
don't
be
panic,
don't
panic
it's
times
400!
It's
about
equivalence
of
you
are
getting
for
the
next
year.
F
For
the
gpu,
they
don't
list
it
on
the
table.
There's
only
one
system
parameter,
it's
one
and
the
future
system
will
be
based
on
the
parameter
fact
factor
so
for
the
changes
and
for
ay
2022,
we
have
a
new
default
python.
Module
it'll
be
changed
to
3.8
anaconda
2021.5,
it's
python,
3,
normal
python,
2
support.
F
F
We
will
also,
we
also
plan
to
do
a
big
query.
Os
upgrade
to
accommodate
the
the
the
system
up
system
need
for
for
supporting
matching.
You
know,
for
example,
the
security
requirement
from
from
our
hpe
from
doe
management
so,
and
we
promise
this
is
going
to
be
our
last
major
planned
major
os
upgrade
unless
there's
another
critical
search
security
concerns.
F
It
includes
all
these
crazy
supported
packages
such
as
mpi
lip,
sci
net,
cdf,
hdf5,
compilers
performance
tools,
a
lot
of
things
in
it
and
each
so
if
we
upgrade
a
cdt
version,
meaning
we're
going
to
get
all
these
packages
having
a
new
software
default,
then
we're
also
going
to
upgrade
not
upgrade
or
change.
Our
intel
compiler
default
version
to
a
newer
version,
then
we'll
provide
a
web
page
later.
With
all
the
details
of
this
version,
change.
F
The
last
slide
about
discontinued
users,
if
users
with
no
active
project
for
new
year,
they're,
considered
discontinued
as
effective
on
the
first
day,
but
they
will
have
a
month
to
access
the
systems.
They
cannot
run
batch
jobs,
but
they
can
log
in
access
their
files
and
bring
them
back
to
their
system
for
longer,
storage
hpss.
They
still
have
write
access
for
one
month
and
then
five
more
months
to
read
only
and
then
they'll
have
no
access
to
hpss.
F
E
E
F
Doesn't
mean
cory
will
be
updating
every
three
times
a
year.
I
was
talking
about
this
great
pe
called
cdt,
create
performance
tool,
create
developer
toolkit
release
is
three
times
a
year.
We
don't
have
to
install
them,
we
don't
have
to
change
our
default.
This
is
just
their
release
in
the
past.
They
do
release
this
every
month
and
we
were
doing
about
quarterly
installation-ish,
newer
versions,
but
also
we
were
having
like
a
year
or
so
to
do
to
change
our
default.
F
F
F
E
A
F
D
F
Yeah
just
go
ahead
and
ask
your
question
and
take
it,
so
I
didn't
mention
it
explicitly
in
the
talk
today
in
the
arcc.
Lcc
actually
goes
six
months
off
cycle
of
our
cap,
so
the
alex
llcc
allocations
runs
from
june
july
to
june
and
the
the
allocation
request
also
it
goes
through
a
different
cycle.
Obviously,.
A
So,
coming
up
next,
we
are
always
looking
for
interesting
topics
for
these
monthly
meetings.
Tentatively
next
month,
one
of
our
regular
participants
will
present
some
work
that
they
have
done.
So
that
should
be
should
be
really
good.
We're
also
planning
a
topic
around
nurse
documentation
and
yeah
what's
there
and
how
you
can
join
the
effort
and
contribute
yeah.
As
I
was
saying,
we're
always
very
interested
to
hear
what
our
users
are
doing.
A
A
A
A
So
what
this
chart
is
showing
the
texture
is
a
little
bit
small.
The
top
chart
is
for
haswell
and
near
the
the
end
of
november,
beginning
of
december,
we're
kind
of
hovering
a
little
over
7.5
kind
of
eight
q
backlog
of
7.5
or
8,
and
what
that
means
is
that
there's
7.5
or
8
days
worth
of
work
using
all
of
the
resources
of
the
query
as
well
nodes.
A
So
if
all
of
the
queued
jobs
ran
for
the
entire
time
that
they
requested-
and
you
know
often
jobs-
you
know
request
more
than
what
they
need
is
a
little
bit
of
a
buffer.
So
this
can
be
a
slight
over
estimate,
but
it
would
take
seven
and
a
half
days
for
all
that
work
to
get
through
the
queue
and
which
can
sort
of
give
some
hints
about
how
long
you
can
expect
a
job
to
wait,
particularly
if
it's
a
if
it's
a
long
job
short
jobs,
can
usually
jump
the
queue
and
start
earlier.
A
We
have
a
lot
more
knl
nodes,
the
bottom
changes
knl.
We
have
a
lot
more
known
nodes
than
haswell
nodes
and
the
backlog
on
that
one
is
that
this
is
actually
quite
difficult
to
read,
but
I
think
it's
about
they're
hovering
around
the
four
mark.
So
it's
a
useful
chart
to
look
at
if
you're
wondering
where
your
job
is
in
the
queue.
E
A
Yes,
there
is,
there
is
another
page
on
my
dirtnurse.gov,
I
think
it's
under
it's
either
under
jobs
or
under
center
status.
There
are
two
sections
that
overlap
a
little
bit
there
and
it's
about
average
queue
wait
times
and
that
shows
sort
of
for
different
sizes
of
jobs
in
terms
of
number
of
nodes
and
length
of
jobs
in
terms
of
number
of
wall
clock
hours
by
taking
a
sample
of
recent
jobs.
A
A
Essentially
different
types
of
requests,
but
you
can
see
the
the
number
of
tickets
coming
in
over
is
actually
over
over
a
couple
of
years
on
a
on
a
month
by
month,
basis
can
be
quite
high,
several
several
hundred
per
month
in
some
cases,
and
the
the
bottom
line
here
is
the
number
of
kind
of
active.
You
know
currently
open
tickets,
this
this
one's
only
over
a
month.
E
A
A
Get
a
lot
of
questions
about
corey,
a
lot
of
questions
about
sort
of
allocations
and
iris
requests
for
access
to
things.
This
is
this
is
quite
a
broad
swathe
of
tickets,
and
it
also
includes
things
that
you
know
are
more
kind
of
off
off
to
the
edge
where
we're
seeing
more
tickets
about
pearl
mudder
good
number
of
tickets
about
you,
know
software
and
sort
of
understanding
well
either
either
using
or
installing
software
and
another
one
is
understanding
what
happens
with
jobs.
A
E
A
A
C
A
Very
high
scaling
file
system,
but
you
know
it
it's
a
it's
like
running
a
formula,
one
car
versus
running
your
own.
You
know
personal,
regular
car.
It
requires
a
little
bit
more
care
and
feeding
than
than
a
lot
of
other
file
systems
and
yeah
yeah.
Occasionally
things
kind
of
jam
up
in
some
way
or
another,
and
because
c-scratch
is
sort
of
fairly
fairly
critical
to
the
system,
it
can
cause
the
the
system
to
become
effectively
unavailable
for
a
while,
so
that
that
happened
here.
A
A
E
A
So
usually,
when
it's
an
unscheduled
outage,
it
means
that
something
kind
of
causes
the
system
to
be
not
kind
of
effectively
usable.
Okay.
You
know
it
might
be
stopping
jobs
from
starting
or
stopping
people
from
being
able
to
log
in
or
you
know,
if
the
file
system
is
so
frozen
up,
that
people's
sessions
freeze
when
there's
a
scheduled
outage,
it
is
usually
a
much
more
well,
it's
a
much
more
sort
of
controlled
shutdown
of
the
system
and
bring
back
up
for
maintenance.