JObserve
Release Notes
Updated 2006-Jan-13
© AUI, Inc., Washington, D.C.
|
JObserve: Known Bugs
|
|
Status Codes and What They Mean
|
|
Status
|
Means
|
|
Q
|
Can't repeat it, need more information. Looking into it.
|
|
U
|
Ugly; this is a known problem and it will take some work
to fix it. Might not be fixed in the next release.
|
|
V
|
Verfied; we've seen it too and we're working on it.
|
|
X
|
Has been fixed, shouldn't be present in the next release.
|
|
|
Known Bugs in JObserve 1.7.2
|
|
#
|
Status
|
Description
|
|
1
|
U
|
Changes made to a user default are not being passed on to
scans already using that default. This may be difficult to
fix, but old observe allows this, and it obviously is a
powerful feature that JObserve should offer as well.
|
|
2
|
V
|
In calculating stop times, JObserve can be off by at much as
the integration time + 10 seconds. In case of 60sec
integration on source, the extra time (70sec) can seriously
eat into the following calibrator scan.
|
|
3
|
V
|
When specifying channel selection on the correlator page,
this needs to be done for all IFs, or not at all. When
channel selection is specified for 1 - 3 IFs, the saving
operation hangs and the environment cannot be saved.
Likewise, when reading in observe files with some (but not
all) of the channel selection fields on the //DS card filled
in, the environment cannot be saved. This is even the case
when the channel selection fields contain zeroes.
|
|
4
|
V
|
On the Frequency Calculations page, entering a sky frequency
in the last column does not automatically cause the
appropriate band designation in the first column to be displayed.
|
|
5
|
V
|
When slewing from the overlap region to the south the "move" time
is calculated correctly on the scheduling page, but unless the
wrap is specified explicitly the "duration" may not be correct,
and can result in reduced or no observing time on source.
|
|
|
