CABBScheduler
Posted: Mon May 31, 2010 3:04 pm
Max emailed around some suggestions for the scheduler - I'll repeat those here and follow up with a reply
On 31/05/2010, at 11:44 AM, Maxim Voronkov wrote:
All other comments are related to CABB scheduler. They are not
problems as such, but just improvement suggestions.
I managed to stuff up frequency a couple of times during my green
time observations (but fortunately noticed that something was wrong
quickly enough). Partly this is
because the green time observations were unexpected and I had to
create schedules in rush. However, the following changes to the
scheduler could reduce the
chance of a similar mistake made again.
1. It may be good to give a warning in the velocity to frequency
conversion dialogue window if the current scan does not look like a
program source
(i.e. marked as a calibrator by calcode or scan type is point, etc).
2. It may also be nice to give a warning if the date in the scheduler
is notably different from the current date. This is how I stuffed up
the conversion second time -
I edited the old schedule by adding zooms and the scan happened to
have an old observation date set.
3. Just as a thought, may be we want a more structured approach to
define zoom windows, i.e. not per scan which is the most general way,
but introduce a frequency
configuration page and give some kind of FREQ_ID for each scan in the
schedule. In most cases I expect that people would use 1 setup in
most cases (and
probably up to 3 frequency setups anyway given the overheads). This
approach would help to ensure that calibrators and sources are
observed using the same
setup. Otherwise there is too much scope for error, especially if one
changes the existing schedule.
Cheers,
Max
On 31/05/2010, at 11:44 AM, Maxim Voronkov wrote:
All other comments are related to CABB scheduler. They are not
problems as such, but just improvement suggestions.
I managed to stuff up frequency a couple of times during my green
time observations (but fortunately noticed that something was wrong
quickly enough). Partly this is
because the green time observations were unexpected and I had to
create schedules in rush. However, the following changes to the
scheduler could reduce the
chance of a similar mistake made again.
1. It may be good to give a warning in the velocity to frequency
conversion dialogue window if the current scan does not look like a
program source
(i.e. marked as a calibrator by calcode or scan type is point, etc).
2. It may also be nice to give a warning if the date in the scheduler
is notably different from the current date. This is how I stuffed up
the conversion second time -
I edited the old schedule by adding zooms and the scan happened to
have an old observation date set.
3. Just as a thought, may be we want a more structured approach to
define zoom windows, i.e. not per scan which is the most general way,
but introduce a frequency
configuration page and give some kind of FREQ_ID for each scan in the
schedule. In most cases I expect that people would use 1 setup in
most cases (and
probably up to 3 frequency setups anyway given the overheads). This
approach would help to ensure that calibrators and sources are
observed using the same
setup. Otherwise there is too much scope for error, especially if one
changes the existing schedule.
Cheers,
Max