►
From YouTube: NUG meeting 15 April 2021
Description
Tips about developing models with Mathematica, avoiding OOMs when using MKL with dynamic linking, and our topic of the day was a preview of NERSC's annual report
A
A
Yeah.
Also,
discussion
for
for
preference,
putting
discussion
in
the
nurse
user
slack
rather
than
the
zoom
slack
is
good,
because
then
the
discussion
continues
past
the
meeting
and
still
visible
afterwards,
and
for
this
we'll
mostly
use
the
webinars
channel,
hashtag
webinars
and
then
excuse
user
slack
sue
will
follow
our
normal
agenda
this
month,
which
is
start
out
with
a
win
of
the
month
and
followed
by
today.
I
learned
some
opportunities
to
talk
about
what
you've
achieved
and
learned
recently
a
few
announcements
and
calls
for
papers
topic
of
the
day.
A
A
I
saw
a
I
saw
a
thumbs
up
there,
so
that's
good
yes
great
to
you
so
win
of
the
month.
The
idea
of
this
segment
is
to
show
off
something
that
you've
achieved
or
shout
out
something
that
you
know
somebody
else
has
achieved.
So,
for
instance,
you
might
have
had
a
paper
accepted,
you
might
have
simply
solved
a
bug.
A
That's
been,
you
know,
challenging
for
a
little
while
you
might
have
a
significant
scientific
achievement
could
be
something
that's
also
a
candidate
for
a
high
impact
scientific
achievement
award
or
for
an
innovative
use
of
high
performance
computing
award
or
for
a
science
highlight
basically
yeah.
The
whole
range
we're
interested
in
sharing
small
wins
as
well
as
big
wins.
B
B
Using
using
corey
for
the
calculation
and
and
and
it
works,
so
I
just
wanted
to
point
out
how
corey,
having
all
these
features
available,
not
just
big
computer
power,
but
also
access
to
mathematica
right.
There
made
it
possible
for
me
to
generate
these
formulas,
write
them
and
then
have
mathematica
spit
out
the
program
spread
out
the
long
computer
code
and
paste
it
into
another
code
that
I
then
submitted
to
a
job
on
corey
and
it
all
worked.
So
so
that's.
A
Really
interesting,
if
I,
if
I'm
interpreting
right,
I'm
actually
hearing
kind
of
several,
what
would
you
call
it
yeah,
interesting
aspects
and
there's
there's
a
whole
sort
of
story
of
application
of
algorithm
development
here?
Is
that
correct,
so
so
you've
used
mathematica
by
the
sounds
of
it
to
prototype
a
new
algorithm
that
you're
developing
and
tenth
order?
That's
that's
hugely
precise
right.
B
B
But
basically,
the
starting
point
for
this
was
an
online
document
written
by
alex
drought,
which
is
about
a
2700
page
document
on
the
algebraic
methods
and
non-linear
dynamics.
If
anyone's
interested,
I
could
I
could
post
the
link
to
it,
and
that
document
describes
the
steps
in
an
algorithm
to
to
calculate
the
concatenation
formulas
order
by
order
right
and
and
then
I
was
able
to
reuse
some
existing
mathematica
code
that
I
found
in
a
paper
on
the
right,
nested
cbh
formula,
and
so
I
didn't
exactly
use
mathematica
to
prototype.
B
B
Oh,
this
is
a.
This
is
a
nothing
job.
This
is
a
quick
job
because
I
mean
a
few
seconds,
but
these
formula
because
they
can
the
concatenator
acts
on
them.
Oh,
does
it
take
a
few
seconds
yeah
a
few
seconds.
The
concatenator
at
the
moment
is
not
the
computational
bottleneck,
but
when
you
are
actually
tracking
particles,
then,
if
you're
doing
a
multi-particle
simulation,
the
parallelization
is
over
the
particles,
the
concatenator
itself.
B
B
A
B
I
don't
know
the
answer
to
that
question,
although
for
my
purposes
that
was
not
such
an
issue
there,
there
was
a
time
over
the
past
week
or
two
when
I
did
run
mathematica
jobs
up
to
eight
hours,
because
I
didn't
realize
that
there
was
a
way
to
make
my
jobs
run
faster
and
if
you'd
asked
me,
then
I
would
have
said
I
sure
wish
it
would
run
faster.
But
now
I
can
generate
the
the
tenth
order
formulas
with
mathematica
running
in
a
minute.
So
I
don't
know.
B
A
B
I
I
just
I
don't
happen
to
have
mathematica
on
my
laptop.
I
have
an
app
on
one
of
my
ancient
laptops,
but
not
on
the
laptop
I'm
using
now,
and
so
it
just
made.
It
was
very
convenient
to
log
in
to
ner
to
nurse.
Do
module
load
mathematica,
generate
my
formulas
and
paste
them
into
the
code
right
there.
So
and
these
things
and
these
formulas
are
hundreds
of
lines
long
at
their
worst
and
the
few
lines
long
at
the
best.
D
A
So
for
up
to
four
hours,
we've
got
the
interactive
queue,
which
is
a
reasonably
fast
way
of
kind
of
you
know
getting
onto
a
compute
node.
You
would
probably
need
to
set
things
up
a
little
bit
using
your,
for
instance,
nx,
so
that
you've
got
a
decent,
gui
connection.
If
you're
using
the
you
know
the
gui
for
it
but
yeah,
you
can
also
run
interactively
just
through
the
regular
queue
it
just
can
take
longer
for
the
job
to
get
in
and
be
a
little
bit
more
unpredictable.
A
You
know
in
terms
of
when
you
need
to
be
there
to
to
start
it
off
if
there's
an
interactive
component
but
yeah,
I
think,
there's
a
degree
of
you
know
sensible
judgment
there
right
now.
You
know
yeah
by
all
means
for
development,
work
and,
and
so
on,
like
that,
that's
a
that's!
A
great
use
of
the
login
nodes
as
yeah
yeah
as
the
intensity
starts
to
go
up,
and,
and
actually,
if
you
have
sort
of
your
questions
along
the
way,
how
do
I
make
good
use
of
the
compute
nodes?
A
A
And
learn
from
the
things
that
didn't
go
so
smoothly.
There's
this
old
saying
every
once
that
I
really
liked,
which
is
that
you
know
knowledge
comes
from
reading
the
fine
print
and
wisdom
comes
essentially
from
not
reading
the
fine
print
and
and
yeah.
This
in
a
way,
is
kind
of
what
we're
talking
about
here,
things
that
you've
discovered
it
doesn't
have
to
be
the
hard
way
it
can
be.
A
A
A
Cherry
picking,
specific
pull
requests
to
you
know
pull
just
a
particular
change
into
you
know
an
earlier
tagged
version
to
get
yeah
something
to
work
without
actually
using
the
cutting
edge
development
version
of
everything,
and
fortunately
it
wasn't
too
hard.
Although
I
did
manage
to
you,
know
mess
it
up
the
first
time
I
have
to
go
back
in
and
carefully
pull
out
just
the
pull
request
files
that
I
was
interested
in.
E
E
E
For
you
know
the
the
mcdrum,
I'm
sorry,
let
me
start
off,
so
this
environment
variable
is,
is
used
to
limit
the
mcd-run
memory
for
mkl.
So
if
we
don't
use
this,
then
it
will
just
use
its
unlimited
intel.
Mkl
can
use
whatever
available
just
to
use
unlimited
memory,
h,
mcd-run
memory,
so
after
you
know
set
to
this,
the
oom
problem
is
resolved.
E
So
actually
this
has
been
bothering
me
like
many
months
and
especially
we
need
to
use
dynamic
linking
for
checkpoint
restart
tool.
So
this
was
really.
You
know,
bothered
me
for
a
long
time,
but
now
I
think,
with
this
workaround,
the
problem
is
resolved,
so
I
think
if
any
users
who
whoever
use
mkl
on
knl
and
if
you
run
into
oom,
probably
you
consider
to
set
this
environmental
yeah
variable
it.
A
E
I
think
so
the
cache
mode
is
yummy
users
that
don't
have
the
control
right,
but
mkl
trying
to
use
this
mankind
to
you,
know,
control
the
memory
used
in
the
mcd
run
and
then
somehow
it
I
don't
know
for
whatever
reason
it
doesn't
work,
I
think
from
the
beginning.
I
guess
so.
Actually
this
environmental
module
is
something
I
I
mean
this
environment
variable
is
something
I
adopted
from
my
early
intel.
You
know
collaborators
yeah.
A
B
A
A
A
We
have
the
what
used
to
be
called
quarterly
allocation
reductions-
and
I
don't
know
if
they're
specifically
quarterly
anymore,
but
there's
a
couple
of
allocation
reduction,
dates
and
they're
set
for
may
4
and
september
7.,
and
what
these
are
is
because
you
know
predicting
exactly
how
much
you're
going
to
need.
You
know
several
months
in
advance
is
not
necessarily
easy,
and
so
we
kind
of
you
know
monitor
the
the
burn
rate.
A
A
Oh,
I
have
to
watch
that
a
little
bit
more
closely
thanks,
lisa
yeah.
So
if
you
have
any
sort
of
questions
about
the
allocation
reductions
and
and
the
reductions
that
go
back
into
the
pool
so
that
the
program
managers
are
able
to,
you
know
reallocate
the
you
know
the
unused
time
to
your
other
projects
that
need
it.
A
I
guess
there
are
some
circumstances
where
perhaps
you
you
know
that
your
project
is
going
to
use
most
of
its
allocation
during
a
very
short
time
of
the
year
and
it
might
be
after
may
4..
So
you
know,
if
you
do
have
these
known
circumstances,
you
can
you're
getting
contact
with
us
via
a
ticket
to
talk
about
it.
A
A
E
A
A
We
also
have
a
tutorial
coming
up
very
soon,
actually
in
april
so
next
week
for
time
memory,
I
think
that's
how
you
pronounce
it
and
that's
a
a
tool
that's
been
developed
within
nurse.
I
don't
know
if
jonathan's
on
the
call
at
the
moment,
I
think
he
is
but
so
this
is
a
tool
for
your
analysis
of
the
you
know,
performance
and
memory
use
of
your
application,
and
so
the
tutorial
is
part
of
part
of
the
ect,
the
ecb
program
for
that
coming
up.
A
A
A
So
anybody
who's
been
a
nurse
user.
For
you
know,
more
than
just
year
will
have
seen
nurse's
annual
survey.
Anybody
who's
submitted
tickets
will
have
seen
the
post-ticket
surveys.
We
make
these
sort
of
calls
regularly
for
nominations
for
awards
and
science
highlights,
and
you
know,
maybe
you've
wondered
what
does
nurse
actually
want
all
this
stuff
for
so
for
today,
we're
going
to
take
a
bit
of
a
sneak
peek
at
nurse's
annual
report.
A
Basically,
why
we
do
it?
Why
we
call
for
these
things
why
we
write
a
report,
how
we
use
the
various
data
that
we
gather
and
perhaps
most
importantly,
how
you
can
use?
I
guess
this
information
and
and
your
knowledge
of
what
nurse
kind
of
you
know,
goals
and
aims
are
to
improve
nurse's
ability
to
support
your
needs.
A
A
So
what
the
doa
wants
from
nurse
is
for
us
to
demonstrate
that
the
facilities
and
resources
we're
providing
are
effective
for
our
users
to
advance
advance.
Your
research
and
we've
kind
of
got
broadly
speaking,
two
tools
for
doing
this.
One
is
to
find
out
what
our
users
have
achieved
and
showcase
it
and
the
other
is
find
out
what
impedes
our
users
from
making
progress
or
what
makes
it
difficult
and
yeah
identify
things
that
we
can
improve
to
cause
more
success.
A
So
showcasing
user
achievements,
one
kind
of
yeah
almost
almost
blunt
instrument
here,
but
that's
an
important
one-
is
simply
counting
publications.
So
you
know
more
public
research
is
more
evidence
that
does
investment
in
nurse
is
reaping
dividends,
yeah
with
the
subtext
thereof.
So
it's
worth
investing
more
yeah.
This
comes
up
about
fairly
early
in
the
report.
A
In
2020,
we
identified
a
little
over
1800
articles
like
1830
or
860
articles
that
cited
nursk
as
a
resource
that
was
used
or
for
support
in
their
research,
and
so
this,
of
course,
bounces
into
you
know
how
you
can
help,
which
is
publish
stuff.
That's
that's
great
for
you,
and
it's
also
great
for
us,
especially
if
you
can
add
some
citation
that
acknowledges
use
of
nurse
resources
in
there.
So
when
we
do
the
report,
you
know
we
essentially.
A
A
So
this
was
also
kind
of
a
a
little
bit
of
a
win-win,
because
by
you're
showcasing
particular
research.
That
also
you
know,
brings
the
successes
of
that
of
that
research
project
into
the
does
sites
as
well
and
yeah.
It
was
also
kind
of
a
nice
point
to
be
able
to
show
off,
for
you
know,
collaborators
and
potential
collaborators
and.
A
A
Of
the
research
and
links
to
you
know,
who
did
it?
Who
was
involved?
There's
a
few
other
things
on
that
page
as
well.
So
there's
there's
some
sort
of
vignettes,
which
are
slightly
more
detailed
in
the
science
highlights.
Some
projects
also
from
this
page,
are
links
to
where
you
can
nominate
particular
achievements.
A
So
then,
on
the
other
side
of
it,
we
have
seeking
and
acting
on
user
feedback,
and
this
is
where
we
come
into
all
the
different
surveys
and
yeah
so
forth
that
we
spread
around
so
nist's
annual
survey.
You
will
have
seen
we've
been
doing
it
for
a
long
time,
which
means
we've
built
up
quite
a
history
of
data,
and
it's
changed
a
few
times
over
that
time.
A
A
A
A
I
think
it
goes
back
something
in
the
order
of
20
years
and
yeah.
We
have
a
target
which
is
roughly
corresponds
to
you
know,
moderately
satisfied
or
above
and
the
yeah
average
score
over
the
years
has
been
consistently
higher
than
it
one
change
that
happened
in
the
last
couple
of
years
as
we
we
switched
from
a
seven
point
scale
to
a
six
point
scale-
and
this
is
all
you
know.
E
A
A
The
other
aspect
of
the
survey
is
the
text
questions,
and
this
is
a
little
small
to
read,
but
so
we
ask
a
few
text
questions
about.
You
know
what
does
nurse
do
well
and,
and
what
can
nurse
do
to
serve
you
better
and
we
do
a
mixture
of,
or
rather
you're,
with
the
help
of
the
survey
experts?
We
do
a
mixture
of
analysis
of
both
the
the
scoring
sort
of
questions
and
the
text
questions
to
try
to
understand.
A
A
A
A
A
A
There
are,
we
have
a
lot
of
nurse
users
doing
a
lot
of
projects,
a
finite
number
of
resources,
and
so,
of
course,
you
know
there
is
a
queue
and
it
can
be
long.
The
approaches
that
nurse
has
been
taking
to
try
to
you
know
alleviate
some
of
this,
but
part
of
it
is,
you
know,
buying
for
ever
more
resources,
but
the
other
part
is
tuning
and
tweaking
things.
So
we
make
adjustments.
A
For
instance,
to
you,
know
cue
settings,
q
policies
to
try
to
increase
the
system
utilization
because
you
know
cycles
where
a
cd
compute
node
is
sitting
idle
that
doesn't
help
anybody,
so
the
better
utilization.
Overall,
we
can
get
that
the
better.
That
means
that
jobs
are
getting
through
the
queue.
A
So
what
else
can
you
do
then
back
to
showcase
your
work?
You
know
that
helps
to
make
a
case
for
more
money
and
and
bigger
resources,
but
also
in
their
everyday
day-to-day
as
a
general
tip.
Shorter,
wider
jobs
tend
to
work
better
with
the
scheduler,
and
if
your
work
is
amenable
to
it-
and
this
is
where
the
transparent
checkpoint
can
can
really
help
as
well.
Take
a
look
at
flex,
jobs
and
using
checkpoint
e
to
work
with
a
scheduler
and
use
the
gaps
in
the
schedule,
and
this
increases
the
utilization.
A
Overall,
summary
might
be
that
nursk
has
some
really
detailed
documentation,
but
it's
quite
complex
and
it
can
be
challenging,
especially
for
new
users
to
you
know,
get
up
and
started
so
that
that
was
useful
for
us
to
discover,
and
it
was
part
of
the
the
motivation
behind
you
may
have
noticed.
We
have
consulting
appointments
and
one
of
the
consulting
appointments
is
nurse
101.
A
These
are
all
under
there's
a
link
down
here.
Actually,
on
help.nurse.gov
down,
on
the
left
hand
side,
you
can
book
a
consulting
appointment
and
there's
a
list
of
types
of
appointments
so
for
new
users,
the
nurse
101
might
be
a
good
one.
So
you
know
one
to
one
getting
started:
we're
also
working
to
improve
the
documentation,
particularly
with
new
users
in
mind,
and
here's
where
our
existing
users
can
join
the
effort.
A
A
We
have
a
small
development
system
with
a
handful
of
nodes
that
have
gpus,
which
are
not
exactly
what
perlmutter
will
have,
but
it's
sort
of
in
that
direction.
So,
if
you're,
you
know,
testing
out
your
workflows
or
developing
code
using
corey's
gpu
development
nodes
is
a
good
way
to.
You
know,
get
a
bit
of
a
feel
of
it
there
and
build
it
there
and
you
you
can
request
access
to
those
also
via
the
help
system.
A
So
I
think
from
a
those
are
the
things
that
I
guess
jumped
out
to
me
as
being
yeah,
particularly
interesting
things,
for
you
know
I'll
use
a
community,
and
you
know
things
that
perhaps
you
can,
you
know,
take
some
sort
of
action
about,
and
there
are
no
doubt
many
other
things
that
are
interesting
there.
So
other
parts
of
the
annual
report
go
through
some
of
our
operational
numbers,
so
yeah
we
kind
of
bounce
off
this
a
little
bit
for
the
last
month.
A
Numbers
section
of
this
meeting,
which
is
coming
up
actually
in
a
moment,
there's
a
section
of
the
report
where
we
talk
about
innovations
that
are
happening
at
nursk
to
improve
nurse
operations
and
also
usability.
So
this
is
this
is
almost
kind
of
you
know:
research
into
or
yeah
yeah,
research
and
development
intended
to
improve
user
experience
in
coming
years.
A
So
it's
it's
quite
a
long
report,
but
you
know
there's
some
interesting
stuff
there
to
read
and
it
will
soon
be
available
at
this
web
page.
Ultimately,
I
think
that
the
key
thing
here
is
that
you
know,
with
with
the
annual
report
being
a
fairly
significant
part
of
it.
Nurse
goes
reviewed
based
on
how
well
we're
able
to
support
the
success
of
our
users
so
yeah.
A
Here's
what
the
front
page
looks
like.
There
are
quite
a
few
pages.
What
have
we
got
122
pages,
so
we
probably
don't
have
time
to
go
into
too
many
details
of
the
actual
content
in
this
discussion,
but
we
do
have
a
few
minutes
for
if
anybody
has
any
questions
or
comments,
I'd
like
to
make
you
know
about
the
process
or
you
know,
I
guess
things
of
interest
in
the
report.
A
D
A
A
A
I
see
because
she's
posted
in
the
chat.
Actually
this
is
this
is
a
good
idea
how
to
edit
and
contribute
to
this
documentation
as
a
monthly
topic.
That
would
be
a
good
topic.
Actually,
we
can
do
a
walkthrough
of
the
the
system,
so
we
use
a
system
called
mcdocs,
mk
docs
and
it's
essentially
marked
down
formatted
documentation
in
a
git
repository
that
we
accept
pull
requests
for
so
yeah
that
that
would
be
a
good
topic,
a
walk
through
how
to
contribute
thanks
kg.
A
And
finally,
last
month's
numbers,
so
much
uptime
wise,
we
had
a
a
really
good
month.
We
had
no
unscheduled
down
times.
I
think
the
message
of
the
day
did
show
one
unscheduled
downtime,
but
it
turned
out
to
be
a
false
alarm
triggered
on
utilization
dropped,
and
it
was
simply
that
a
very
large
job
was
getting
ready
to
start
and
a
lot
of
nodes
had
to
be
cleared.
So
the
only
downtime
that
we
had
was
the
scheduled
maintenance.
A
The
utilization,
so
the
the
large
jobs
was
actually
up
a
little
bit
from
normal.
Our
target
is,
I
think,
25
of
the
workload
being
large
jobs,
so
work
that
can't
progress
without
a
really
large
scale
system
such
as
quarry
utilization
was
high,
but
you
know
in
in
recent
months
it's
actually
been
sitting
up
around.
The
kind
of
you
know,
94
95,
and
I
kind
of
wonder
if
part
of
the
relative
dip
is
because
you
know
large
jobs
can
have
gaps
scheduling
around,
but
this
is
where
this
is
partly.
A
A
New
tickets
yeah
a
chart
of
how
these
tickets
move
over
over
time
would
probably
be
interesting.
The
numbers
do
tend
to
be
reasonably
consistent.
You
know
so
yeah,
five
to
seven
hundred
a
month,
newty
gets
closed
to
get
our
current
backlog
as
of
a
couple
of
weeks
ago
was
a
little
over
500
tickets
flash
and
that's
all
we
have
for
today,
and
it's
right
at
the
top
of
the
hour.