| <<O>> Difference Topic ADASS2008 (r1.45 - 23 Sep 2008 - PaulMarganian) |
| Changed: | |
| < < |
|
| > > |
|
| <<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) discussionsRenaissance 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:
|
| > > |
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 ExperiencesBasing 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 TechnologiesThe 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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| <<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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| <<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) |
| <<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: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.25 - 08 Aug 2008 - MikeMcCarty) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.24 - 08 Aug 2008 - KarenONeil) |
| Added: | |
| > > |
|
| Added: | |
| > > |
|
| Added: | |
| > > |
|
| Added: | |
| > > |
|
| Added: | |
| > > |
|
| Changed: | |
| < < |
I think this should be more about how things work from an observer's perspective.
E.g. something like:
|
| > > |
Scheduler's Perspective - Jules
|
| Added: | |
| > > |
|
| Added: | |
| > > |
|
| Changed: | |
| < < |
Demo/Overview - Jules
|
| > > |
Demo
|
| Changed: | |
| < < |
|
| > > | |
| <<O>> Difference Topic ADASS2008 (r1.23 - 07 Aug 2008 - MikeMcCarty) |
| Changed: | |
| < < |
Teams's Perspective - Mike
|
| > > |
Software Engineer's Perspective - Mike
|
| 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
|
| > > | 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: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.20 - 07 Aug 2008 - DanaBalser) |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.19 - 07 Aug 2008 - MarkClark) |
| Changed: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| Added: | |
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.18 - 07 Aug 2008 - JimBraatz) |
| Changed: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.15 - 06 Aug 2008 - MarkClark) |
| Added: | |
| > > |
Scheduling Probabilities - Mark
|
| <<O>> Difference Topic ADASS2008 (r1.14 - 06 Aug 2008 - PaulMarganian) |
| Changed: | |
| < < |
|
| > > |
|
| Deleted: | |
| < < |
Agile Software Development applied to the DSS - Mark
|
| <<O>> Difference Topic ADASS2008 (r1.13 - 06 Aug 2008 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > | |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > |
|
| Deleted: | |
| < < |
The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Engineering Perspective - Mike?
|
| Changed: | |
| < < |
|
| > > |
|
| <<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: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| <<O>> Difference Topic ADASS2008 (r1.10 - 31 Jul 2008 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| Deleted: | |
| < < |
Scheduling Probabilities - Mark
|
| 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
|
| Changed: | |
| < < |
Agile Software Development applied to the DSS |
| > > |
Agile Software Development applied to the DSS - Mark |
| Deleted: | |
| < < |
|
| Changed: | |
| < < |
Demo - ?? |
| > > |
Demo/Overview - Jules |
| <<O>> Difference Topic ADASS2008 (r1.9 - 31 Jul 2008 - KarenONeil) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > | |
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > | |
| Added: | |
| > > | |
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > |
I think this should be more about how things work from an observer's perspective.
E.g. something like:
|
| Changed: | |
| < < |
|
| > > |
|
| 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 -
|
| > > |
The Green Bank Telescope Dynamic Scheduling System Beta Tests: The Engineering Perspective - Mike?
|
| Added: | |
| > > |
|
| Changed: | |
| < < |
Demo |
| > > |
Demo - ?? |
| <<O>> Difference Topic ADASS2008 (r1.8 - 24 Jul 2008 - MarkClark) |
| Changed: | |
| < < |
Scheduling Algorithms - All Software (Lead author?) |
| > > |
Scheduling Algorithms - Eric |
| Added: | |
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.7 - 14 Jul 2008 - JimBraatz) |
| Changed: | |
| < < |
|
| > > |
|
| 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: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic ADASS2008 (r1.5 - 10 Jul 2008 - PaulMarganian) |
| Added: | |
| > > |
Agile Software Development applied to the DSSI 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:
Ov |