From fb4af454f17e77e7ea0aa954b738d6b1be41db5e Mon Sep 17 00:00:00 2001
From: Jorrit Schaap <schaap@astron.nl>
Date: Thu, 25 Feb 2021 14:31:18 +0100
Subject: [PATCH] TMSS-528: used moved flys_eye enabled setting
---
SAS/TMSS/backend/src/tmss/tmssapp/subtasks.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/SAS/TMSS/backend/src/tmss/tmssapp/subtasks.py b/SAS/TMSS/backend/src/tmss/tmssapp/subtasks.py
index 7cdd05b3348..c8fe894d96a 100644
--- a/SAS/TMSS/backend/src/tmss/tmssapp/subtasks.py
+++ b/SAS/TMSS/backend/src/tmss/tmssapp/subtasks.py
@@ -239,10 +239,9 @@ def create_observation_subtask_specifications_from_observation_task_blueprint(ta
"stations": task_beamformer['stations'],
"SAPs": saps}
subtask_spec['COBALT']['beamformer']['tab_pipelines'].append(beamformer_pipeline)
- if task_beamformer.get("flys_eye_enabled", False):
+ if task_beamformer['flys_eye'].get("enabled", False):
flyseye_pipeline = {"coherent": task_beamformer["flys eye"]["settings"],
- "stations": task_beamformer['stations'],
- }
+ "stations": task_beamformer['stations']}
subtask_spec['COBALT']['beamformer']['flyseye_pipelines'].append(flyseye_pipeline)
# todo: Clarify if we can add a subbands_selection on the flys eye task spec, to filter down for sap['subbands']
# If I got that correctly, specifying subbands is not really supported later down the chain, so whatever we do here gets ignored anyway?
--
GitLab