From 069d09546763a69cbd508245852996d067a28dd5 Mon Sep 17 00:00:00 2001
From: Jan David Mol <mol@astron.nl>
Date: Thu, 18 Jul 2024 10:08:41 +0200
Subject: [PATCH] Updated procedure to add a station to LOFAR

---
 NEWSTATION.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/NEWSTATION.md b/NEWSTATION.md
index 6658e292e..3ba525154 100644
--- a/NEWSTATION.md
+++ b/NEWSTATION.md
@@ -7,3 +7,10 @@ When deploying to a new station, for example CS123, you will need to:
 * `CBD/stations/CS123.json`: Create and populate the station-specific Tango configuration. To generate this from LOFAR1, run `tangostationcontrol/tangostationcontrol/toolkit/generate-cdb-from-lofar1.py -s cs123 -C > CDB/stations/CS123.json`,
 * Upload the CDB files through http://cs123c.control.lofar:4646/ui/jobs/dsconfig@default/dispatch, see the [CDB Readme](CDB/stations/README.md) for the list files.
 * Obtain calibration tables and upload them to MinIO at http://cs123c.control.lofar:9001/browser/caltables/CS123. To generate them from LOFAR1, run `tangostationcontrol/tangostationcontrol/toolkit/generate-caltable-from-lofar1.py -s cs123`.
+
+To integrate it further into LOFAR, you will need to:
+
+* TMSS: Add it to the LOFAR2 station group.
+* COBALT: Update `GPUProc/etc/parset-additions.d/default/StationStreams.parset` to receive the station using `udp+sdp` instead of `udp`.
+* lcs129: Make sure `rpc.service.lofar-cs123.consul` is reachable from `lcs129.control.lofar`.
+* Run an observation to check whether everything is reachable and working.
-- 
GitLab