Behavior with unrecognized antennas #4

Open
opened 4 months ago by marcote · 0 comments
marcote commented 4 months ago

Currently, if the observation has an antenna name that is not recognized, antab_editor crashes. Actually it allows normal interaction until the tab for the given antenna is selected.

It is relatively frequent to have unexpected antenna names but that do not belong to a usual name (hence that should not be in the database), such testing Ib, Ed, Kd, or new testing antennas.

In this sense, could it be possible for antab_editor to generate dummy values (e.g. all DPFU/SEFD/etc = 1 or 0) when the antenna is not recognized and only show a warning pop up indicating the fact?

This would still allow us to verify the provided ANTAB file even in these particular cases, or generate one automatically within antab_editor.

Currently, if the observation has an antenna name that is not recognized, `antab_editor` crashes. Actually it allows normal interaction until the tab for the given antenna is selected. It is relatively frequent to have unexpected antenna names but that do not belong to a usual name (hence that should not be in the database), such testing Ib, Ed, Kd, or new testing antennas. In this sense, could it be possible for `antab_editor` to generate dummy values (e.g. all DPFU/SEFD/etc = 1 or 0) when the antenna is not recognized and only show a warning pop up indicating the fact? This would still allow us to verify the provided ANTAB file even in these particular cases, or generate one automatically within `antab_editor`.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.