►
From YouTube: SunPy Developer Discussion (11/4)
Description
A
C
A
A
C
A
G
F
A
E
A
D
D
F
C
D
C
D
A
B
D
F
A
F
C
A
A
E
G
G
A
E
A
E
A
E
A
A
C
A
B
B
B
C
E
A
A
A
C
D
A
D
D
A
A
D
E
A
D
H
H
D
C
C
A
A
D
A
F
A
E
A
A
E
E
D
E
A
What
the
what
the
test,
in
my
opinion,
I've,
been
told
that
this
Esen
actually
particularly
straight
forward
to
despite
the
fact
that
it
seems
logically
simple
what
it
seems
to
me
that
you
should
do,
is
it
should
do
the
HEK
query
like
the
test
does
write
the
test?
Does
the
HEK
query
for
and
gets
the
results
it
should,
then
the
test
should
then
pass
the
results
and
know
how
many
entries
in
the
database
they
should
be
given
this
set
of
results
from
the
HEK.
D
C
A
It
stays
true,
however,
the
that
is
okay
in
an
ideal
world.
That's
what
was
that
should
be
doing,
because
the
test
is
actually
testing
that,
when
you
add
entries
to
the
database
from
our
HEK
result,
it
returns
the
same
number
of
the
equivalent
number
of
records
in
the
database.
Get
added
from
that
result.
A
D
Routine
that
the
text
is
supposed
to
before
then
it
seems
to
me,
then
that
this
tell
the
tests
that
should
be.
There
should
be
that
the
testing
that
ad
from
HEK
query
result
should
use
a
synthetic
HEK
query
result
that
way:
you're
testing
the
add
function,
and
then
you
have
a
separate
tests.
The
tests
that
the
query
is
actually
returning,
something
edible,
then
the
greater
than
zero
makes
sense.
I
mean
like
you
can
say
you
know
we're.
Not
the
test
as
hatched
would
be.
D
A
B
D
C
A
E
A
Yeah
I'm
I
would
agree
that
synthetic
results
are
actually
something
that
we
should
adopt
widely
in
the
tests
for
PSO
and
HEK.
There
are
probably
quite
a
lot
of
things
that
if
we
had
some
way
of
generating
synthetic
results,
we
could
make
a
lot
more
of
our
test
suite
online,
which
would
be
very
useful
because
the
offline
tests
do
not
get
as
one
as
much
that's
the
online
test.
Well,.