NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Dynamic > ADASS2008 (r1.1 vs. r1.45)
   Changes | Index | Search | Go
 <<O>>  Difference Topic ADASS2008 (r1.45 - 23 Sep 2008 - PaulMarganian)
Changed:
<
<

  • Abstract: The web technologies utilized for the Robert C. Byrd Green Bank Telescope's (GBT) new Dynamic
Scheduling System (see 'The GBT Dynamic Scheduling System: A New Scheduling Paradigm') are discussed, focusing on languages, frameworks, and tools. We use a popular Python web framework, TurboGears?, to take advantage of the extensive web services the system provides. TurboGears? is a model-view-controller framework, which aggregates SQLAlchemy, Genshi, and CherryPy? respectively. On top of this framework, Javascript (Prototype, script.aculo.us) and cascading style sheets (Blueprint) are used for desktop-quality web pages.
>
>

  • Abstract: The web technologies utilized for the Robert C. Byrd Green Bank Telescope's (GBT) new Dynamic Scheduling System are discussed, focusing on languages, frameworks, and tools. We use a popular Python web framework, TurboGears?, to take advantage of the extensive web services the system provides. TurboGears? is a model-view-controller framework, which aggregates SQLAlchemy, Genshi, and CherryPy? respectively. On top of this framework, Javascript (Prototype, script.aculo.us) and cascading style sheets (Blueprint) are used for desktop-quality web pages.

 <<O>>  Difference Topic ADASS2008 (r1.44 - 15 Sep 2008 - MikeMcCarty)
Changed:
<
<

The renaissance of the web has driven development of many new technologies to that have forever changed the way we write software. The resulting tools have been applied to both solve problems and created new ones in a wide range of domains ranging from monitor and control user interfaces to information distribution. This discussion covers which of and how these technologies are being used in the astronomical computing community. Topics include JavaScript?, Cascading Style Sheets, HTML, XML, JSON, RSS, iCalendar, Java, PHP, Python, Ruby on Rails, database technologies, and web frameworks/design patterns.

>
>

The renaissance of the web has driven development of many new technologies that have forever changed the way we write software. The resulting tools have been applied to both solve problems and created new ones in a wide range of domains ranging from monitor and control user interfaces to information distribution. This discussion covers which of and how these technologies are being used in the astronomical computing community. Topics include JavaScript?, Cascading Style Sheets, HTML, XML, JSON, RSS, iCalendar, Java, PHP, Python, Ruby on Rails, database technologies, and web frameworks/design patterns.


 <<O>>  Difference Topic ADASS2008 (r1.43 - 11 Sep 2008 - KarenONeil)
Changed:
<
<

Birds Of a Feather (BOF) discussion

>
>

Birds Of a Feather (BOF) discussions

Renaissance of the Web

Changed:
<
<

Web Technologies

>
>

The renaissance of the web has driven development of many new technologies to that have forever changed the way we write software. The resulting tools have been applied to both solve problems and created new ones in a wide range of domains ranging from monitor and control user interfaces to information distribution. This discussion covers which of and how these technologies are being used in the astronomical computing community. Topics include JavaScript?, Cascading Style Sheets, HTML, XML, JSON, RSS, iCalendar, Java, PHP, Python, Ruby on Rails, database technologies, and web frameworks/design patterns.

Deleted:
<
<

The renaissance of the web has driven development of many new technologies to that have forever changed the way we write software. The resulting tools have been applied to both solve problems and created new ones in a wide range of domains. This discussion covers how these technologies are being used in the scientific computing community.

Changed:
<
<

We'd like to start a BOF on Telescope Scheduling, but:

  • what to call it?
  • how to describe it?
  • where the heck on the adass.org site do you register your BOF?
>
>

Engaging the Observer

Changed:
<
<

-- MikeMcCarty - 09 Jul 2008

>
>

Procedures and policies such as automated observing, remote observing, service observing, or dynamic scheduling, while providing for more efficient use of telescopes, has rendered the role of the observer as more of a customer than a partner in the process of observing. Where once the presence and interaction of the astronomer with observatory staff encouraged understanding and responsiveness by both staff and observers, observatories now often face the problem of the timely providing and receiving of information with observers. Topics include scheduling, data quality, observing training and preparation, and information distribution technologies (web sites, email, RSS, etc.). The BOF is to share experiences and methods of engaging the observer.

Dynamic Telescope Scheduling Experiences

Basing a telescope's schedule on more reliable, short-term weather forecasts has the promise of providing better matches between observing needs and conditions, but it also creates new problems. For this BOF, we hope to share experiences, problems, and/or solutions resulting from "on-the-fly" telescope scheduling, either the scheduling of a sequence of observing scripts in service observing or the direct granting of telescope time for interactive observing. Topics include, but are not limited to: weather forecasting, time dependent scoring of projects, efficient telscope use, schedule packing, handling observing overhead, monitoring projects, observer schedules and constraints, inter-telescope dependencies (VLB), observer expectations, equipment availability, observatory/observer interactions, project candidate pools, and targets of opportunity.


 <<O>>  Difference Topic ADASS2008 (r1.42 - 04 Sep 2008 - MikeMcCarty)
Added:
>
>

Web Technologies

The renaissance of the web has driven development of many new technologies to that have forever changed the way we write software. The resulting tools have been applied to both solve problems and created new ones in a wide range of domains. This discussion covers how these technologies are being used in the scientific computing community.


 <<O>>  Difference Topic ADASS2008 (r1.41 - 15 Aug 2008 - JulesHarnett)
Changed:
<
<

  • Title: The GBT Dynamic Scheduling System: Scheduling
  • Authors: J. Harnett, C. Bignell, K. O'Neil, D. Balser, J. Braatz, M. Clark, M. McCarty, P. Marganian, A. Shelton
>
>

  • Title: The GBT Dynamic Scheduling System: The Scheduler's Perspective
  • Authors: J. Harnett, C. Bignell, K. O'Neil, D. Balser, J. Braatz, M. Clark, M. McCarty, P. Marganian, A. Shelton, R. Maddalena
Changed:
<
<

Before June 2008, scheduling at the Robert C. Byrd Green Bank Telescope (GBT) was accomplished using two templates, one a high frequency (>4.8 GHz) schedule the other low frequency, constructed by the GBT telescope scheduler. The beta testing of the Dynamic Scheduling System (DSS) has provided a a more efficient method of interleaving the various types of observing sessions. For the summer, 2008 beta testing the observing sessions were broken into three groups - fixed such as pulsar monitoring, windowed such as particular dates required by the observer and open that can run at any time. Some constraints of the beta version of the DSS are an inability to handle GBT receiver availability, no audit trail and an the inflexible handling of session durations chosen by observers. We describe the new scheduling process together with advantages and limitations akin to those above, and the impact on observers from the scheduler's viewpoint. Finally we suggest improvements that will be incorporated into future DSS releases.

>
>

Before June 2008, scheduling at the Robert C. Byrd Green Bank Telescope (GBT) was accomplished using two templates, one a high frequency (>4.8 GHz) schedule to run in good weather, the other low frequency. These were constructed and maintained by the GBT telescope scheduler. The beta testing of the Dynamic Scheduling System (DSS) has provided a a more efficient method of interleaving the various types of observing sessions. For summer 2008, these sessions were divided into three groups - fixed such as coordinated VLBI observations, windowed such as pulsar monitoring, and open that can run at any time. Although there are inefficiencies and limitations in the System from the scheduler's perspective, a particularly valuable feature is the ability to handle flexible scheduling of high frequency projects based on weather forecasts. We describe the new scheduling process in some detail and its impact on observers from the scheduler's viewpoint. Finally we suggest improvements that will be incorporated into future DSS releases.


 <<O>>  Difference Topic ADASS2008 (r1.40 - 15 Aug 2008 - KarenONeil)
Changed:
<
<

Before June 2008, scheduling at the Robert C. Byrd Green Bank Telescope (GBT) was accomplished using two templates, one a high frequency (>4.8 GHz) schedule the other low frequency, constructed by Dr Carl Bignell. The advent of the DSS has provided a a more efficient method of interleaving 3 types of observing sessions: fixed such as pulsar monitoring, windowed such as particular dates required by the observer and open that can run at any time. Some constraints of this beta version are an inability to handle GBT receiver availability, no audit trail and an the inflexible handling of session durations chosen by observers. We describe the new scheduling process together with advantages and limitations akin to those above, and the impact on observers from the scheduler's viewpoint. Finally we suggest improvements that should be incorporated into the next DSS release.

>
>

Before June 2008, scheduling at the Robert C. Byrd Green Bank Telescope (GBT) was accomplished using two templates, one a high frequency (>4.8 GHz) schedule the other low frequency, constructed by the GBT telescope scheduler. The beta testing of the Dynamic Scheduling System (DSS) has provided a a more efficient method of interleaving the various types of observing sessions. For the summer, 2008 beta testing the observing sessions were broken into three groups - fixed such as pulsar monitoring, windowed such as particular dates required by the observer and open that can run at any time. Some constraints of the beta version of the DSS are an inability to handle GBT receiver availability, no audit trail and an the inflexible handling of session durations chosen by observers. We describe the new scheduling process together with advantages and limitations akin to those above, and the impact on observers from the scheduler's viewpoint. Finally we suggest improvements that will be incorporated into future DSS releases.


 <<O>>  Difference Topic ADASS2008 (r1.39 - 15 Aug 2008 - JulesHarnett)
Changed:
<
<

  • Authors: J. Harnett, K. O'Neil, D. Balser, C. Bignell, J. Braatz, M. Clark, M. McCarty, P. Marganian, A. Shelton
>
>

  • Authors: J. Harnett, C. Bignell, K. O'Neil, D. Balser, J. Braatz, M. Clark, M. McCarty, P. Marganian, A. Shelton
Changed:
<
<

>
>

Before June 2008, scheduling at the Robert C. Byrd Green Bank Telescope (GBT) was accomplished using two templates, one a high frequency (>4.8 GHz) schedule the other low frequency, constructed by Dr Carl Bignell. The advent of the DSS has provided a a more efficient method of interleaving 3 types of observing sessions: fixed such as pulsar monitoring, windowed such as particular dates required by the observer and open that can run at any time. Some constraints of this beta version are an inability to handle GBT receiver availability, no audit trail and an the inflexible handling of session durations chosen by observers. We describe the new scheduling process together with advantages and limitations akin to those above, and the impact on observers from the scheduler's viewpoint. Finally we suggest improvements that should be incorporated into the next DSS release.


 <<O>>  Difference Topic ADASS2008 (r1.38 - 15 Aug 2008 - JimBraatz)
Changed:
<
<

  • Authors: J. Braatz, D. Balser, C. Bignell, M. Clark, M. McCarty, P. Marganian, A. Shelton
>
>

  • Authors: J. Braatz, D. Balser, C. Bignell, M. Clark, J. Harnett, M. McCarty, P. Marganian, K. O'Neil, A. Shelton
Changed:
<
<

software tools to help observers manage scheduling their projects, to notify

>
>

software tools to help observers manage their projects, to notify

Changed:
<
<

projects will make the schedule. In this contribution we will report

>
>

projects will get scheduled. In this contribution we will report


 <<O>>  Difference Topic ADASS2008 (r1.37 - 15 Aug 2008 - KarenONeil)
Changed:
<
<

The Robert C. Byrd Green Bank Telescope (GBT) Dynamic Scheduling System (DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are scheduled on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters. Observing projects are divided into a number of possible observing sessions, which may be classified as Fixed, Open or Windowed. Observations are scheduled with a minimum of 24-hour notice, and observers are able to schedule blackout times and dates for which they will not be available. To accommodate the <20% of the time when schedules can change due to, e.g. a sudden change in the weather, certain projects can be designated as backup and be run either by the telescope operator or by an observer who has elected to be called at upon with no notice.

>
>

The Robert C. Byrd Green Bank Telescope (GBT) Dynamic Scheduling System (DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are scheduled on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters. Observing projects are divided into a number of possible observing sessions, which may be classified as Fixed, Open or Windowed. Observations are scheduled with a minimum of 24-hour notice, and observers are able to schedule blackout times and dates for which they will not be available. To accommodate the <20% of the time when schedules can change due to, e.g. a sudden change in the weather, certain projects can be designated as backup and be run either by the telescope operator or by an observer who has elected to be called upon with no prior notice.

Changed:
<
<

The scheduling algorithm then uses all available data to determine the most efficient schedule for the GBT over the subsequent 24-hours. This demonstration presents an overview of the GBT DSS including the ranking and scheduling algorithms for TPs, scheduling probabilities generation, the web framework for the system, and a summary of the beta testing which were held in the from June - September, 2008

>
>

The scheduling algorithm then uses all available data to determine the most efficient schedule for the GBT over the subsequent 24-hours. This demonstration presents an overview of the GBT DSS including the ranking and scheduling algorithms, scheduling probabilities generation, the web framework for the system, and a summary of the beta testing which was held from June - September, 2008


 <<O>>  Difference Topic ADASS2008 (r1.36 - 15 Aug 2008 - KarenONeil)
Changed:
<
<

  • Title: The GBT Dynamic Scheduling System: A Demo
>
>

  • Title: The GBT Dynamic Scheduling System: Demonstrating the System
Changed:
<
<

The Robert C. Byrd Green Bank Telescope (GBT) Dynamic Scheduling System(DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are schedules on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters (constraints?). Observing projects are divided into a number of possible observing sessions, which may be classified Fixed, Open or Windowed. Observers may elect to be available at all times; ie they can be called upon with no notice to use an Telescope Period (TP) which has become available because of changes in local conditions, eg a sudden change in the weather. Alternately, they can elect to observe with 24-hours notice (the regular decision) or can black themselves out for time when they cannot observe. The Scheduling algorithm then uses all such data to determine the most efficient schedule for the GBT over the following 24-hours. This poster presents an overview of the GBT DSS including the ranking and scheduling algorithms for TPs, scheduling probabilities generation, the web framework for the system, and a summary of the beta testing which were held in the from June - September, 2008

>
>

The Robert C. Byrd Green Bank Telescope (GBT) Dynamic Scheduling System (DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are scheduled on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters. Observing projects are divided into a number of possible observing sessions, which may be classified as Fixed, Open or Windowed. Observations are scheduled with a minimum of 24-hour notice, and observers are able to schedule blackout times and dates for which they will not be available. To accommodate the <20% of the time when schedules can change due to, e.g. a sudden change in the weather, certain projects can be designated as backup and be run either by the telescope operator or by an observer who has elected to be called at upon with no notice.

The scheduling algorithm then uses all available data to determine the most efficient schedule for the GBT over the subsequent 24-hours. This demonstration presents an overview of the GBT DSS including the ranking and scheduling algorithms for TPs, scheduling probabilities generation, the web framework for the system, and a summary of the beta testing which were held in the from June - September, 2008


 <<O>>  Difference Topic ADASS2008 (r1.35 - 14 Aug 2008 - KarenONeil)
Changed:
<
<

  • Abstract: The Robert C. Byrd Green Bank Telescope (GBT) is implementing a new Dynamic Scheduling System (DSS)designed to maximize the observing efficiency of the telescope while ensuring that none of the flexibility and ease of use of the GBT is harmed and the data quality of observations is not adversely affected. To accomplish this, the GBT DSS is implementing a dynamic scheduling systems which schedules observers, rather than running scripts. The DSS works by breaking each project into one or more sessions which have associated observing criteria such as RA, Dec, frequency, etc. Potential observers may also enter dates when members of their team will not be available for either on-site or remote observing. The scheduling algorithm uses those data, along with the predicted weather, to determine the most efficient schedule for the GBT. The DSS provides all observers at least 24 hours notice of their upcoming observing. In the uncommon (< 20%) case where the predictions do not match the actual weather, a backup project, chosen from the database, will be run instead. Here we give an overview of the GBT DSS project, including the ranking and scheduling algorithms for the sessions, the scheduling probabilities generation, the web framework for the system, and an overview of the results from the beta testing which were held in the from June - September, 2008.
>
>

  • Abstract: The Robert C. Byrd Green Bank Telescope (GBT) is implementing a new Dynamic Scheduling System (DSS)designed to maximize the observing efficiency of the telescope while ensuring that none of the flexibility and ease of use of the GBT is harmed and that the data quality of observations is not adversely affected. To accomplish this, the GBT DSS is implementing a dynamic scheduling system which schedules observers, rather than running scripts. The DSS works by breaking each project into one or more sessions which have associated observing criteria such as RA, Dec, and frequency. Potential observers may also enter dates when members of their team will not be available for either on-site or remote observing. The scheduling algorithm uses those data, along with the predicted weather, to determine the most efficient schedule for the GBT. The DSS provides all observers at least 24 hours notice of their upcoming observing. In the uncommon (< 20%) case where the actual weather does not match the predictions, a backup project, chosen from the database, is run instead. Here we give an overview of the GBT DSS project, including the ranking and scheduling algorithms for the sessions, the scheduling probabilities generation, the web framework for the system, and an overview of the results from the beta testing which were held from June - September, 2008.
Changed:
<
<

  • Authors: D. Balser, J. Condon, R. Maddalena, others?
>
>

  • Authors: D. Balser, Carl Bignell (NRAO), J. A. Braatz (NRAO), Mark H. Clark (NRAO), J. J. Condon (NRAO), Karen O'Neil (NRAO), Paul Marganian (NRAO), Mike McCarty? (NRAO), Eric Sessoms (NRAO), Amy Shelton (NRAO), Ron Maddalena (NRAO)

 <<O>>  Difference Topic ADASS2008 (r1.34 - 14 Aug 2008 - MarkClark)
Changed:
<
<

on the other hand, using the best forecasts would require observers to be constantly "on-call."

>
>

however, using the best forecasts would require observers to be constantly "on-call."

Changed:
<
<

weather forecasts from previous years,

>
>

weather forecasts from previous years


 <<O>>  Difference Topic ADASS2008 (r1.33 - 13 Aug 2008 - PaulMarganian)
Changed:
<
<

Scheduling System (see poster?) are discussed, focusing on languages,

>
>

Scheduling System (see 'The GBT Dynamic Scheduling System: A New Scheduling Paradigm') are discussed, focusing on languages,


 <<O>>  Difference Topic ADASS2008 (r1.32 - 12 Aug 2008 - PaulMarganian)
Changed:
<
<

  • Abstract: The web technologies utilized for the new Robert C. Byrd Green Bank Telescope (GBT) Dynamic
>
>

  • Abstract: The web technologies utilized for the Robert C. Byrd Green Bank Telescope's (GBT) new Dynamic
Changed:
<
<

leverage the extensive web services the system provides. TurboGears? is a

>
>

take advantage of the extensive web services the system provides. TurboGears? is a

Changed:
<
<

desktop-quality web pages. It Rocks.

>
>

desktop-quality web pages.


 <<O>>  Difference Topic ADASS2008 (r1.31 - 11 Aug 2008 - KarenONeil)
Changed:
<
<

  • Abstract: Need Eric to characterize the solution
>
>

  • Abstract: We applied algorithmic approaches to both theoretical and practical aspects of scheduling the Robert C. Byrd Green Bank Telescope (GBT).

On the theoretical side, assigning a numerical value to a telescope period is only one piece of the puzzle. The other piece consists of using that score to determine the best global arrangement of telescope periods in order to maximize the scientific throughput of the telescope. The naive brute-force approach of trying all possible schedules is too computationally expensive. Instead we applied a well-studied approach from operations research, known as dynamic programming. Specifically, we found the so-called "knapsack" algorithm to be a good fit to this problem.

On the other hand, we cannot actually achieve maximum theoretical efficiency due to many practical constraints on telescope scheduling. The most severe practical constraints are fixed periods - that must be scheduled at a specific date and time regardless of possible score - and windowed periods that must be scheduled in regular, recurring intervals.

The primary difficulty in scheduling fixed and windowed sessions is that they have the potential to conflict and even to generate irresolvable conflicts (double booking). In working on this problem we realized it shared many characteristics with the game of sudoku. In sudoku, there are many possible arrangements of the recurring numbers 1 through 9 (telescope sessions). Some of these are fixed (the hints) and the others must live in windows (distinct groups having one instance each of each digit).

Sudoku puzzles are solved algorithmically using a heuristic-guided brute-force search. We followed a similar approach. A full brute-force search is, again, too computationally expensive, but we found ways to restrict the search enough to make it feasible. We used a number of heuristics but found the largest gains came from partitioning the problem into distinct subsets than can each be scheduled independently and from ordering the search in such a way that earlier choices had the greatest impact on reducing the computational complexity of later choices.


 <<O>>  Difference Topic ADASS2008 (r1.30 - 11 Aug 2008 - MikeMcCarty)
Changed:
<
<

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Robert C. Byrd Green Bank Telescope (GBT) were scheduled using the new Dynamic Scheduling System (DSS). Beta testing exercised the policies, algorithms, and software developed for the DSS project. The DSS was implemented as a web application due to the fact that observers are located all over the world. Technologies such as iCalendar, RSS feeds, email, and instant messaging are used to transfer as much or as little information as possible to observers based on their desires. We discuss the software engineering challenges which led to our implementation and relate our adaptation of agile development practices to design and develop the DSS. Additionally, we describe handling differences in expected versus actual initial conditions. We then identify lessons learned from beta testing and present conclusions.

>
>

During the summer trimester of 2008, all observations on the Robert C. Byrd Green Bank Telescope (GBT) were scheduled using the new Dynamic Scheduling System (DSS). Beta testing exercised the policies, algorithms, and software developed for the DSS project. Since observers are located all over the world, the DSS was implemented as a web application. Technologies such as iCalendar, RSS feeds, email, and instant messaging are used to transfer as much or as little information to observers based on their desires. We discuss the software engineering challenges leading to our implementation and relate our adaptation of agile development practices to design and develop the DSS. Additionally, we describe handling differences in expected versus actual initial conditions. We then identify lessons learned from beta testing and present conclusions.


 <<O>>  Difference Topic ADASS2008 (r1.29 - 11 Aug 2008 - PaulMarganian)
Added:
>
>

Birds Of a Feather (BOF) discussion

Added:
>
>

We'd like to start a BOF on Telescope Scheduling, but:

  • what to call it?
  • how to describe it?
  • where the heck on the adass.org site do you register your BOF?

 <<O>>  Difference Topic ADASS2008 (r1.28 - 11 Aug 2008 - MarkClark)
Changed:
<
<

along with the large frequency range of the Robert C. Byrd Green Bank Telescope (GBT),

>
>

along with the wide frequency coverage of the Robert C. Byrd Green Bank Telescope (GBT),

Changed:
<
<

within the time range when weather forecasts are reliable, however, using the best forecasts would require observers to be "on-call" within hours.

>
>

within a time range when weather forecasts are reliable; on the other hand, using the best forecasts would require observers to be constantly "on-call."

Changed:
<
<

weather forecasts from previous years (covering the trimester),

>
>

weather forecasts from previous years,

Changed:
<
<

of available weather forecasts (five days).

>
>

of available weather forecasts.


 <<O>>  Difference Topic ADASS2008 (r1.27 - 11 Aug 2008 - MarkClark)
Changed:
<
<

along with the flexibility of the Robert C. Byrd Green Bank Telescope (GBT),

>
>

along with the large frequency range of the Robert C. Byrd Green Bank Telescope (GBT),

Changed:
<
<

within the time frame of reliable weather forecasts. On the other hand, requiring observers to be "on-call" daily over a four-month trimester is asking a good deal of even the most dedicated astronomers (or their graduate students).

>
>

within the time range when weather forecasts are reliable, however, using the best forecasts would require observers to be "on-call" within hours.

Changed:
<
<

1) compromising between weather forecasts vs. observer notification, and 2) providing additional measures as to when specific projects might be scheduled. These latter additional indicators of the likelihood of being selected by the scheduling algorithms were derived from trimester simulations based on

>
>

1) compromising between the best weather forecasts vs. short-term observer notification, and 2) providing earlier indicators of the likelihood of being selected by the scheduling algorithms. These indicators were derived from simulations based on Green Bank

Changed:
<
<

(long-term),

>
>

(covering the trimester),

Changed:
<
<

over the extended time range

>
>

covering the entire time range

Changed:
<
<

(short-term).

>
>

(five days).


 <<O>>  Difference Topic ADASS2008 (r1.26 - 08 Aug 2008 - MarkClark)
Changed:
<
<

  • Authors: K. O'Neil, D. Balser, C. Bignell, M. Clark, J. Condon, M. McCarty, P. Marganian, A. Shelton, J. Braatz, J. Harnett, R. Maddelena, M. Mello, E. Sessoms
>
>

  • Authors: K. O'Neil, D. Balser, C. Bignell, M. Clark, J. Condon, M. McCarty, P. Marganian, A. Shelton, J. Braatz, J. Harnett, R. Maddalena, M. Mello, E. Sessoms
Changed:
<
<

  • Authors: D. Balser, J. Condon, R. Maddelena, others?
>
>

  • Authors: D. Balser, J. Condon, R. Maddalena, others?
Changed:
<
<

  • Authors: M. Clark, D. Balser, C. Bignell, J. Condon, M. McCarty, P. Marganian, K. O'Neil,, A. Shelton, R. Maddelena (? depends on fi you ar egoing to talk at all about the weather info)
>
>

  • Authors: M. Clark, D. Balser, E. Sessoms, C. Bignell, J. Condon, M. McCarty, P. Marganian, K. O'Neil,, A. Shelton, R. Maddalena

 <<O>>  Difference Topic ADASS2008 (r1.25 - 08 Aug 2008 - MikeMcCarty)
Changed:
<
<

  • Authors: K. O'Neil, D. Balser, C. Bignell, M. Clark, J. Condon, M. McCarty?, P. Marganian, A. Shelton, J. Braatz, J. Harnett, R. Maddelena, M. Mello, E. Sessoms
>
>

  • Authors: K. O'Neil, D. Balser, C. Bignell, M. Clark, J. Condon, M. McCarty, P. Marganian, A. Shelton, J. Braatz, J. Harnett, R. Maddelena, M. Mello, E. Sessoms
Changed:
<
<

  • Authors: E. Sessoms, M. Clark, P. Marganian, M. McCarty?, A. Shelton
>
>

  • Authors: E. Sessoms, M. Clark, P. Marganian, M. McCarty, A. Shelton
Changed:
<
<

  • Authors: P. Marganian, M. Clark, M. McCarty?, E. Sessoms, A. Shelton
>
>

  • Authors: P. Marganian, M. Clark, M. McCarty, E. Sessoms, A. Shelton
Changed:
<
<

  • Authors: J. Braatz, D. Balser, C. Bignell, M. Clark, M. McCarty?, P. Marganian, A. Shelton
>
>

  • Authors: J. Braatz, D. Balser, C. Bignell, M. Clark, M. McCarty, P. Marganian, A. Shelton
Changed:
<
<

  • Authors: J. Harnett, K. O'Neil, D. Balser, C. Bignell, J. Braatz, M. Clark, M. McCarty?, P. Marganian, A. Shelton
>
>

  • Authors: J. Harnett, K. O'Neil, D. Balser, C. Bignell, J. Braatz, M. Clark, M. McCarty, P. Marganian, A. Shelton
Changed:
<
<

  • Authors: M. McCarty?, M. Clark, P. Marganian, K. O'Neil, E. Sessoms, A. Shelton
>
>

  • Authors: M. McCarty, M. Clark, P. Marganian, K. O'Neil, E. Sessoms, A. Shelton
Changed:
<
<

  • Authors: M. Clark, D. Balser, C. Bignell, J. Condon, M. McCarty?, P. Marganian, K. O'Neil,, A. Shelton, R. Maddelena (? depends on fi you ar egoing to talk at all about the weather info)
>
>

  • Authors: M. Clark, D. Balser, C. Bignell, J. Condon, M. McCarty, P. Marganian, K. O'Neil,, A. Shelton, R. Maddelena (? depends on fi you ar egoing to talk at all about the weather info)

 <<O>>  Difference Topic ADASS2008 (r1.24 - 08 Aug 2008 - KarenONeil)
Added:
>
>

  • Authors: K. O'Neil, D. Balser, C. Bignell, M. Clark, J. Condon, M. McCarty?, P. Marganian, A. Shelton, J. Braatz, J. Harnett, R. Maddelena, M. Mello, E. Sessoms
Added:
>
>

  • Authors: D. Balser, J. Condon, R. Maddelena, others?
Added:
>
>

  • Authors: E. Sessoms, M. Clark, P. Marganian, M. McCarty?, A. Shelton
Added:
>
>

  • Authors: P. Marganian, M. Clark, M. McCarty?, E. Sessoms, A. Shelton
Added:
>
>

  • Authors: J. Braatz, D. Balser, C. Bignell, M. Clark, M. McCarty?, P. Marganian, A. Shelton
Changed:
<
<

I think this should be more about how things work from an observer's perspective. E.g. something like:

  • An observer's introduction to the GBT DSS
  • Entering (and changing) your session information
  • Scheduling notification (email, rss feeds, etc) and how well they all worked
  • Problems and issues
  • A look to the future (ease of use)
>
>

Scheduler's Perspective - Jules

  • Title: The GBT Dynamic Scheduling System: Scheduling
  • Authors: J. Harnett, K. O'Neil, D. Balser, C. Bignell, J. Braatz, M. Clark, M. McCarty?, P. Marganian, A. Shelton
  • Abstract:
Added:
>
>

  • Authors: M. McCarty?, M. Clark, P. Marganian, K. O'Neil, E. Sessoms, A. Shelton
Added:
>
>

  • Authors: M. Clark, D. Balser, C. Bignell, J. Condon, M. McCarty?, P. Marganian, K. O'Neil,, A. Shelton, R. Maddelena (? depends on fi you ar egoing to talk at all about the weather info)
Changed:
<
<

Demo/Overview - Jules

  • Title: The GBT Dynamic Scheduling System: An Overview
>
>

Demo

  • Title: The GBT Dynamic Scheduling System: A Demo
Changed:
<
<

    • We need to find out more about the demos - what will be available, etc.
>
>


 <<O>>  Difference Topic ADASS2008 (r1.23 - 07 Aug 2008 - MikeMcCarty)
Changed:
<
<

Teams's Perspective - Mike

  • Title: The GBT Dynamic Scheduling System: Results from Beta Testing - The Development Team's Perspective
>
>

Software Engineer's Perspective - Mike

  • Title: The GBT Dynamic Scheduling System: Development and testing
Changed:
<
<

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Robert C. Byrd Green Bank Telescope (GBT) were scheduled using the Dynamic Scheduling System (DSS). Beta testing exercised the policies, algorithms, and software developed for the DSS project. We will discuss the experience of using the DSS to schedule observers covering the daily process of creating a schedule, notifying observers of events, managing project information, and rescheduling due to unexpected circumstances. We also cover software engineering aspects such as adapting agile development practices to implement the DSS, handling differences in expected and actual initial conditions, and providing 24/7 support. We then identify lessons learned from the beta testing and present conclusions.

All the stuff from the beta testing except obs perspective

  • The scheduler's perspective
  • The software engineer's perspective
  • Lessons Learned
  • Conclusions - how efficient were we?
>
>

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Robert C. Byrd Green Bank Telescope (GBT) were scheduled using the new Dynamic Scheduling System (DSS). Beta testing exercised the policies, algorithms, and software developed for the DSS project. The DSS was implemented as a web application due to the fact that observers are located all over the world. Technologies such as iCalendar, RSS feeds, email, and instant messaging are used to transfer as much or as little information as possible to observers based on their desires. We discuss the software engineering challenges which led to our implementation and relate our adaptation of agile development practices to design and develop the DSS. Additionally, we describe handling differences in expected versus actual initial conditions. We then identify lessons learned from beta testing and present conclusions.


 <<O>>  Difference Topic ADASS2008 (r1.22 - 07 Aug 2008 - MarkClark)
Changed:
<
<

  • Abstract: The Robert C. Byrd Green Bank Telescope (GBT) is implementing a new Dynamic Scheduling System (DSS)designed to maximize the observing efficiency of the telescope while ensuring that none of the flexibility and ease of use of the GBT is harmed and the data quality of observations is not adversely affected. To accomplish this, the GBT DSS is implementing a dynamic scheduling systems which schedules observers, rather than running scripts. The DSS works by breaking each project into one or more sessions which have associated observing criteria such as RA, Dec, frequency, etc. Potential observers may also enter dates when members of their team will not be available for either on-site or remote observing. The scheduling algorithm uses those data, along with the predicted weather, to determine the most efficient schedule for the GBT. The DSS provides all observers at least 24 hours notice of their upcoming observing. In the uncommon (< 20%) case where the predictions do not match the actual weather, a backup project, chosen from the database, will be run instead. Here we give an overview of the GBT DSS project, including the ranking and scheduling algorithms for the sessions, the scheduling probabilities generation, the web framework for the system, and an overview of the results from the beta tests which were held in the from June - September, 2008.
>
>

  • Abstract: The Robert C. Byrd Green Bank Telescope (GBT) is implementing a new Dynamic Scheduling System (DSS)designed to maximize the observing efficiency of the telescope while ensuring that none of the flexibility and ease of use of the GBT is harmed and the data quality of observations is not adversely affected. To accomplish this, the GBT DSS is implementing a dynamic scheduling systems which schedules observers, rather than running scripts. The DSS works by breaking each project into one or more sessions which have associated observing criteria such as RA, Dec, frequency, etc. Potential observers may also enter dates when members of their team will not be available for either on-site or remote observing. The scheduling algorithm uses those data, along with the predicted weather, to determine the most efficient schedule for the GBT. The DSS provides all observers at least 24 hours notice of their upcoming observing. In the uncommon (< 20%) case where the predictions do not match the actual weather, a backup project, chosen from the database, will be run instead. Here we give an overview of the GBT DSS project, including the ranking and scheduling algorithms for the sessions, the scheduling probabilities generation, the web framework for the system, and an overview of the results from the beta testing which were held in the from June - September, 2008.
Changed:
<
<

    • Beta test results
>
>

    • Beta testing results
Changed:
<
<

  • Abstract: The web technologies utilized for the new Green Bank Telescope (GBT) Dynamic
>
>

  • Abstract: The web technologies utilized for the new Robert C. Byrd Green Bank Telescope (GBT) Dynamic
Changed:
<
<

Dynamic Scheduling System (DSS) for the Green Bank Telescope (GBT). The DSS

>
>

Dynamic Scheduling System (DSS) for the Robert C. Byrd Green Bank Telescope (GBT). The DSS

Changed:
<
<

  • Title: The GBT Dynamic Scheduling System: Results from Beta Tests - The Development Team's Perspective
>
>

  • Title: The GBT Dynamic Scheduling System: Results from Beta Testing - The Development Team's Perspective
Changed:
<
<

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Green Bank Telescope (GBT) were scheduled using the Dynamic Scheduling System (DSS). These beta tests exercised the policies, algorithms, and software developed for the DSS project. We will discuss the experience of using the DSS to schedule observers covering the daily process of creating a schedule, notifying observers of events, managing project information, and rescheduling due to unexpected circumstances. We also cover software engineering aspects such as adapting agile development practices to implement the DSS, handling differences in expected and actual initial conditions, and providing 24/7 support. We then identify lessons learned from the beta tests and present conclusions.

>
>

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Robert C. Byrd Green Bank Telescope (GBT) were scheduled using the Dynamic Scheduling System (DSS). Beta testing exercised the policies, algorithms, and software developed for the DSS project. We will discuss the experience of using the DSS to schedule observers covering the daily process of creating a schedule, notifying observers of events, managing project information, and rescheduling due to unexpected circumstances. We also cover software engineering aspects such as adapting agile development practices to implement the DSS, handling differences in expected and actual initial conditions, and providing 24/7 support. We then identify lessons learned from the beta testing and present conclusions.

Changed:
<
<

All the stuff from the beta tests except obs perspective

>
>

All the stuff from the beta testing except obs perspective

Changed:
<
<

along with the flexibility of the Green Bank Telescope (GBT),

>
>

along with the flexibility of the Robert C. Byrd Green Bank Telescope (GBT),

Changed:
<
<

During the 2008 summer trimester beta tests,

>
>

During the 2008 summer trimester beta testing,

Changed:
<
<

compromising between 1) weather forecasts vs. observer notification, and 2) providing some further measure when specific projects might be scheduled. Additional indicators of the likelihood of being selected by the

>
>

1) compromising between weather forecasts vs. observer notification, and 2) providing additional measures as to when specific projects might be scheduled. These latter additional indicators of the likelihood of being selected by the

Changed:
<
<

The new Green Bank Telescope (GBT) Dynamic Scheduling System(DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are schedules on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters (constraints?). Observing projects are divided into a number of possible observing sessions, which may be classified Fixed, Open or Windowed. Observers may elect to be available at all times; ie they can be called upon with no notice to use an Telescope Period (TP) which has become available because of changes in local conditions, eg a sudden change in the weather. Alternately, they can elect to observe with 24-hours notice (the regular decision) or can black themselves out for time when they cannot observe. The Scheduling algorithm then uses all such data to determine the most efficient schedule for the GBT over the following 24-hours. This poster presents an overview of the GBT DSS including the ranking and scheduling algorithms for TPs, scheduling probabilities generation, the web framework for the system, and a summary of the beta tests which were held in the from June - September, 2008

>
>

The Robert C. Byrd Green Bank Telescope (GBT) Dynamic Scheduling System(DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are schedules on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters (constraints?). Observing projects are divided into a number of possible observing sessions, which may be classified Fixed, Open or Windowed. Observers may elect to be available at all times; ie they can be called upon with no notice to use an Telescope Period (TP) which has become available because of changes in local conditions, eg a sudden change in the weather. Alternately, they can elect to observe with 24-hours notice (the regular decision) or can black themselves out for time when they cannot observe. The Scheduling algorithm then uses all such data to determine the most efficient schedule for the GBT over the following 24-hours. This poster presents an overview of the GBT DSS including the ranking and scheduling algorithms for TPs, scheduling probabilities generation, the web framework for the system, and a summary of the beta testing which were held in the from June - September, 2008


 <<O>>  Difference Topic ADASS2008 (r1.21 - 07 Aug 2008 - DanaBalser)
Changed:
<
<

  • Abstract: We discuss the ranking algorithm of the new Green Bank Telescope (GBT) Dynamic Scheduling System. Since the GBT is located in a continental, mid-latitude region where weather is dominated by water vapor and small-scale effects, the weather plays an important role in optimizing the observing efficiency of the GBT. We rank observing sessions as a product of many factors. Some factors are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. Simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
>
>

  • Abstract: We discuss the ranking algorithm of the Robert C. Byrd Green Bank Telescope (GBT) Dynamic Scheduling System. Since the GBT is located in a continental, mid-latitude region where weather is dominated by water vapor and small-scale effects, the weather plays an important role in optimizing the observing efficiency of the GBT. We rank observing sessions as a product of many factors. Some factors are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. Simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.

 <<O>>  Difference Topic ADASS2008 (r1.20 - 07 Aug 2008 - DanaBalser)
Changed:
<
<

  • Abstract: The new Green Bank Telescope (GBT) dynamic scheduling method is discussed, including the ranking algorithm that selects which observing session to schedule next, and simulations that compare dynamic scheduling with traditional GBT scheduling. We rank observing sessions as a product of many factors. Some are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. The simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
>
>

  • Abstract: We discuss the ranking algorithm of the new Green Bank Telescope (GBT) Dynamic Scheduling System. Since the GBT is located in a continental, mid-latitude region where weather is dominated by water vapor and small-scale effects, the weather plays an important role in optimizing the observing efficiency of the GBT. We rank observing sessions as a product of many factors. Some factors are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. Simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.

 <<O>>  Difference Topic ADASS2008 (r1.19 - 07 Aug 2008 - MarkClark)
Changed:
<
<

  • Title: The GBT Dynamic Scheduling System: Handling Observer's Expectations under Dynamic Scheduling: Providing Likelihoods of Getting Telescope Time Beyond Available Weather Forecasts - I hate the phrase "of Getting Telescope Time", anything better? How about "scheduling sessions" or "scheduling projects"
>
>

  • Title: The GBT Dynamic Scheduling System: "When do I observe?" Guiding Users' Expectations
Added:
>
>

Because of variable local weather in Green Bank, West Virginia, along with the flexibility of the Green Bank Telescope (GBT), substantial improvement in efficient use of telescope time is possible by dynamically scheduling observers within the time frame of reliable weather forecasts. On the other hand, requiring observers to be "on-call" daily over a four-month trimester is asking a good deal of even the most dedicated astronomers (or their graduate students). During the 2008 summer trimester beta tests, the GBT Dynamic Scheduling System (DSS) attempted to mitigate this inherent conflict by compromising between 1) weather forecasts vs. observer notification, and 2) providing some further measure when specific projects might be scheduled. Additional indicators of the likelihood of being selected by the scheduling algorithms were derived from trimester simulations based on weather forecasts from previous years (long-term), and from relative project rankings over the extended time range of available weather forecasts (short-term). We report our experience on the generation of the information, its presentation, and its use by observers.

Changed:
<
<

    • short term: using relative scoring
>
>

    • forecast/notification dichotomy
    • short term: using relative ranking
Added:
>
>

    • use statistics
    • user feedback

 <<O>>  Difference Topic ADASS2008 (r1.18 - 07 Aug 2008 - JimBraatz)
Changed:
<
<

  • Title: The Green Bank Telescope Dynamic Scheduling System: Results from Beta Tests - The Observers' Perspective
>
>

  • Title: The GBT Dynamic Scheduling System: The Observers' Perspective
Changed:
<
<

projects will make the schedule. In this contribution we will relate

>
>

projects will make the schedule. In this contribution we will report

Deleted:
<
<

Include the scheduling probabilities in this


 <<O>>  Difference Topic ADASS2008 (r1.17 - 06 Aug 2008 - MikeMcCarty)
Changed:
<
<

  • Title: The GBT Dynamic Scheduling System: Algorithms, Metrics, and Simulations
  • Abstract: We discuss the ranking algorithm of the new Green Bank Telescope (GBT) Dynamic Scheduling System. Since the GBT is located in a continental, mid-latitude region where weather is dominated by water vapor and small-scale effects, the weather plays an important role in optimizing the observing efficiency of the GBT. We rank observing sessions as a product of many factors. Some factors are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. Simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
>
>

  • Title: GBT Dynamic Scheduling System: Algorithms, Metrics, and Simulations
  • Abstract: The new Green Bank Telescope (GBT) dynamic scheduling method is discussed, including the ranking algorithm that selects which observing session to schedule next, and simulations that compare dynamic scheduling with traditional GBT scheduling. We rank observing sessions as a product of many factors. Some are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. The simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
Changed:
<
<

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Green Bank Telescope (GBT) were scheduled using the new Dynamic Scheduling System (DSS). These Beta tests exercised the policies, algorithms, and software developed for the DSS project. We will discuss the experience of using the DSS to schedule observers covering the daily process of creating a schedule, notifying observers of events, managing project information, and rescheduling due to unexpected circumstances. We also relate the software engineer's experience of using agile development practices to implement the DSS. We then identify lessons learned from the Beta tests and present conclusions.

>
>

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Green Bank Telescope (GBT) were scheduled using the Dynamic Scheduling System (DSS). These beta tests exercised the policies, algorithms, and software developed for the DSS project. We will discuss the experience of using the DSS to schedule observers covering the daily process of creating a schedule, notifying observers of events, managing project information, and rescheduling due to unexpected circumstances. We also cover software engineering aspects such as adapting agile development practices to implement the DSS, handling differences in expected and actual initial conditions, and providing 24/7 support. We then identify lessons learned from the beta tests and present conclusions.


 <<O>>  Difference Topic ADASS2008 (r1.16 - 06 Aug 2008 - DanaBalser)
Changed:
<
<

  • Title: GBT Dynamic Scheduling System: Algorithms, Metrics, and Simulations
  • Abstract: The new Green Bank Telescope (GBT) dynamic scheduling method is discussed, including the ranking algorithm that selects which observing session to schedule next, and simulations that compare dynamic scheduling with traditional GBT scheduling. We rank observing sessions as a product of many factors. Some are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. The simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
>
>

  • Title: The GBT Dynamic Scheduling System: Algorithms, Metrics, and Simulations
  • Abstract: We discuss the ranking algorithm of the new Green Bank Telescope (GBT) Dynamic Scheduling System. Since the GBT is located in a continental, mid-latitude region where weather is dominated by water vapor and small-scale effects, the weather plays an important role in optimizing the observing efficiency of the GBT. We rank observing sessions as a product of many factors. Some factors are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. Simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.

 <<O>>  Difference Topic ADASS2008 (r1.15 - 06 Aug 2008 - MarkClark)
Added:
>
>

Scheduling Probabilities - Mark

  • Title: The GBT Dynamic Scheduling System: Handling Observer's Expectations under Dynamic Scheduling: Providing Likelihoods of Getting Telescope Time Beyond Available Weather Forecasts - I hate the phrase "of Getting Telescope Time", anything better? How about "scheduling sessions" or "scheduling projects"
  • Abstract:
  • Sections:
    • short term: using relative scoring
      • "qualifying" sessions
      • measurements
        • raw scores
        • rankings
        • percentiles
    • long term: using historical simulations
      • weather history
      • administrative constraints

 <<O>>  Difference Topic ADASS2008 (r1.14 - 06 Aug 2008 - PaulMarganian)
Changed:
<
<

  • Abstract: The web technologies utilized for the new Green Bank Telescope (GBT) Dynamic Scheduling System are discussed, focusing on languages, frameworks, and tools. We use a popular Python web framework, TurboGears?, to leverage the extensive web services the system provides. TurboGears? is a model-view-controller framework, which aggregates SQLAlchemy, CherryPy?, and
Genshi respectively. On top of this framework, Javascript (Prototype, script.aculo.us) and cascading style sheets (Blueprint) are used fordesktop-quality web pages. It Rocks.
>
>

  • Abstract: The web technologies utilized for the new Green Bank Telescope (GBT) Dynamic
Scheduling System (see poster?) are discussed, focusing on languages, frameworks, and tools. We use a popular Python web framework, TurboGears?, to leverage the extensive web services the system provides. TurboGears? is a model-view-controller framework, which aggregates SQLAlchemy, Genshi, and CherryPy? respectively. On top of this framework, Javascript (Prototype, script.aculo.us) and cascading style sheets (Blueprint) are used for desktop-quality web pages. It Rocks.
Deleted:
<
<

Agile Software Development applied to the DSS - Mark

  • Title: The GBT Dynamic Scheduling System: Agile Software Development

I was checking out the ADASS page, and one of the 4 themes for the year is 'Software engineering in Astronomy'. What do you think? (PRM)


 <<O>>  Difference Topic ADASS2008 (r1.13 - 06 Aug 2008 - KarenONeil)
Changed:
<
<

  • Title: A New Dynamic Scheduling Paradigm for the GBT
>
>

  • Title: The GBT Dynamic Scheduling System: A New Scheduling Paradigm
Changed:
<
<

  • Title: GBT Scheduling Algorithms: Application of the Knapsack Problem and Sudoku
>
>

  • Title: The GBT Dynamic Scheduling System: Scheduling Applications of the Knapsack Problem and Sudoku
Changed:
<
<

  • Abstract:
>
>

  • Abstract: The web technologies utilized for the new Green Bank Telescope (GBT) Dynamic Scheduling System are discussed, focusing on languages, frameworks, and tools. We use a popular Python web framework, TurboGears?, to leverage the extensive web services the system provides. TurboGears? is a model-view-controller framework, which aggregates SQLAlchemy, CherryPy?, and
Genshi respectively. On top of this framework, Javascript (Prototype, script.aculo.us) and cascading style sheets (Blueprint) are used fordesktop-quality web pages. It Rocks.
Changed:
<
<

  • Title: The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Observers' Perspective
>
>

  • Title: The Green Bank Telescope Dynamic Scheduling System: Results from Beta Tests - The Observers' Perspective
Added:
>
>

Changed:
<
<

  • Scheduling notification (email, rss feeds, etc)
>
>

  • Scheduling notification (email, rss feeds, etc) and how well they all worked
Changed:
<
<

  • Title: The GBT Dynamic Scheduling System Beta Tests: Scheduling Observers
>
>

  • Title: The GBT Dynamic Scheduling System: Results from Beta Tests - The Development Team's Perspective
Added:
>
>

  • Title: The GBT Dynamic Scheduling System: Agile Software Development
Deleted:
<
<

The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Engineering Perspective - Mike?

  • Title: The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Engineering Perspective
  • Abstract:

  • Sections:
    • Intro to the tests

Changed:
<
<

  • Title: The Green Bank Telescope Dynamic Scheduling System: An Overview
>
>

  • Title: The GBT Dynamic Scheduling System: An Overview

 <<O>>  Difference Topic ADASS2008 (r1.12 - 01 Aug 2008 - MikeMcCarty)
Added:
>
>

During the summer trimester of 2008 (June 1 - September 20, 2008) all observations on the Green Bank Telescope (GBT) were scheduled using the new Dynamic Scheduling System (DSS). These Beta tests exercised the policies, algorithms, and software developed for the DSS project. We will discuss the experience of using the DSS to schedule observers covering the daily process of creating a schedule, notifying observers of events, managing project information, and rescheduling due to unexpected circumstances. We also relate the software engineer's experience of using agile development practices to implement the DSS. We then identify lessons learned from the Beta tests and present conclusions.

Added:
>
>


 <<O>>  Difference Topic ADASS2008 (r1.11 - 31 Jul 2008 - JulesHarnett)
Changed:
<
<

  • Title:
>
>

  • Title: The Green Bank Telescope Dynamic Scheduling System: An Overview
Added:
>
>

The new Green Bank Telescope (GBT) Dynamic Scheduling System(DSS) aims to maximize the observing efficiency of the telescope, while maintaining its signal characteristics: data quality, ease of use and flexibility. Observations are schedules on the basis of weather, sky coordinates, radio-frequency interference (RFI) and other local parameters (constraints?). Observing projects are divided into a number of possible observing sessions, which may be classified Fixed, Open or Windowed. Observers may elect to be available at all times; ie they can be called upon with no notice to use an Telescope Period (TP) which has become available because of changes in local conditions, eg a sudden change in the weather. Alternately, they can elect to observe with 24-hours notice (the regular decision) or can black themselves out for time when they cannot observe. The Scheduling algorithm then uses all such data to determine the most efficient schedule for the GBT over the following 24-hours. This poster presents an overview of the GBT DSS including the ranking and scheduling algorithms for TPs, scheduling probabilities generation, the web framework for the system, and a summary of the beta tests which were held in the from June - September, 2008

Deleted:
<
<

    • Poster will be a condensed version of the overview talk

 <<O>>  Difference Topic ADASS2008 (r1.10 - 31 Jul 2008 - KarenONeil)
Changed:
<
<

  1. Can one person give more then one poster, as first author? No
  2. we have too many talks/posters/demos. We need to eliminate a few things. (We can handle only 7 individual "things");
>
>

  1. All titles should start with "The GBT Dynamic Scheduling System:..."
Deleted:
<
<

Scheduling Probabilities - Mark

  • Title: Handling Observer's Expectations under Dynamic Scheduling: Providing Likelihoods of Getting Telescope Time Beyond Available Weather Forecasts - I hate the phrase "of Getting Telescope Time", anything better? How about "scheduling sessions" or "scheduling projects"
  • Sections:
    • short term: using relative scoring
    • long term: using historical simulations
  • Abstract:
Changed:
<
<

Observer's Perspective - Jim and Jules

>
>

Observer's Perspective - Jim

Changed:
<
<

Scheduler's Perspective - Mike

>
>

Include the scheduling probabilities in this

Teams's Perspective - Mike

Changed:
<
<

Is this worth a whole poster, or could it be part of a poster on the software end of the beta tests?

>
>

All the stuff from the beta tests except obs perspective

  • The scheduler's perspective
  • The software engineer's perspective
  • Lessons Learned
  • Conclusions - how efficient were we?
Changed:
<
<

Agile Software Development applied to the DSS

>
>

Agile Software Development applied to the DSS - Mark

Deleted:
<
<

    • The scheduler's perspective
    • The software engineer's perspective
    • Lessons Learned
    • Conclusions - how efficient were we?
Changed:
<
<

Demo - ??

>
>

Demo/Overview - Jules


 <<O>>  Difference Topic ADASS2008 (r1.9 - 31 Jul 2008 - KarenONeil)
Changed:
<
<

  1. Can one person give more then one poster, as first author?
  2. Is Eric going?
>
>

  1. Can one person give more then one poster, as first author? No
  2. we have too many talks/posters/demos. We need to eliminate a few things. (We can handle only 7 individual "things");
Changed:
<
<

  • Abstract:
>
>

  • Abstract: The Robert C. Byrd Green Bank Telescope (GBT) is implementing a new Dynamic Scheduling System (DSS)designed to maximize the observing efficiency of the telescope while ensuring that none of the flexibility and ease of use of the GBT is harmed and the data quality of observations is not adversely affected. To accomplish this, the GBT DSS is implementing a dynamic scheduling systems which schedules observers, rather than running scripts. The DSS works by breaking each project into one or more sessions which have associated observing criteria such as RA, Dec, frequency, etc. Potential observers may also enter dates when members of their team will not be available for either on-site or remote observing. The scheduling algorithm uses those data, along with the predicted weather, to determine the most efficient schedule for the GBT. The DSS provides all observers at least 24 hours notice of their upcoming observing. In the uncommon (< 20%) case where the predictions do not match the actual weather, a backup project, chosen from the database, will be run instead. Here we give an overview of the GBT DSS project, including the ranking and scheduling algorithms for the sessions, the scheduling probabilities generation, the web framework for the system, and an overview of the results from the beta tests which were held in the from June - September, 2008.
Changed:
<
<

  • Abstract: The GBT dynamic scheduling method is discussed, including the ranking algorithm that selects which observing session to schedule next, and simulations that compare dynamic scheduling with traditional GBT scheduling. We rank observing sessions as a product of many factors. Some are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. The simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
>
>

  • Abstract: The new Green Bank Telescope (GBT) dynamic scheduling method is discussed, including the ranking algorithm that selects which observing session to schedule next, and simulations that compare dynamic scheduling with traditional GBT scheduling. We rank observing sessions as a product of many factors. Some are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. The simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.
Added:
>
>

Changed:
<
<

  • Title: Handling Observer's Expectations under Dynamic Scheduling: Providing Likelihoods of Getting Telescope Time Beyond Available Weather Forecasts - I hate the phrase "of Getting Telescope Time", anything better?
>
>

  • Title: Handling Observer's Expectations under Dynamic Scheduling: Providing Likelihoods of Getting Telescope Time Beyond Available Weather Forecasts - I hate the phrase "of Getting Telescope Time", anything better? How about "scheduling sessions" or "scheduling projects"
Added:
>
>

Added:
>
>

Changed:
<
<

  • Title: The Green Bank Telescope Dynamic Scheduling System: The Observers' Perspective
>
>

  • Title: The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Observers' Perspective
Added:
>
>

I think this should be more about how things work from an observer's perspective. E.g. something like:

  • An observer's introduction to the GBT DSS
  • Entering (and changing) your session information
  • Scheduling notification (email, rss feeds, etc)
  • Problems and issues
  • A look to the future (ease of use)
Changed:
<
<

  • Title: Using the Dynamic Scheduling System: Scheduling Observers
>
>

  • Title: The GBT Dynamic Scheduling System Beta Tests: Scheduling Observers
Added:
>
>

Is this worth a whole poster, or could it be part of a poster on the software end of the beta tests?

Changed:
<
<

08B Test Results -

  • Title:
>
>

The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Engineering Perspective - Mike?

  • Title: The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Engineering Perspective
Added:
>
>

  • Sections:
    • Intro to the tests
    • The scheduler's perspective
    • The software engineer's perspective
    • Lessons Learned
    • Conclusions - how efficient were we?
Changed:
<
<

Demo

>
>

Demo - ??


 <<O>>  Difference Topic ADASS2008 (r1.8 - 24 Jul 2008 - MarkClark)
Changed:
<
<

Scheduling Algorithms - All Software (Lead author?)

>
>

Scheduling Algorithms - Eric

Added:
>
>

    • Sudoku
      • Game - picture
      • Windowed sessions - picture
      • Diagnostics
        • Conflicts
        • Knots
        • Run-time constraints

 <<O>>  Difference Topic ADASS2008 (r1.7 - 14 Jul 2008 - JimBraatz)
Changed:
<
<

  • Title:
>
>

  • Title: The Green Bank Telescope Dynamic Scheduling System: The Observers' Perspective
Added:
>
>

To make the most efficient use of telescope time, the NRAO is implementing a Dynamic Scheduling System (DSS) for the Green Bank Telescope (GBT). The DSS aims to match observing projects to the existing weather and other observing conditions, without sacrificing observers' interactive control of their experiments. To meet this goal, the DSS schedules not observing scripts but rather blocks of time during which an observer can attend to the observation and control the telescope, often from a remote location. The DSS generates a new schedule every day, for the 24-hour period beginning one day hence. Observers therefore must be prepared to run observations with 24 - 48 hours notice. Being available and ready to observe on short notice requires observers to adopt a mindset and set of practices unlike their experiences with other telescopes. While these may be an inconvenience for some, the benefits are substantial, the primary one being astronomers are almost assured of observing in appropriate weather and getting high quality data. While observers should expect to be "on the ready" at all times, the DSS does give them the opportunity to black-out time ranges to avoid for scheduling. In addition to the scheduling algorithms, the DSS team has developed a set of software tools to help observers manage scheduling their projects, to notify observers of scheduling news, and to help observers anticipate when their projects will make the schedule. In this contribution we will relate observers' experiences from the first tests of the GBT DSS, which took place from June 1 - September 30, 2008.


 <<O>>  Difference Topic ADASS2008 (r1.6 - 10 Jul 2008 - DanaBalser)
Added:
>
>

Changed:
<
<

  • Title:
  • Abstract:
>
>

  • Title: GBT Dynamic Scheduling System: Algorithms, Metrics, and Simulations
  • Abstract: The GBT dynamic scheduling method is discussed, including the ranking algorithm that selects which observing session to schedule next, and simulations that compare dynamic scheduling with traditional GBT scheduling. We rank observing sessions as a product of many factors. Some are continuous functions intended to maximize the scientific output of the GBT. Several factors are binary limits taking values of 0 or 1, any one of which can eliminate a candidate session by forcing the rank to zero. Others reflect management decisions to expedite observations by visiting observers, ensure the timely completion of projects, etc. The simulations indicate that dynamic scheduling can increase the effective observing time at frequencies higher than 10 GHz by about 50% over one full year.

 <<O>>  Difference Topic ADASS2008 (r1.5 - 10 Jul 2008 - PaulMarganian)
Added:
>
>

Agile Software Development applied to the DSS

I was checking out the ADASS page, and one of the 4 themes for the year is 'Software engineering in Astronomy'. What do you think? (PRM)


 <<O>>  Difference Topic ADASS2008 (r1.4 - 09 Jul 2008 - KarenONeil)
Changed:
<
<

Overview Talk

>
>

A few notes:

  1. Can one person give more then one poster, as first author?
  2. Is Eric going?



Ov