Observation workflows in KStars -- looking for feedback and ideas

[Akarsh Simha]

Hi all,

I'm just trying to get a sense of how people use the Observation Planner. A
long time ago, the "Observation Planner" was called "Observing List" and
just carried:
(a) A list of objects
(b) Ability to add notes / observation logs
can't remember what else -- there may have been Alt vs Time

But anyway, in 2009, Prakash Mohan and I worked together as part of GSoC to
add the DSS image download feature, and the bifurcation between a "Session
Plan" and a "Wishlist". Back then, my idea was as follows:
1. Whenever you come across an object that interests you, add it to your
Wish List
2. Before you go out observing, plan out your observing session by
importing the objects you wish to see from your wish list into your
"session plan". KStars automatically assigns the upper meridian transit
time on the night of observation (I suspect this is currently broken) as
the observing time for each object.
3. Before you go out to a dark place, while you still have fast internet
access, download any reference images you need from the DSS
4. On the observing field, sort the observing session plan by observation
time. A special sorting filter sorts it from evening to morning.
5. Work through your objects in order.
I have a tendency to pack my night with as many objects as I can possibly
observe, and I imagined that the above workflow would maximize my
efficiency.

After trying this out on the field a few times, though, I found it very
sub-par for visual observing. The reason is, it is difficult to estimate
correctly how long it takes to observe an object. And the above is not
robust to, let's say, losing half an hour due to dinner. Moreover, for
those of us who observe with Dobsonians, sometimes meridian transit is a
very inconvenient time to observe an object because of the singular motion
of azimuth around the zenith ("Dobson's Hole" / "the Dob hole").

So I later came up with the following workflow that only involves the "Wish
List":
1. Whenever you come across an object that interests you, add it to your
Wish List.
2. Before you go out to a dark place, while you still have fast internet
access, download any reference images you need from the DSS
3. On the observing field, sort the _wish list_ by % of max. altitude
achieved at current time, while demoting the objects that are in the hole.
4. At any given time, pick your favorites amongst the top 5 or 10 objects
in the sorted list and observe it.

I have found the above wishlist-based workflow exceptional for visual
observing. So much so that I am tempted to deprecate the session plan
workflow, but I do think:
(a) The session plan workflow is much better suited for imaging /
scientific observations
(b) There might still be people out there using the session plan workflow
so I do think we should still retain it.

Now, finally, I have a few more itches to scratch with the wishlist
workflow:
1. Wish list grows to unmanageable sizes very quickly.
2. There is no easy way of removing/demoting objects that you have already
observed.
3. Plus, unlike with the session plan, there's no scope for targeted
observing projects -- just one massive wishlist.

I'm looking for other people's "itches" with these workflows, and trying to
understand how others use the Observation Planner, if at all. I remember
Jasem telling me it's also integrated somehow with the Ekos sequencer, so
I'm curious to know how that works. Finally, I'm proposing the following
changes:

1. Let the Wish List remain a massive "Wish List"
2. Move/replicate the "% of max. altitude" workflow into the session plan
instead.
3. Provide flexible ways of selecting and adding objects from the Wish List
into the session plan (eg: only objects in a certain constellation, only
objects in a certain catalog, only objects matching a certain regex, only
objects that will attain culmination tonight, only objects which are above
a certain magnitude...)
4. Preserve the old workflow of "assigned times" for objects, and fix any
bugs in it
5. Provide an "Observed" checkbox that will demote the object in the "% of
max. altitude" workflow, if checked.
6. Provide a way of removing objects that have already been observed from
the session plan / wishlist

I believe these features will create a much smoother observation experience
for anyone interested in using the Observation Planner for observing. Now,
I don't have enough context on imagers' requirements, but if there are any
allied requirements, I would be happy to incorporate them into a project.

The plan for this project is either I will slowly do it over my weekends
and evenings, or work with a GSoC / SoK student to achieve these goals.
Anyone else interested is also welcome.

Regards
Akarsh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20201030/7bd0a8b1/attachment.htm>