►
From YouTube: SJAA Imaging SIG Meeting 2020 09 15 at 19 28 GMT 7
Description
We're very excited to have member Hy Murveit presenting this month on:
Recent Improvements to KStars
He'll be introducing KStars/Indi which is an open-source software package for astrophotography. Hy is one of the developers of KStars and will show us several improvements he's implemented recently including changes to improve guiding, as well as a new module that can be used to monitor or analyze current or past imaging sessions.
B
B
I
had
mentioned
to
some
of
these
other
folks
before
well,
actually
we're
starting
to
get
a
few
people
come
in
right
now
that
I
was
taking
some
classes,
some
astronomy
classes
these
days,
and
so
I'm
taking
this
astrophysics
class,
and
this
has
nothing
to
do
with
my
presentation.
Incidentally,
and
the
professor
asked
an
interesting
question,
so
I
thought
you
know
unmute
your
mics
and
answer
the
question.
B
B
D
B
B
E
D
B
B
Oh
wow,
it
might
contract,
god
knows,
but
it
might
expand,
but
it
has
the
internal
thermal
heat
to
keep
it
going
for
150
million
years.
In
fact,
the
in
you
know
in
the
I
think
it
was
the
19th
century.
Everybody
thought
that's
why
the
sun
was
hot
was
all
the
gravity.
You
know
compressing
the
matter
making
things
hot,
but
they
did
the
math
and
it
turned
out.
B
Let's
get
into
my
talk
so
and
by
the
way
right
now
you
see
the
cover
slide
right.
Yes,
okay,
so
I
I
retired
in
january-
and
I
recognized
probably
a
little
while
before
that
that
you
know
I
was
nearing
the
end
of
my
career
and
I
needed
something
to
do
so.
I
don't
drive
my
wife,
leslie,
crazy
and
all
that
kind
of
stuff,
and
I
eventually
ended
up
in
this
hobby,
but
I
knew
that
I
also
had
to
do
some
programming.
B
B
Astrophotography-
and
I
decided
you
know
I
wanted
to
do
a
little
more-
I
wanted
to
contribute
software-wise
to
it,
and
I
found
the
the
this
k-stars
project
where,
where
you
know
it's
available,
that's
sort
of
the
reason
I
wound
up
in
k-stars,
as
opposed
to
a
sequence
generator
pro
or
something
else
is
I
wanted
to
find
a
project
that
I
could
muck
with.
That's
just
my
you
know
that
that's
one
of
the
things
I
get
out
of
it
that
other
folks
might
not,
but
anyway,
that's
sort
of
where
I
come
from.
B
But
of
course
k-star
is
a
general
purpose
thing.
So
what
I
thought
I'd
do
is
I
mean
many
of
you
may
know
about
it
and
you
can
speed
me
up
or
slow
me
down,
but
I'll
give
a
quick
overview
of
k-stars
and
then
a
couple
projects
I
did
in
the
last
four
or
five
months
I
I've
made
just
to
say
probably
three
or
four
sort
of
major
changes
to
k-stars
in
the
last
in
the
last
year.
B
Let's
say
I
got
into
it
about
a
year
ago
and
you
know
probably
my
first
20
30
changes
were
a
little
bit.
You
know
little,
you
know,
add
a
menu
item
here
fix
a
bug
there,
but
I
eventually
got
to
the
point
where
I
could
start
making
changes
and
most
of
the
changes
I
made
related
to.
You
know
things
that
I
found
you
know
bothered
me
about
it
and
I
wanted
to
improve
so
an
example
that
I
won't
talk
about
today.
B
Other
than
now
is
the
stretching
you
know
like
when
you,
when
you
see
an
image,
take
a
picture.
You
see
an
image,
they
had,
they
had
a
viewer,
but
it
didn't
it
didn't
do
all
the
stretching
controls
and
whatnot
that
you
might
have,
and
you
know
I
thought
that
was
a
place
I
could
contribute
and
so
on.
So
anyway,
I
found
k-stars
program
which
k-stars
in
india
and
ecos
has
existed
for
a
long
time
right.
B
It's
I
don't
know
how
old
it
is
at
least
10,
maybe
15
years
old
as
a
project
and
what's
interesting
about
it.
For
me,
as
I
said,
was
the
open
source
aspect
of
it.
You
know
you
could
find
all
the
software
you
can
modify
the
software
if
you
could
convince
the
people
running
the
show
that
your
contributions
make
sense.
B
B
There
are
windows
users,
there
are
mac
users,
but
I
think
the
lion's
share
of
the
users
are
linux
and
it's
sort
of
a
forum
based
thing
as
many
things
are
these
days,
but
one
of
the
things
that
I
know
confused
me
was
all
the
names
related
to
it.
The
k-stars
is
the
sort
of
the
planetarium
in
the
sort
of
the
device
end
of
it.
B
Ecos
is
the
astrophotography
part
of
it,
but
you
know
I
I
don't
know
different
people
tend
to
refer
to
the
whole
thing
with
each
of
the
names
and
then
there's
different
packaging
of
it.
There's
this
stellar
mate
thing
you
can
buy,
which
comes
with
a
raspberry
pi
and
the
software,
but
you
know
you
can
just
buy
stellar
merit
os,
which
is
the
software
there's
something
you
can.
Google,
all
the
links
are
on
this
slide,
which
I
guess
you'll
be
able.
B
If
you
haven't
written
them
down,
and
you
want
to
see
them,
you
could
find
it
on
the
youtube
thing
later
or
send
us
a
note.
Astroberry
is
an
interesting
packaging
of
k-stars
and
several
other
programs.
Astro
pi
3
is
a
shell
script
that
basically
installs
everything
on
on
linux
and
so
on
and
so
forth.
So
there
are
a
lot
of
names
and
I
don't
know
I
find
that
confusing,
but
you
know
in
the
end
just
call
it
k-stars
or
whatever,
by
the
way
feel
free
to
interrupt
me.
B
I
welcome
interruptions
on
talks
like
this.
So
if
you
have
any
questions,
just
let
me
know
so.
This
is
I
mean
I
could
have
done
this
by
going
through
the
browser,
but
you
know
it's
sort
of
safe,
safer
to
take
screenshots
and
a
talk.
You
never
know
what's
going
to
happen,
so
this
is
a
screenshot
from
a
couple
days
ago
of
the
you
can
see:
indielib.org
forum.html,
it's
the
you
know,
k-stars
forum,
indie
forum
whatever,
and
it's
pretty
active.
I
try
to
help
out
there.
You
know
when
people
have
questions.
B
I
I
answer
a
lot
of
questions
and
there
are
a
lot
of
people
like
that.
You
know
now
that
I'm
more
experienced
with
it
I'm
sure
at
the
beginning
I
was
the
one
asking
most
mostly,
and
now
I'm
mostly
answering
okay,
it's
it's
a
good
forum.
You
know,
don't
let
it
scare
you
you
know
when
you
look
at
it.
You'll
see
bug
reports,
but
of
course
that's
you
know.
That's
why
often
people
post
to
forums
is
because
they're
having
some
kind
of
problem,
so
I
would
say,
for
the
most
part,
it's
reasonably
stable.
B
Here's
this
next
page,
I'm
showing
you
is,
if
you,
if
you
you
know,
search
for
the
source
code,
you
can
find
it
it's
actually
not
on
github,
it's
on
something
called
get
lab,
but
I
think
if
you
search
for
k-star
source
code
or
something
you'll
find
it,
and
you
know
you
go
in
there,
if
you
know
c
plus
plus
you
could
find
anything,
you
know
everything
and
anything
related
to
k
stars.
How
does
the
guider
work?
How
to
you
know
capture?
B
It
may
not
be
easy
to
you
know,
I
mean
it's
a
big,
complicated
program,
but
it's
there
and
for
people
you
know
software
engineers
or
people
comfortable,
writing
software.
Reading
software,
you
know
you
can
you
can
if
you
work
at
it,
you
can
certainly
understand
and
make
modifications
and
just
to
show
you
see.
This
page
is
the
overall
one-
and
I
I
can
you
see
my
mouse
over
here-
okay.
Well,
I'm
assuming.
B
Okay,
great
so
over
here,
if
you
clicked
on
that
merge
requests.
You
know
this
is
a
copy
of
that
page
from
a
couple
days
ago,
and
you
can
see
you
know.
These
are
the
changes
that
have
been
made
recently
or
are
some
of
them
well,
some
say
merged,
which
means
they're
now
included
in
the
source
closed,
I
guess
means
they
were
abandoned
and
you
could
see
like
the
top.
One
is
just
a
new
feature
that
hasn't
been
merged,
yet
that
somebody
that
eric
in
france
is
working
on
so
yeah.
B
It's
active
there's
a
lot
of
development
in
this,
even
though
it's
complete
in
the
sense
that
you
can
do
your
astrophotography
with
it,
but
like
anything
else,
there's
new
features
that
that
might
be
interesting
or
or
bug
fixes
or
or
better
tests
and
eric
there
on
the
top
often
adds
tests
which
something
an
end
user
might
not
see,
which
is
really
valuable
for
developers
anyway.
So
it's
interesting.
B
B
If
I
have
some
ideas
about
something,
I
want
to
change
I'll
pass
it
by
him
I'll
eventually,
you
know,
write
the
code
and
put
in
a
merge
request
and
he'll
he's
the
one
mainly
who
reviews
stuff
and
approves
stuff,
and
it
makes
many
changes
himself,
and
he
has
this
blog
josem's
ecosphere
where,
where
you
know
mostly
it's
about
k-star's
releases,
you
could
see
the
last
release
in
july
was
v343
and
there's
going
to
be
a
3-5
coming
up.
An
interesting
thing
about
k-stars.
B
B
I
mean
that's.
How
you
get
stable
releases
is.
Somebody
has
to
be
the
first
or
second
or
tenth
person.
You
know
using
the
software,
and
so
there
is
actually
a
reasonably
large
community
of
people
willing
to
test
out
the
latest
stuff-
and
you
know,
complain
on
the
forum
if
something's
not
working-
and
you
know
these
people
are-
you
know
very
nice
they're.
They
understand
when
there's
a
bug.
B
Obviously
the
developers
try
not
to
have
any
issues,
but
you
know
it's
just
human
nature
to
nothing's
going
to
be
perfect
initially,
and
it
gets
us
to
the
point
where
we
can,
you
know,
add
features
and
have
stable
releases.
So
that's
a
valuable
thing,
so
I'm
just
going
to
go
through
some
screenshots
of
k-stars.
It
has
a
basic.
Actually,
I
don't
know
if
you
notice
the
background
of
my
screen
right
here
is
the
planetarium,
and
then
this
is
sort
of
a
a
zoom.
B
B
So
here
you
could
see
my
setup
except
I
don't
have
a
dome,
but
I
opened
up
the
dome
menu,
so
you
could
sort
of
see
that
and
there
there's
a
good
variety
of
support.
Indy
indy
is
sort
of
an
underdog
in
the
sense
that
the
manufacturers,
you
know,
don't
that's
not
the
first
driver.
They
write
right,
they're,
going
to
write
the
windows,
I'm
spacing.
What's
the
name?
Well
anyway,
it
doesn't
matter
the
the
the
stand:
the
windows
standard
for
interfacing
hardware,
to
these
kinds
of
things.
B
But
anyway
there's
a
reasonable
amount
of
of
hardware
supported,
and
if
there
isn't
often
people
write
it.
So
you
configure
your
hardware,
you
can
see
in
the
upper
left,
there's
sort
of
three
tabs
that
are
that
exist
without
starting
up
the
astrophotography,
without
starting
up
connecting
indy
to
ecos
and
I'll
talk
about
one
of
them.
B
But
anyway,
so
the
drivers
are
configured
and
then
I
in
this
screen
now
I've
started
it
up.
I
don't
know
if
over
here
and
the
screen
was
a
start
button,
that's
now
a
stop
button
and
it
said
okay
connect
to
all
my
devices.
You
know
I
showed
you
the
devices
here
so
then
I
hit
the
start
button
and
I
said,
connect
and
poof
the
devices
connect
and
now
you
can
see.
B
I
have
a
focuser,
a
filter,
wheel,
a
mount,
a
a
guide
camera
and
a
camera
all
connected
up,
and
this
window
here
is
sort
of
the
drivers
end
of
things.
If
you
want
to
change
something
in
a
driver,
and
then
you
have
you
know
the
planetarium
here
and
then
the
ecos
astrophotography
stuff
here
so
the
way
it's
organized
is
you
have
these
tabs
that
control
different
aspects?
The
mount
is
something
you
often
you
don't
often
control
other
than
hitting
this
park
and
unpark
button
on
the
right.
B
You
have
a
few
things
you
could
do
with
it,
like
you
know,
make
sure
your
meridian
flip
control
is
set.
Assuming
you
want
to
do
that
or
automatically
park
it
in
the
morning
or
enable
various
limits
or
whatever
it's
not
a
tab.
That's
used
a
lot
of
course.
It's
good
to
set
it
up
with
the
right,
aperture
and
focal
length,
and
that
I
think
I
did
this
from
my
simulator.
B
So
it
doesn't
have
my
particular
focal
length
right,
but
whatever
autofocus
is
an
interesting
tab,
something
I
contributed
to
does
the
obvious
you
know
here,
you
could
see
a
v
curve
and
it's
come
down
here
and
back
up
and
then
found
an
optimal,
auto
focus
point
anyway.
It
does
the
standard,
auto
focus
in
this
case.
It's
a
full
frame
autofocus,
where
it
finds
a
lot
of
stars,
finds
their
diameters
half
flux,
radius.
I
guess
and
minimizes
that
you
can
choose.
B
You
know
to
auto
focus
on
a
single
star
as
well.
It
has
plate
solving
with
aztec
or
astrometry.net
online
or
local,
and
that
works
pretty.
Well,
I
I
don't
know
I
tend
to
I'd
use
the
local
stuff.
Of
course
I
tend
to
go
back
and
forth
between
those
two
guiding
is
something
another
thing.
Actually
I'm
going
to
be
talking
about
guiding,
you
can
use
phd2
and
when
I
started
with
this
program,
probably
until
two
three
months
ago,
that's
all
I
ever
did
was
use
phd2
and
that
interface
works.
B
B
So
now
I
tend
to
use
my
stuff,
but
either
way
and
the
capture
is
pretty
standard.
You
know
you
sort
of
set
up
a
sequence
of
of
captures
in
this
case
you
know
I'm
alternating
red,
green
blue
about
every.
Oh,
I
don't
know
what
this
is
a
silly
one,
because
I
did
this.
This
is
just
my
simulator,
but
I'll
often
alternate
red,
green
and
blue.
B
I
don't
think
any
of
this
stuff
is
different
than
or
I
mean
I'm
not
that
familiar
with
sequence,
generator
probe,
but
I
think
it's
similar
capabilities
to
what
you
might
see
there,
although
I'm
not
sure
about
that,
and
then
there's
a
fits
viewer.
You
know,
so
you
take
a
picture,
you
can
look
at
it
and
you
can
open
up
other
things
and
they're
zooming,
and
you
can
see
these
various
controls
at
the
bottom
and
that's
basically
what
I
added
sim
very
similar
to
the
pix
insight.
B
B
B
Well,
I
didn't
know
if
it
would
be
dark
enough
when
I
was
done,
but
you
see
here
we
are
on
the
am
I
yeah,
I'm
on
the
plate
solve
thing
tab
right
and
if
you
look
right,
can
you
see
the
mouse?
It
says
polar
alignment
so
right
there
is
an
automated
polar
alignment
automated.
What
does
that
mean?
What
that
means
is
that
you
know
it
assumes
your
park
or
not
parked
but
pointing
at
the
north
star.
It
doesn't
do
drift
alignment,
it
does.
B
B
You
know
where
you're
pointing
and
where
you
need
to
be
pointing
and
then
of
course
it's
up
to
you
to
turn
the
altitude
and
the
azimuth
knobs,
but
you'll
see
you
know,
you'll
get
visual
feedback
that
you're
getting
closer
to
your
target
and
in
fact
I
use
that
all
the
time
whenever
I
polar
align,
I
used
to
use
my
pole
master
and
anybody
want
to
buy
a
pole.
Master
just
call
me
because
I
basically
I
just
use
the
k
stars,
one
now
or
ecos
one
now
all
right.
B
So
the
other
thing
I
wanted
to
mention
was
it
all
runs
on
the
raspberry
pi.
So
there
there's
me
at
gssp,
obviously
not
2020
but
2019.,
and
you
could
see
the
red
lights
coming
from
my
raspberry
pi
and
it
all
ran
there.
Now,
of
course,
I
got
a
laptop
there,
but
all
it
I
was
just
vnc
into
the
raspberry
pi
or
actually
I
had
a
monitor
too
connected.
B
B
I
mean
it
worked,
but
it
was
slow,
the
pi
4,
it's
it's
fine,
all
right,
so
that's
k,
stars
and
and
the
various
other
things
related
to
k
stars,
and
now
I
was
going
to
mention
a
few
things
I
worked
on
in
the
in
the
last
little
while
is
it
before
I
do.
Is
I'll
give
you
a
few
seconds.
Anybody
have
a
a
question
about
k-stars
or
whatever
that
you
want
to
ask
before
I
change
topics
and
talk
about
things.
I
did.
G
B
D
B
B
Yes,
of
course,
right
keyboard
monitor
mouse.
You
know
the
package
right
a
little
a
little
hub,
usb
hub
to
put
anyway,
okay
and
any
other
questions
all
right.
Let's
talk
about,
feel
free
to
interrupt
and
ask,
but
I'm
going
to
switch
over
now
to
project.
So
the
first
project
is
a
a
thing
that
I
don't
tell
me
if
it
exists
elsewhere,
but
I'm
not
familiar
with
this
concept,
but
it
was
something
to
me
that
was
just
screaming
to
be
built
for
for
k-stars.
B
Maybe
sgp
could
use
something
like
this.
Maybe
they
already
have
it
and
I
call
it.
I
called
it
the
analyze
module-
and
I
say
it's
currently
in
pre-release
nightly's,
meaning
it
didn't
make.
You
know
I
wrote
this
or
completed
it
after
that
334
release,
and
so
it's
in
the
code
base,
people
who
you
know
either
download
the
code
or
there's
a
nightly,
build
of
the
code
that
you
can
get
and
just
download.
H
B
Somebody
should
mute
or
talk
one
or
the
other
okay.
So
when
I
I've
introduced
several
new
features
and
whenever
I
do
it,
what
I
do
is
I
post
on
the
indie
lib
forum
and
say
hey.
I
got
this
new
thing
and
you
know
if
you're
using
nightlys,
please
test
it
out,
and
so
you
could
see
here's
a
post
that
I
that
you
could
find.
B
If
you
went
to
that
forum,
you
know
new
keystar,
zecos
module
called
analyze,
and
I
you
know
it's
longer
than
what
you
see
here
and
I
sort
of
described
what
it
was
and
you
know
tried
to
give
a
few
and
you
know,
instructions
on
how
you
might
use
it
and
you
know
obviously
I'm
looking
for
bugs
and
feedback
on
how
I
can
improve
it
and
it's
interesting
tonight.
You
know,
I
being
you
know
a
certain
age.
A
B
B
B
So
this
is
the
analyze
tab,
so
you
can
see
on
the
top
of
the
screen.
There's
the
various
tabs
right
and
the
three
on
the
left,
which
is
mine,
and
you
know
the
third
one
is
mine.
These
first
two
are,
you
know
how
you
connect
to
indy
and
the
the
sk
the
scheduler,
and
then
the
the
five
on
the
right
are
the
ones
I
went
through
earlier.
You
know
capture,
focus,
mount
align
and
guide.
B
B
B
So
that's
a
very
valuable
thing,
so
kde
is
important,
but
anyway
below
kdes
k,
stars
so
kde
has.
I
know
there
are
volunteers
there
that
do
you
know
design
that
are
talented
artists
and
hopefully
I'll
get
a
little
icon
done
so
anyway.
This
is
the
analyze
module
and
this
is
the
the
one
screen
really
there's
there's
only
one
screen
and
what
you
see
here
is
first,
the
the
top
section.
B
You
know
that
says
mount
flip
guide,
align,
focus
and
capture,
that's
a
timeline,
so
it
shows
you
what's
happened
so
far
tonight
or
you
can
go
back
and
look
at
yesterday's
or
last
week's
or
last
month's
sessions
right,
so
it
stores
logs
specialized
logs
that
you
could
look
at.
But
let's
pretend
that
we're
in
the
middle
of
capturing
this
is
actually
read
from
a
file.
You
could
see
that
on
the
top
line.
B
It
says
you
know
it
gives
you
the
time
when
this
log
was
written,
but
but
it
could
also
have
been
the
current
session
and
you
could
see
you
know
we're.
You
know
almost
two
hours
into
it
and
so
on
and
so
forth,
and
it
shows
you
what
happened
so
we
did
eight
green
captures
followed
by
well.
First,
we
did
a,
I
don't
know.
It
looks
like
an
h,
a
like.
Oh,
I
can't
click.
Let
me
go
back
some
kind
of
focus
on
with
some
kind
of
filter.
B
Then
we
did
a
green
focus.
Then
we
did
eight
green
captures
a
blue
focus.
I
hope
this
is
clear
what
I'm
pointing
at
and
then
a
blue
capture,
another
blue
focus.
God
knows
why.
I
don't
remember
why
you
know
I
just
went
back
and
took
one
of
my
logs.
Maybe
I
was
playing,
I
don't
remember
and
so
on,
so
you
could
sort
of
see
what
happened
there
with
respect
to
captures
and
focus
a
line.
B
Oh,
here's,
the
meridian
flip
and
there's
a
mount
basically
tracking
sessions.
So
this
whole
thing
sort
of
gives
you
a
view
of
what
happened
tonight
last.
You
know
this
night
this
this
guiding
session.
You
know
my
idea
was
to
make
it
so
that
you
could
you
know,
did
things
work
out,
you
know
and
better
than
you
know.
I
don't
know
the
way.
When
I
would
image.
B
I
would
never
be
100
sure
how
things
went
until
I
looked
at
all
my
images
and
yada
yada,
and
this
at
least
gives
you
some
kind
of
view
on
that,
and
then
the
the
next
session
called
statistics
has
a
whole
bunch
of
stuff.
You
can
plot
and
I
probably
should
add
another
six
or
eight,
but
this
is
you
know
what
I
did
on
v
1.0
and
what
only
a
few
of
them
are
checked
right
now.
B
B
This
change
in
signal-to-noise
ratio
at
the
beginning
most
likely
has
to
do
with
a
a
change
in
guide
star,
I'm
guessing
that
there
wasn't
a
problem,
but
anyway,
you
know
this
is
the
kind
of
thing
you're
going
to
look
at
the
plots
and
learn
to
how
to
interpret
them.
The
blue
line
there
is
the
the
hfr
of
the
image.
What
that
really
means
is
it
takes
a
hundred
stars
in
the
image
and
it
computes.
B
You
know
their
half
flux
with
our
radius
and
averages
those
hundred
or
something
like
that-
comes
up
with
a
value
for
the
image,
and
you
know
the
tighter
the
star.
You
know
the
smaller,
the
half
flux
radius
for
the
stars,
I
mean
it
may
be
relative
depending
on
your
equipment,
but
again
you
could
see
imaging
getting
a
lot
worse
at
the
end,
you
know
when
this
the
skies
are
getting
iffier.
B
The
red
line
is
a
it's
the
rms
guiding
value.
There's
this
funny
thing
I'm
going
to
look
into
and
you
can
actually
see
it
here
see.
Let
me
point
out
that
I've
clicked
on
one
of
the
guide
sessions
here
right
and
one
of
the
captures
where
the
arrow
on
top
is
pointing
and
when
I
click
on
that,
what
that
does
is
it
displays
the
the
guiding?
B
What's
called
a
drift
plot
in
k-stars,
which
is
you
know
all
the
guide,
error,
values
and
those
two
circles
are
one
arc
and
two
arc
seconds
and
it's
showing
you
the
values
and
you
can
see
at
the
beginning.
The
first
three
samples
after
the
focus
it
had
drifted
out,
it
had
drifted
away
and
then
it
started
guiding
and
that
that
spike
in
in
in
in
snr
has
to
do
with
those
three
samples
it.
It
may
even
not
start
capturing
until
that
is
below
two.
B
I
I
think
there's
an
option
for
that
and
that
I
may
or
may
not
have
write
yet
in
the
analyze
module.
But
anyway
you
got
the
idea.
Let's
say
this
was
a
problem.
This
would
have
alerted
me
to
it
and
I
could
look
at
it.
So
there
you
go
when
I
click
on
the
capture
session.
It
also
gives
me
some
statistics
about
you
know
when
it
started
when
it
ended
the
filter
that
was
used.
Yada
yada-
and
you
know
this
is
dependent
on
the
thing
you
click
on.
B
I
don't
know
if
I
have
it
here,
let's
see
yeah
I
see
you
can
click
on
a
focus
session
and
then
it'll
show
you.
I
I've
set
it
up
to
where
it
could
show
you
the
v
curve
from
that
focus,
and
you
could
see
you
know
it
got
down
to
less
than
one
arc.
Second
hfr
on
the
focus
which
is
good
and
it
gives
you
some
statistics.
It
took
90
seconds.
A
lot
of
people
complain
about
my
focusing
software
that
it
takes
a
long
time.
B
I
always
say
you
know
why
sweat
30
seconds
when
you're
gonna
image
with
it
for
the
next
hour.
I
don't
understand,
but
anyway
there
you
go
different
point
of
view
in
an
event,
so
you
can
click
on
different
things
and
get
information.
The
most
interesting
things
to
click
on
are
like.
Oh,
if
you
double
click
on
the
capture,
I
don't
believe
I
have
this
in
this
presentation,
but
if
you
double
clicked
on
the
capture-
and
it
has
the
image
still
on
disk,
it
will
show
you
the
it'll
pop
open,
a
fits
viewer.
B
You
know,
which
is
the
k
stars
display
program
for
fitz
files,
and
you
can
look
at
your
image.
The
focus
information.
I
told
you
about
guiding
more
or
less
just
shows
you
a
drift
plot
and
some
guiding
statistics
and
the
other
two
aren't
that
interesting.
Yet-
and
I
don't
know
I'm
wondering
about
if
there
are
other
things
that
that
might
be
interesting-
I
don't
have
a
a
dome
I
haven't
had
a
you
know.
B
B
I
I
could
have
added
the
actual
ra
and
dec
errors
in
this
case.
It's
the
correction
pulses,
which
is
a
similar
kind
of
plot,
and
you
could
sort
of
do
that
and
zoom
into
it
and
in
this
case
I've
also
zoomed
into
the
hfr
plot.
So
you
can
sort
of
you
know.
I
don't
know
if
there
is
a
difference
between
1.4
and
1.7,
there
might
be,
and
so
you
could
sort
of
see
it
was
a
little
rough
at
the
beginning.
Maybe
that
was
early
in
the
evening.
B
B
I
told
you
about
the
focus
session
and
okay,
so
here's
guiding
where
I've
clicked
on
the
ra
error,
which
is
the
brighter
line,
so
the
bright
green,
I
believe,
is
ra
yeah.
You
can
see
that
from
the
legend
here,
so
I
believe
I
anyway,
and
the
blue.
The
bright
blue
is
the
I
believe
by
the
way,
this
software,
you
probably
no
it's
okay.
I
had
a
bug
in
there
where
it
was
plotted
wrong.
B
The
the
guide
pulses,
you
know,
obviously,
should
be
opposite
the
errors
in
any
event,
so
there's
that
and
the
other
thing
to
notice
by
the
way-
I
don't
know,
if
you
I
didn't,
call
it
out,
but
I
zoomed
in
to
the
graph
right,
so
you
can
zoom
in
from
a
time
perspective
as
well,
so
now
it's
only
showing
what
8
900
seconds
on
top
instead
of
a
couple
hours
on
top,
so
you
can
zoom
around
in
both.
You
know
the
timeline.
Well,
these
two
plots
are
coordinated.
These
two
graphs
are
coordinated.
B
They
always
show
the
same
time
interval
and
you
can
zoom
in
and
another
thing
on
top.
Is
this
latest
button
where,
if
it
doesn't
apply
for
reading
from
file?
But
if
you
were
imaging
and
looking
at
this
screen,
it
would
always
you
know,
stay
up
to
date.
So
as
time
advances,
the
screen
will
scroll
and
you
can
choose
the
width
that
you
want
here.
Here's
an
example
where
it
zoomed
in
on
the
meridian
flip
sequence,
and
so
I
believe
this
yellow
line
is
the
mount
was
ready.
B
B
So
I
waited
till
the
capture
ended
and
then
you
could
see
the
amount
started.
Slewing
I
mean
you
can't
tell
that.
But
if
you,
I
don't
think
I
have
it
here,
but
if
I
in
the
real
program,
if
I
clicked
on
that
you'd
see
it
was
a
slew
and
then
you
could
see
a
bunch
of
slews
and
this
will
you
know
the
align
module,
activating
and
plate
solving,
and
you
know,
did
a
little
iteration
on
that
until
it
found
just
the
right
spot
and
then
started
tracking
again.
B
So
you
could
examine
things
like
that
at
this
point
you
know,
I'm
not
100
sure
it's
not
just
eye
candy
for
something
like
the
meridian
flip,
but
you
know
it
it.
We
could
probably
add
enough
statistics
if
stuff
is
missing
where
it
really
could
help.
You
understand
your
system
better
and
you
know
be
more
effective
at
using
it.
B
So
I
mentioned
there
that
you
could
read
from
file,
so
you
know
you
could
look
at
your
old
logs
and
and
see
how
yesterday's
session
went
and
maybe
compare
yesterday's
and
today's
and
and
stuff
like
that
again
this
over
here
is
the
the
this
is
the
0102
means
it
was
1am
102
am
and
7
074
and
that's
how
many
seconds
into
the
start
of
k.
Stars
base,
or
at
least
the
start
of
analyze
that
it
was
okay.
B
G
B
B
B
No,
it's
it's
not
there.
Yet
it's
certainly
on
the
list.
I'll
I'll
tell
you
just
offhand
the
reason
it
isn't
there
is
somebody
one
of
the
other
developers
rob
lancaster
is
he's
he's
in
delaware,
he's
doing
the
other
people
who
work
on
k-stars
and
he's
doing
an
overhaul
of
the
the
star
detection
module
and
the
plate
solving.
B
I'm
not
module,
but
the
libraries
that
are
called
and
the
plate
solving
ones,
and
I
didn't
want
to
sort
of
start
getting
into
you
know
like
making
changes
to
you
know
because
eccentricity
isn't
something
that's
available
right
now
and
it's
a
small
change.
I
mean
you
know
in
fact
it's
a
it's
a
three-line
change
and
I
know
how
to
do
it,
but
I
just
sort
of
avoided
it
on
v
1.0
for
that,
but
I
agree
with
you.
I
tell
you
what,
though
I
think
one
of
the
problems
is.
B
I
already
have
18
or
god
knows
not
18,
but
a
lot,
maybe
16
check
boxes
there.
Some
of
them
are
ridiculous
to
plot,
but
are
interesting
to
look
at
in
terms
of
their
numbers,
but
you
know
so
I'm
going
to
have
to
deal
with.
You
know
eventually,
there's
going
to
be
30
or
40
values
to
choose
for
plotting
and
yada
yada,
and
that
that
is
a
complexity
is
how
to
do
the
user
interface.
B
For
that,
oh
and
there's
one
more
interesting
user
interface,
constraint,
josem
insisted
and
I
think
he's
absolutely
right
that
it
has
to
work
on
a
relatively
small
monitor.
You
know
low
resolution,
so
I
think
the
constraint
was
something
like
800
across
and
750
up
down,
and
so
you
know
this
is
the
kind
of
a
tab.
That's
you
know
screaming
for
2000
by
1500
or
something
but
yeah.
B
I
don't
think
there
are
a
lot
of
k-stars
users
at
the
sjaa
right,
but
you
know
so
maybe
it
doesn't
directly
apply
to
you.
I
mean.
Obviously,
if
you
are,
you
know
I'd
love
to.
If
you
have
any
questions,
I
I'd
love
to
help
out,
but
but
anyway,
it's
an
interesting
way
to
go
this
analyze
thing.
I
think
I
use
it
all
the
time
all
right.
B
So
the
second
topic
is
a
guiding
and,
as
I
said,
I
used
I
used
phd2
and
you
know
like
a
lot
of
phd2
user
and
by
the
way,
phd2
is
an
excellent
product.
So
I
or
whatever
you
want
to
call
a
product,
it's
free,
but
you
know
software
piece
of
software.
It's
excellent
and
I
used
it
for
a
long
time
and
enjoyed
it
and
it
was
great,
but
you
know,
like
everybody
else,
you
know
I
would
fret
about
my
guiding
right.
B
B
So
we'll
you
can
see
I'll
put
this
one
up.
Sorry
about
that
so
well,
let
me
just
go
back
to
the
main
thing,
so
I
had
this
idea
that
guiding
that
I
could
do
better
that
that
seeing
was
messing
with
my
guiding
right
and
everybody.
I
mean,
of
course,
that's
true
and
seeing
messes
with
everything,
certainly
messes
with
guiding-
and
I
had
this
idea
that
you
know
if
you
guide
on
more
than
one
star
and
I'm
not
the
first
person
to
think
about
this-
that
maybe
that
could
improve
the
guiding.
B
B
You
know
the
version
that
I'd
always
been
choosing
and
sap
was
already
detecting
all
the
stars
in
the
image.
So
I
thought
what
the
hell?
Let's
guide
on
more
than
one
star,
and
let's
say
you
know
you
pick
10
guide
stars,
you
could
find
their
average
error
and
you
know
push
the
amount
in
the
direction
of
the
average
of
the
10
error.
B
Instead
of
one-
and
this
isn't
a
you
know,
I'm
not
the
first
person
to
have
the
idea
of
using
more
of
the
image
to
guide
with
and
there's
other
approaches
to
this
there's.
You
know
like
overall
image,
analysis
versions
of
that
as
well,
but
anyway
it
was
straightforward
to
add
multiple
stars,
and
I
came
up
with
this
set
multi-star
guiding
idea
and
I
implemented
it
and
tried
to
get
it
to
work
and
long
story.
Sh
this
this
slide
isn't
the
slide.
B
I
wanted
to
show
you
but
you'll,
see
why
I
have
it
there
for
a
second
in
a
second.
In
the
end
I
implemented
it
and
I
started
guiding
and
I
I
couldn't
convince
myself
that
I
had
improved
the
guiding
substantially
I
mean
maybe
I
had,
but
I
I
couldn't
prove
it
guiding-
is
sort
of
hard
to
prove
that
you've
improved
something
you
know
because
conditions
change.
You
know
you
can't
guide
with
two
algorithms
on
the
same
night.
Sort
of
you
know
you're
guiding
with
one.
B
B
So
I
wasn't
100
convinced
that
I
had
improved
things,
but,
interestingly,
I
was
having
trouble
for
whatever
reason
I
was
having
trouble.
I
would
lose
my
guide
star
a
lot
and
it
occurred
to
me
that
with
this
multi-star
approach,
do
I
have
a
picture
of
it
here.
Let
me
find
a
picture
of
it
here.
It
is.
Let
me
show
you
this
a
picture,
so
this
is
what
I
wound
up
doing
you
could
see
here.
B
This
is
by
the
way,
simulated
image.
Unfortunately,
you
know
bruce-
and
I
talked
about
doing
this
talk
and
I
last
week-
and
you
know
since
last
week,
there's
been
no
imaging
here
in
the
bay
area
as
you're
all
very
well
aware-
and
so
I
just
made
this
slide
from
the
simulator
but
same
idea,
so
yeah
k-stars
has
a
simulator
which
is
really
useful
for
writing
software
debugging
software
testing
software.
B
B
It's
actually
picked
one
as
sort
of
the
the
real
guide
star,
the
one
in
the
square
and
the
other
nine
are
circled,
but
my
idea
was
that
we
would
track
them
all
and,
like
I
say,
guide
using
the
offsets
of
all
of
them
and,
as
I
was
saying
I
I
did
that.
I
didn't
convince
myself
that
I
I
had
improved
it,
although
it's
possible
I
had,
but
what
I
realized
was
well.
B
You
know
they're
at
a
certain
offset
to
the
guide
star
right.
There's
there's
a
certain
pattern
here
right,
you
have
a
star
our
friend
the
guide
star
and
then
to
you
know
to
the
right
of
that
no
slightly
down,
but
pretty
close
is
another
star
and
then
down
30
degrees
and
a
little
further
ways,
another
star
and
so
on.
B
Right
and
there's
this
pattern
in
the
sky,
and
probably
at
least
for
this
image
you
couldn't
find
you
know
like
if
you
shifted
that
square
and
put
it
on
another
star,
you
wouldn't
find
a
position
where
you'd
find
all
those
other
stars
just
in
the
right
place
or
within
some
small
error.
You
know
so
this
pattern.
B
You
see
here
sort
of
defines
the
position
of
the
guide
star
it
that
occurred
to
me
and
because
of
that
it
occurred
to
me
that
hey
this
would
be
a
a
better
guide
star
finder,
you
know
like
the
way
the
guide
star
finder
worked
before
was
that
you
know
it
had
a
sort
of
rough
area
of
where
it
was
it
assumed
it
didn't,
move
much,
and
so
it
just
looked
in
that
reticle
and
and
look
for
a
star.
But
what?
If
there's
two
stars
in
that
reticle?
B
B
Now,
of
course,
it
may
not
be
the
smartest
thing
in
the
world
to
pick
guide
stars.
You
know
right
next
to
other
stars,
but
this
is
a
general
problem
as
well.
So
it
occurred
to
me
that
the
the
same
set
multi-star
approach
that
I
used
would
be
good
for
finding
guide
stars,
and
perhaps
you
know,
and
so
selecting
so
anyway.
With
that
in
mind,
that's
it
definitely
improved
things.
B
B
So
if
we
look
at
the
left
and
ignore
the
fact
that
I've
sort
of
grayed
things
out,
I
intended
to
have
a
slide
where
this
was
all
dark.
You
could
see
that
the
steps
are,
you
know,
select
a
guide
star
calibration
where
you
move
the
guide
star
around,
and
you
see
you
know
a
few
things
you
find
out
the
ra
and
dec
directions.
B
You
know
if
you
haven't
thought
about
it,
your
image,
the
the
ra
or
the
deck
a
direction
it
can
be
at
an
arbitrary
angle.
In
your
guide
image.
It
depends
on
how
you
rotate
your
camera.
You
rotate
your
telescope,
yada
yada,
so
it
can
be
at
an
arbitrary
angle.
Now
it
keeps
that
angle
throughout
your
imaging
until
you
rotate
your
camera,
but
it
is
at
an
arbitrary
angle.
B
So
you
need
to
know
that,
and
you
know,
because
let's
say
you
want
to
move
you're
you're
off.
Let's
say
the
guide
star
needs
to
come
down
by
two
pixels
in
the
main
image.
Well,
how
do
you
move
it
down
by
two
pixels?
That
may
be
some
combination
of
pushing
the
ra
in
a
certain
direction
and
pushing
the
deck
in
a
certain
direction,
so
you
have
to
know
the
directions
that
they're
pointing
so
that's
what
one
of
the
things
calibration
does.
B
Usually
I
mean
almost
always
ra
and
dex
should
be
orthogonal
at
right
angles
to
each
other,
but
still
you
need
to
know
that
and
they
can
flip
and
also
you
know
a
certain
push
on
the
ra
motor.
Can
you
know
you
have
to
understand
how
much
that
affects
how
you
know
like
if
you
push
the
ra
motor
for
half
a
second,
how
many
pixels
in
your
guide
image?
B
Will
that
move
typically
so
that
that's
another
thing
that
calibration
typically
does
it
determines
those
two
things:
the
angles
and
the
and
the
sort
of
the
gain
of
the
you
know
in
pixels
of
the
ra
motor
and
deck
motor,
then
it
guides
and
in
guiding
you
you
capture,
an
image.
You
locate
the
guide
star,
you
compute
offsets.
You
know
how
far
things
moved
and
then
you
push
the
thing
again
and
then
you
iterate
and
then
there's
dithering,
which
is
a
whole
separate
topic.
That's
not
that
relevant.
B
Let's
get
back
so
so
I
had
this
idea
for
set
multistar,
so
select
a
guide
star.
I
I
I
added
this
a
set
multi,
I
mean
anyway,
here's
my
new
algorithm.
So
the
first
thing
it
does
is
select
the
guide
star
it.
I
I
actually
did
update
the
algorithm
for
finding
a
guide
star.
There
was
a
heuristic
there
and
I
changed
it
to
basically
the
signal
to
noise
of
the
guide
star.
B
You
know
finding
the
a
star
with
a
good
signal
to
noise.
You
know
the
maximum,
but
not
too
high,
because
it
tends
that
the
the
the
things
in
your
image
that
are
you
know
have
monstrous
signal
to
noises
tend
to
be.
You
know
you
know
galaxies.
You
know
the
middle
of
the
core
of
andromeda
and
stuff
like
that,
which
you
probably
don't
want
to
guide
on.
So
you
know
within
reason.
B
B
You
know
it
finds
a
hundred
of
them.
It
picks
10..
In
this
case
it
rejected
the
real
high
one
saying:
well,
maybe
that's
a
a
galaxy
or
or
something
bright.
That's
a
little
too
broad.
You
could
see
it
has
a
high,
it's
not
a
ridiculously
high
hfr
at
4.6,
but
it's
higher
than
the
rest.
So
I
wound
up
picking
one
as
the
guide
star
and-
and
this
is
the
collection
of
10
stars-
it's
going
to
be
using
for
its
multi-star
algorithm
in
calibration.
B
B
B
This
is,
I
guess,
the
positive
r
a
direction
and
then
it'll
go
back,
and
then
you
do
the
same
for
deck.
The
lines
are
pretty
close
to
90
degrees,
they're,
not
exactly.
You
could
force
the
thing
to
be
90
degrees
or
you
could
just
take
the
lines
you
got
since
you
don't
know
exactly
what
the
truth
is
and,
of
course
the
number
of
pulses
tell
you.
You
know
if
it
took
this
many
pulses
to
go
this
distance.
You
sort
of
have
an
idea
of
what
the
gain
is.
B
You
know
how
many
milliseconds
of
pulse
leads
to
how
much
movement
in
the
on
the
image.
So
I
I
made
some
changes
to
this
algorithm,
mostly
well
in.
In
fact,
we
weren't
using
the
gain
at
all.
There
was
sort
of
a
hard-coded
gain,
and-
and
so
I
changed
that
I
added
the
ability
to
to
remember
calibrations
for
future
sessions.
B
You
know
the
control
algorithm,
that's
used
there.
Oh,
you
know
what
what
do
I
mean?
I
actually
did
change
that
glad.
I
had
this
slide.
You
could
see
here.
I
was
thinking
of
changing
it.
You
know
because,
like
again,
I
was
fretting
over
my
guiding
and-
and
I
was
anyway-
it
was
bothered
by
it
and
then
I
know
phd2
had
this
really
good
algorithm
called
oh,
what's
it
called?
B
B
It
was
a
phd
to
a
phd
thesis
out
of
zurich,
and
so
I
I
it
turns
out
it's
open
source
and
it's
not
just
phd2.
So
I
found
this
guy
edgar,
klensky
and
edgar
allowed
me
to
use
it
for
k-star.
So
it's
the
I
wish
I
could
remember
what
it's
called
than
phd2,
but
it's
the
same
code,
same
algorithm,
integrated
into
into
k
stars.
It's
a
really
interesting
algorithm
in
that
it.
It
basically
estimates
the
the
periodic
error
in
the
mount.
B
B
You
know
the
algorithm
code,
but
I
added
I
integrated
it
into
the
ecos
program
which
you
know,
which
was
which
had
its
complexities
and
then
I
I
did
the
what
I
just
said
earlier,
which
is
to
post
about
it,
and
that
is
in
the
343
release
and
it's
got
a
a
lot
of
use
and
in
general
I
think,
there's
been
good
feedback
that
the
the
internal
guiding
has
improved
in
k-stars.
It's
probably,
I
think.
Well
I
don't
know
I
I
can't
evaluate
it.
B
B
B
Right,
predictive
pack,
it
is
exactly
predictive
pack,
it's
the
same
source
code.
I
mean
there
may
be
things
in
phd2
that
they
do
on
top
of
predictive
pack,
but
the
predictive
pec
code
is
the
same
code
and
which
is
an
excellent
algorithm.
It's
an
interesting
algorithm
because
it
improves
right,
like
the
first
15
minutes,
aren't
as
good
as
the
next
two
hours
and
then,
if
you
move
the
mount
you
start
over.
So
it's
interesting
in
that
it
improves,
but
it
definitely
improves.
B
B
But
you
know
some
mounts
have
the
encoder
available
to
the
software,
and
so
in
theory
it
could
know
where
it
was
and
pick
up
where
it
started
from
anyway.
I
started
talking
to
klensky
about
that
and
he
was
discouraging
it
sort
of
saying
it's
complicated.
I
mean
we,
you
could
do
it,
but
it's
complicated.
He
wasn't
discouraging
it,
but
he
was
just
telling
me
that
it
was
com
more
complicated
than
just
throwing
in
the
encoder
number
and
poof.
B
So
that's
you
know
that
was
you
know
three
months
working
on
the
guider,
I
would
say,
and
then
I
did
a
whole
bunch
of
other
small
changes
you
could
see
there.
You
know
it
keeps
me
busy.
I'm
retired
keeps
me
out
of
trouble
the
challenges
and
all
almost
all
this
stuff,
I
would
say,
are
data.
You
know
like,
as
I
say
here,
it's
easy
to
think
of
something
you
know
exciting
and
new
to
do.
B
But
how
do
you
know
that
you
really
improved
anything
and
honestly,
I
don't
have
a
good
answer
for
that.
You
know,
I
really
don't
know
how
many
users
are
using
either
of
these
two
things.
I
really
wish
I
did
know
I
do
you
know
when
I
write
some
new
software.
I
find
a
buddy
on
on
the
forum.
You
know
I
find
somebody's
interested
in
a
topic.
I
send
him
a
note.
I
say:
hey,
you
know,
you're
having
problems
with
you
know
guiding.
B
You
know,
I'm
writing
this
new
geider
algorithm.
You
want
to
test
it
out
and
I
work
with
this
person
or
two
or
three
and
I
try
to
you
know,
make
sure
it
works
really
well
for
them
and
for
me,
but
you
know
I
don't
have
a
view
of
a
hundred
people
doing
that
and
that's
what
you
really
need
you
know
in
my
professional
career.
You
know
we
were
able
to
get
data
and
and
feedback
on
on
how
our
products
were
working.
B
B
You
know
ship,
your,
you
know
whatever
usage
statistics
out,
maybe
we
could
do
that.
You
know
with
a
you
know
they
default
off,
but
you
could
click
to
turn
it
on.
But
I
would
say
getting.
Data
on
use
and
getting
data
on
you
know
are
things
improving
is,
is,
is
a
key
challenge
for
this
kind
of
program
and
a
lot
of
what
I've
done
was
sort
of
you
know
intuition
and
hopefully
some
of
it
worked,
but
but
it
would
be
good
to
know
that
better.
I
wonder
if
other
programs
have
better
access
to
that.
A
B
Yeah
I
can
get
testers
like
I
say
you
know
I
I
typically
get
you
know
two
or
three
testers
for
a
feature,
but
I
meant,
like
you,
know,
large
usage
statistics
like
getting.
You
know,
understanding
guiding
from
a
hundred
people.
You
know
when
I
worked
on
speech
recognition.
We
would
have
you
know
fifty
thousand
a
hundred
thousand
a
million
test
things
and
we
would,
you
know,
make
leaks
to
the
algorithms
and
we
would
see
it
improve
and
self-driving
cars
the
same
way.
B
B
B
B
You
know
something's
going
to
fail
now,
but
nothing
has
failed.
Yet
I'm
trying
to
unjinx
it
by
saying
that
you
figure,
if
I
say
it's
going
to
fail,
you
know
it's
a
demo
syndrome.
Okay,
so
we
find
the
target
well,
the
first
thing
you
got
to
do.
I
don't
know
why
it
doesn't
do
it
itself
is
unpark,
so
I'll
un-park.
B
B
B
B
B
A
B
Okay,
so
then
I
mean
obviously
I'm
not
going
to
be
able
to
turn
the
knobs,
but
let
me
show
you
what
you
would
do.
So
what
you
do
is
you,
you
know,
make
the
window
a
little
bigger,
because
damn
it
that
window's
too
small
find
something
that
you
want
to
move.
You
know,
so
you
you
find
a
star
I'll
click
on
the
north
star
and
we'll
just
zoom
in
there
right.
B
Sure
right,
so
it's
telling
me
you
know.
Well,
maybe
I
shouldn't
have
picked
that
maybe
you
know
in
this
case.
Maybe
it's
too
fuzzy
since
we're
so
small
I'll
pick
this
star,
and
so
you
could
sort
of
see.
I
mean
you
know.
Maybe
you
know
you
want
a
reliable
star
too,
but
in
any
event,
who
cares
so
I'll
put
it
to
the
middle
and
zoom
in
some
more
and
you
know
there
you
go
right,
and
so
at
this
point
let's
say
this
is
set
up
enough.
B
B
A
B
A
I
mean
the
seeing
will
affect
as
you
make
adjustments.
You'll
see
your
star
move
around
a
little
bit.
If
there's
you
know,
if
the
scene
isn't
really
steady,
so
it
might
be
slightly
less
accurate,
I
suppose,
but
it's
gonna
average
to
the
same.
You
know
to
the
center
of
what
you're
trying
to
adjust
to
probably
over
over
time.
I
I
suppose
is
that
correct.
I.
B
Yeah
I
mean
yeah,
I
think
the
seeing
errors
is
small,
don't
worry
about
it
and
yeah
and
I
think
people
fret
about
polar
alignment
a
little
too
much
anyway.
I
mean
like,
like
bruce
said.
I
know
I
would
have
probably
reduced
it
if
it
was
five,
but
one
arc
minute
seems
probably
plenty
now
I
don't
have.
I
don't
know,
does
that
change
when
you
have
a
longer
scope,
I
mean.
A
E
B
E
D
A
I
D
E
E
C
E
E
E
A
A
A
A
B
B
I
think
in
that
was
the
word
I
was
looking
for
was
ask
him
indy.
Is
you
know
a
replacement
for
ascom
right?
It's
it's
separate,
it's
the
same
functionality,
and
so
no
it
doesn't
work
with
ascom.
It
uses
indy
and-
and
that's
my
point
was
that
drivers
tend
to
be
written
first
for
outcome
and
then
so,
I
think,
is
maybe
the
struggle
struggle
of
the
ecosystem.
Is
you
know
doing
that?
But
I
think
more
and
more
you
know.
Almost
all
the
new
equipment
was
an
indie
driver.
F
F
A
D
C
I
did
early
on
when
it
wasn't
fully
working
and
just
passed
over
it
from
there.
I
haven't
gone
back
to
it
since
it's
been
released,
but
I
I'm
not
sure
I'm
I'm
buying
into
the
the
concept
it
seems
like
you're
you're,
adding
points
of
failure
right.
So
just
so
so
people
are
clear
what
it
would
allow
you
to
do,
for
instance,
is
you
could
run
sgp
or
or
whatever?
Let's
say
whatever
uses,
azcom
that
you
like
to
use.
C
You
could
run
that
on
the
computer
in
the
house,
but
then
have
your
devices
out
on
the
on
the
telescope
computer
talking
across
the
network.
So
you
know
it's
it's
sort
of
a
little
different
than
than
doing
vnc
or
teamviewer
or
something
a
remote
desktop.
But
as
high
mentioned,
you
know,
if
you're
doing,
vnc
and
and
your
laptop
dies
it
doesn't
matter
because
you
can.
Your
raspberry
pi
out
on
the
computer
is
still
going.
C
B
B
D
A
B
I
have
to
say
about
it:
I
mean
it's
a
lot
faster
than
the
3b,
so
it
was
a
big
improvement
and,
and
probably
the
biggest
part
of
that
improvement
was
going
to
four
gigabytes.
One
gigabyte
was
just
you
know:
it's
not
a
modern
computer.
If
it
only
has
one
gigabyte
of
memory
right,
that's
just
too
little
memory.
So
you
know
the
pi
4
with
four
gigabytes
you
know
is
usable.
Is
it
a
fast
computer?
No
right!
It's
it's!
B
B
B
Is
it
lives
on
your
telescope
and
you
don't
think
about
it,
and
you
know
it
doesn't
reboot
in
the
middle
of
the
night
and
all
that
am
I
tempted
to
buy
a
faster
computer
sure
you
know
I
mean
it
seems
ridiculous
that
you
know
people
spend
all
this
money
on
equipment
and
then
insist
on
spending
fifty
dollars
for
their
computer
right.
Well,.
B
Right
so
so
does
the
pie,
work
yes
and,
and
the
pie
is,
is
ubiquitous,
and
so
it's
supported
well
and
you
know
there's
a
lot
of
you
know
the
software
is
going
to
work
better
on
it
than
some
computer.
That
is
twice
as
fast,
but
nobody
uses
right.
So
anyway,
you
get
the
idea,
it
works,
and
it's
what
I
use
you
sure
it
would
be.
I
don't
develop
on
it
right,
not
at
all
right
I
develop
on
my
mac.
B
I
run
a
virtual
machine
ubuntu
on
my
mac
and
you
know
all
my
compiling
my
initial
testing.
Everything
runs
on
my
mac.
I
get
some
code,
that's
you
know
and
by
the
way
the
compile
is
an
order
of
magnitude
faster,
and
I
I
kid
you
not
when
I
say
an
order
of
magnitude,
it's
an
order,
but
you
know
I
got
a
fast
mac
and.
B
B
B
B
C
B
C
B
C
I
C
F
B
B
I
mean
how
many
bits
is
a
4k
I
mean
is
a
a
color
image.
I
mean
there
are
a
lot
of
people
that
shoot
color.
I
think
I
think
it
does
okay,
you
know
it
could
be
that
the
download
time
you
know
the
usb
3
time
to
get
it
from
the
camera
to
the
pi
might
be
10
seconds
or
something
like
that
for
the
cut
for
the
big
image.
But
I
don't
think
the
processing
you
know
just
learning
the
image
you
know
finding
the
stars.
Whatever
would
be
that
bad.
B
The
whole
image,
oh
by
the
way,
getting
back
to
that
rgb
question.
You
know
it's
it's
downloading
the
the
raw
file,
so
it
actually
is
the
same
number
of
bits
as
a
monochrome
pixels
as
a
monochrome,
because
it
has
a
bayer
pattern.
It
really
isn't
three
times
so
now,
you're
saying
in
the
preview,
you
could
turn
it
into
a
color
image
but
and
k
stars.
Don't
do
that
if
you
wanted
to,
but
you
you
also
have
the
option
of
just
not.
B
B
Yeah,
I
don't
know
I
mean
it's,
I
think
the
download
the
for
my
16
asi
1600.
You
know
it
takes
a
ballpark,
a
second
to
load
over
usb
3..
You
know
from
the
camera
to
the
to
the
you
know
to
the
pi
it
it
takes
longer
than
that
if
you
to
move
it
from
the
pi
to
your
computer,
but
I
don't
do
that,
you
know
I
just
throw
the
thing
on
a
fast
stick
and
in
the
morning
I
carry
my
stick
in
you
know
into
my
computer.
You
know
sneaker
net.
C
B
C
No,
that's
not
why,
but
it's
one
of
the
the
the
things
that
I
think
causes
problems
with
asi
1600
and
I'm
still
not
100
sure
which
end
of
the
graph
is
which
end
of
the
knob
is
is
which,
but
I
I
tend
to
run
mine
at
80
or
90,
and
they
keep
telling
you.
You
know
these
chinese
translated
instructions
say
you
know
if
no
picture
decrease
the
throttling
or
something
which
I'm
not,
you
know
sure,
which
way
they
mean
to
go,
but.