Debian Codegraph @

docs/faq/terminology.rst

raw
1 .. _terminology:
2
3 ***********
4 Terminology
5 ***********
6
7 Scheduling
8 ==========
9
10 Scheduling observations is a common task in astronomy, but there is a lack of
11 formal terminology. Here we define the terminology as it will be used in astroplan
12 for scheduling tasks. This is for consistency within the code and the documentation.
13
14 The terms used are as follows:
15
16 * **observing block** (**OB**): an observation of a target for an amount of time
17 and a particular instrument configuration.
18 * **priority**: number assigned to the **observing block** by the user that
19 defines its precedence within the set of blocks to be scheduled. Should probably
20 also be on a 0->1 (0=no good, 1=good) scale, or rescaled within the scheduler
21 * **rank**: like a **priority**, but defined for a specific set of **OB**s, often set
22 by an agent other than the observer. (e.g. a proposal is **ranked** by a time
23 allocation committee (TAC))
24 * **constraint**: sets limits and can yield **scores** based on inputs. Currently
25 only boolean scores are implemented in the code.
26 * **score**: the value returned by evaluating a **constraint** or **constraints**. Can be
27 boolean or floats between 0 and 1 inclusive (0=no good, 1=good), with a flag in the
28 ``Constraint`` call that selects which is used. Can be combined by a **scorekeeper**
29 into a cumulative score for an **observing block** given a start time.
30 * **scorekeeper**: assigns a cumulative score to the **OB** based on some function that
31 would be applied to all the individual **scores** (result should be in (0, 1))
32 * **scheduler**: the entity that consumes the results of the **scorekeeper** and the
33 **observing blocks** and produces a schedule
34 * **Weights** (“user defined”?): preferences for which constraint's **scores** matter most
35 (e.g. I care more about getting dark time than getting a low airmass). **weights** can be
36 floats between 0 and 1 inclusive (0=not important, 1 = important)
37
38
39 This is a list of possible schedulers, none are implemented yet. Once implemented they
40 will have different methods for creating their schedule. Below is a list of ideas for
41 the scheduler descriptors and the related scheduler would work. Each scheduler will be
42 able to be called with ``DescriptorScheduler(args)`` using the descriptor defined below.
43
44 * **Sequential**: starts from the beginning of the time range and schedules the **OB**
45 with the best **score**, that hasn't already been scheduled, for that time.
46 * **Priority**: starts from the highest **priority** **OB** and schedules it at the time
47 where it has its highest **score**. Then schedules the next-highest priority without
48 overlapping blocks