Merge branch 'SW-919' into 'master'

SW-919: Changed svn.astron.nl to git.astron.nl for code reference and checkout...

Closes SW-919

See merge request !163

CEP/Pipeline/helper_scripts/pipeline_commisioning.txt

@@ -12,12 +12,13 @@
 
 # *****************************************************************************
 # 1. Prepare the directories and build for doing pipeline runs
-# a. Checkout the current branch:
-#    Username and password of the svn are: lofar-guest and lofar-guest
-mkdir ~/source/7058 -p
-cd ~/source/7058
-# this might take some time:
-svn export --ignore-externals  https://svn.astron.nl/LOFAR/branches/CEP-Pipeline-Task7058 LOFAR
+# a. Clone and Checkout a ´Pipeline´ branch, e.g. 7058:
+mkdir ~/source
+cd ~/source
+# this might take some time (if clone has not not before, otherwise this step can be skipped):
+git clone https://git.astron.nl/ro/lofar.git
+cd lofar
+git checkout 7058
 
 # b. build the pipeline framework and needed executables:
 # CMake collects information about the environment and creates a make file

Docker/lofar-documentation/lofar_documentation.md

@@ -40,7 +40,7 @@ steps for every change in the Dockerfile that is related to e.g. the building pr
 
 ### Source Code
 
-The Docker file and its dependencies (if their license allows it) can be found in SVN folder:
+The Docker file and its dependencies (if their license allows it) can be found in folder:
 
     Docker/lofar-documentation
 

INSTALL

@@ -103,12 +103,14 @@ NOTE (any OS): For manual builds, the most prominent dependencies you may need t
 Instructions for Manual Build from Source
 -----------------------------------------
 
-- SVN checkout build and configuration scripts of a tagged release x.y.z (or the
-  trunk) from https://svn.astron.nl/LOFAR/ into e.g. $HOME/src/LOFAR-x.y.z/
+- Git Clone and checkout build and configuration scripts of a particular branch e.g. LOFAR-xyz
+  from https://git.astron.nl/ into local working directory e.g. $HOME/my_source_folder
 
+    git clone https://git.astron.nl/ro/lofar.git $HOME/my_source_folder
+    cd $HOME/my_source_folder
+    git checkout LOFAR-xyz
+  Assume you want to put the build results in a separate build folder which you call a release, e.g.
 	LOFAR_RELEASE=LOFAR-Release-x.y.z  # set to used release version
-	svn checkout --depth=files "https://svn.astron.nl/LOFAR/tags/$LOFAR_RELEASE" "$HOME/src/$LOFAR_RELEASE"
-	svn update --depth=infinity "$HOME/src/$LOFAR_RELEASE/CMake"
 
 - Auto-checkout and install the usual offline data reduction (imaging) packages
   into e.g. $HOME/local/$LOFAR_RELEASE/
@@ -116,7 +118,7 @@ Instructions for Manual Build from Source
 
 	mkdir -p $HOME/build/$LOFAR_RELEASE/gnu_opt  # last directory must be {gnu|clang}[cxx11]_{debug|opt}
 	cd $HOME/build/$LOFAR_RELEASE/gnu_opt
-	cmake -DCMAKE_INSTALL_PREFIX="$HOME/local/$LOFAR_RELEASE" -DBUILD_PACKAGES="DP3 Calibration Imager PyBDSM" -DUSE_OPENMP=ON "$HOME/src/$LOFAR_RELEASE"
+	cmake -DCMAKE_INSTALL_PREFIX="$HOME/local/$LOFAR_RELEASE" -DBUILD_PACKAGES="DP3 Calibration Imager PyBDSM" -DUSE_OPENMP=ON "$HOME/my_source_folder/$LOFAR_RELEASE"
 
 - Build and install:
 

LCS/Messaging/doc/Messaging.md

@@ -35,7 +35,7 @@ The `libmessaging.so` library is used by the following modules:
 *TODO*
 
 ### Source Code
-[LCS/Messaging](https://svn.astron.nl/LOFAR/trunk/LCS/Messaging)
+[LCS/Messaging](https://git.astron.nl/ro/lofar/-/tree/master/LCS/Messaging)
 
 ### Testing
 - *How do you run unit tests?*

LCS/WinCCWrapper/doc/winccwrapper.md

@@ -45,7 +45,7 @@ Because we needed to have the same API available in python as well, we decided t
 No fancy design needed. This is just a library with a few classes wrapping the complicated WinCC_OA API into a simple API.
 
 ### Source Code
-- [WinCCWrapper in SVN](https://svn.astron.nl/LOFAR/branches/SW-26_WinCC/LCS/WinCCWrapper)
+- [WinCCWrapper in Git](https://git.astron.nl/ro/lofar/-/tree/master/LCS/WinCCWrapper) 
 - [WinCCWrapper Code Documentation](@ref winccwrapper_overview)
 
 ### Testing
@@ -65,8 +65,9 @@ Dependencies on other libraries are automatically found by cmake, and otherwise
 
 ##### Build locally
 
-    svn co https://svn.astron.nl/LOFAR/<some_branch_or_trunk> <my_source_dir>
+    git clone https://git.astron.nl/ro/lofar.git <my_source_dir>
     cd <my_source_dir>
+    git checkout <some_created_branch>
     mkdir -p build/gnu_cxx11debug
     cd build/gnu_cxx11debug
     cmake -DBUILD_PACKAGES=WinCCWrapper -DUSE_LOG4CPLUS=OFF -DCMAKE_INSTALL_PREFIX=/opt/lofar/ ../..

LTA/LTAIngest/doc/lta_ingest.md

@@ -153,7 +153,7 @@ meetings with stakeholders.*
 *Add technical considerations and design choices here*
 
 ### Source Code
-- [LTA Ingest in SVN](https://svn.astron.nl/LOFAR/trunk/LTA/LTAIngest/)
+- [LTA Ingest in Git](https://git.astron.nl/ro/lofar/-/tree/master/LTA/LTAIngest/)
 - [LTA Ingest Source Code Documentation](@ref LTA)
 
 ### Testing
@@ -182,8 +182,9 @@ tests (see below).
 
 ##### Build locally
 
-    svn co https://svn.astron.nl/LOFAR/<some_branch_or_trunk> <my_source_dir>
+    git clone https://git.astron.nl/ro/lofar.git <my_source_dir>
     cd <my_source_dir>
+    git checkout <some_created_branch>
     mkdir -p build/gnu_debug
     cd build/gnu_debug
     cmake -DBUILD_PACKAGES=LTAIngest -DCMAKE_INSTALL_PREFIX=/opt/lofar/ ../..

LTA/ltastorageoverview/doc/lta_storage_overview.md

@@ -53,7 +53,7 @@ Before this package ltastorageoverview existed, we generated similar overviews u
 - Website can be simple (and slow) for now, so in this first phase we chose python flask.
 
 ### Source Code
-- [LTA Storage Overview in SVN](https://svn.astron.nl/LOFAR/trunk/LTA/ltastorageoverview/)
+- [LTA Storage Overview in Git](https://git.astron.nl/ro/lofar/-/tree/master/LTA/ltastorageoverview/)
 - [LTA Storage Overview Code Documentation](@ref lta_storage_overview)
 
 ### Testing
@@ -78,8 +78,9 @@ The 2 services work on the same (shared) database, so there is some integration
 
 ##### Build locally
 
-    svn co https://svn.astron.nl/LOFAR/<some_branch_or_trunk> <my_source_dir>
+    git clone https://git.astron.nl/ro/lofar.git <my_source_dir>
     cd <my_source_dir>
+    git checkout <some_created_branch>
     mkdir -p build/gnu_debug
     cd build/gnu_debug
     cmake -DBUILD_PACKAGES=ltastorageoverview -DCMAKE_INSTALL_PREFIX=/opt/lofar/ ../..

MAC/Deployment/data/OTDB/Component_diff.sh

 #!/bin/bash
 #
 # Script to show the diffs in the component files between two versions of SVN
+# ==> THIS SCRIPT IS OBSOLETE SINCE LOFAR SOURCE TREE IS NOW HOSTED WITH GIT !!!
 #
 # Usage:
 #
@@ -89,6 +90,7 @@ function show_list {
 # MAIN
 #
 
+echo "THIS SCRIPT IS OBSOLETE SINCE LOFAR SOURCE TREE IS NOW HOSTED WITH GIT !!!"
 if [ -z $1 ]; then
     SyntaxError
     exit 1

MAC/WinCCPublisher/doc/winccpublisher.md

@@ -30,7 +30,7 @@ This application builds upon the features provided by the [WinCCWrapper](@ref wi
 This application builds upon and combines features from the WinCCWrapper and Messaging libraries. It uses the connect datapoints feature from the WinCCWrapper, and creates and sends a MonitoringMessage on the messagebus in the datapoint changed callback function.
 
 ### Source Code
-- [WinCCPublisher in SVN](https://svn.astron.nl/LOFAR/branches/SW-26_WinCC/MAC/WinCCPublisher)
+- [WinCCPublisher in Git](https://svn.astron.nl/LOFAR/branches/SW-26_WinCC/MAC/WinCCPublisher) *TODO: Add correct link to (generated?) source code documentation.*
 - [WinCCPublisher Code Documentation](@ref winccpublisher_overview)
 
 ### Testing
@@ -51,8 +51,9 @@ When BUILD_TESTING is ON, then a little test program is built: wincclistener. It
 
 ##### Build locally
 
-    svn co https://svn.astron.nl/LOFAR/<some_branch_or_trunk> <my_source_dir>
+    git clone https://git.astron.nl/ro/lofar.git <my_source_dir>
     cd <my_source_dir>
+    git checkout <some_created_branch>
     mkdir -p build/gnu_cxx11debug
     cd build/gnu_cxx11debug
     cmake -DBUILD_PACKAGES=WinCCPublisher -DUSE_LOG4CPLUS=OFF -DCMAKE_INSTALL_PREFIX=/opt/lofar/ ../..

RTCP/Cobalt/GPUProc/doc/rtcp-usage.txt

@@ -4,11 +4,11 @@ Installation
 
 To build and install Cobalt:
 
-  # check out code from svn (here we assume a trunk-build)
+  # git clone and check out code from git repository (here we assume a master-build)
   ROOT=`pwd`
-  svn co -N https://svn.astron.nl/LOFAR/trunk LOFAR
-  cd $ROOT/LOFAR
-  svn up RTCP CMake LCS
+  git clone https://git.astron.nl/ro/lofar.git
+  cd $ROOT/lofar
+  git checkout master
 
   # Set up a config variants file for your system. This is only needed if
   # packages like casacore and DAL are installed in a non-standard

SAS/MoM/MoMQueryService/MoMQueryServiceClient/doc/MoM_query_service_client.md

@@ -37,9 +37,9 @@ meetings with stakeholders.* TODO
 *Add technical considerations and design choices here* TODO
 
 ### Source Code
-- [source code](https://svn.astron.nl/LOFAR/trunk/SAS/MoM/MoMQueryService/)
-- [source code documentation | MoMQueryRPC](https://svn.astron.nl/lofardoc/SW-90/df/db5/a01158.html)
-- [source code documentation | MoMRPC](https://svn.astron.nl/lofardoc/SW-90/d7/de8/a01159.html)
+- [source code](https://git.astron.nl/ro/lofar/-/tree/master/SAS/MoM/MoMQueryService/)
+- [source code documentation | MoMQueryRPC](https://svn.astron.nl/lofardoc/SW-90/df/db5/a01158.html) *TODO: Add correct link to (generated?) source code documentation.*
+- [source code documentation | MoMRPC](https://svn.astron.nl/lofardoc/SW-90/d7/de8/a01159.html) *TODO: Add correct link to (generated?) source code documentation.*
 
 ### Testing
 TODO tests are missing 

SAS/MoM/MoMQueryService/MoMQueryServiceServer/doc/MoM_query_service_server.md

@@ -44,8 +44,8 @@ meetings with stakeholders.* TODO
 *Add technical considerations and design choices here* TODO
 
 ### Source Code
-- [source code](https://svn.astron.nl/LOFAR/trunk/SAS/MoM/MoMQueryService/MoMQueryServiceClient/)
-- [source code documentation](https://svn.astron.nl/lofardoc/SW-90/d5/d55/a04469.html)
+- [source code](https://git.astron.nl/ro/lofar/-/tree/master/SAS/MoM/MoMQueryService/MoMQueryServiceClient/)
+- [source code documentation](https://svn.astron.nl/lofardoc/SW-90/d5/d55/a04469.html) *TODO: Add correct link to (generated?) source code documentation.*
 
 
 

SAS/MoM/MoMQueryService/doc/MoM_query_service.md

@@ -35,7 +35,7 @@ meetings with stakeholders.* TODO
 *Add technical considerations and design choices here* TODO
 
 ### Source Code
-- [source code](https://svn.astron.nl/LOFAR/trunk/SAS/MoM/MoMQueryService/MoMQueryServiceClient/)
+- [source code](https://git.astron.nl/ro/lofar/-/tree/master/SAS/MoM/MoMQueryService/MoMQueryServiceClient/)
 
 
 ### Testing

SAS/OTB/doc/otb.md

@@ -32,7 +32,7 @@ meetings with stakeholders.*
 *Add technical considerations and design choices here*
 
 ### Source Code
-- [Source](https://svn.astron.nl/LOFAR/trunk/SAS/OTB/)
+- [Source](https://git.astron.nl/ro/lofar/-/tree/master/SAS/OTB/)
 - *Add a link to (generated?) source code documentation.*
 
 ### Testing

SAS/OTDB/doc/otdb.md

@@ -30,7 +30,7 @@ meetings with stakeholders.*
 *Add technical considerations and design choices here*
 
 ### Source Code
-- [Source](https://svn.astron.nl/LOFAR/trunk/SAS/OTDB/)
+- [Source](https://git.astron.nl/ro/lofar/-/tree/master/SAS/OTDB/)
 - *Add a link to (generated?) source code documentation.*
 
 ### Testing

SAS/OTDB_Services/doc/OTDB_services.md

@@ -38,7 +38,7 @@ meetings with stakeholders.*
 *Add technical considerations and design choices here*
 
 ### Source Code
-- [Source](https://svn.astron.nl/LOFAR/trunk/SAS/OTDB_Services/)
+- [Source](https://git.astron.nl/ro/lofar/-/tree/master/SAS/OTDB_Services/)
 - *Add a link to (generated?) source code documentation.*
 
 ### Testing

SAS/ResourceAssignment/Common/doc/ra_common.md

@@ -35,8 +35,8 @@ No analyses documentation available.
 The current design of the Specification class comes out of a refactor action. The code comments mentions the wish to add more OO based design to it. The code now does not enforce consistency.
 
 ### Source Code
-- https://svn.astron.nl/viewvc/LOFAR/trunk/SAS/ResourceAssignment/Common/
-- https://svn.astron.nl/lofardoc/trunk/d6/d18/a01925.html
+- https://git.astron.nl/ro/lofar/-/tree/master/SAS/ResourceAssignment/Common/
+- https://svn.astron.nl/lofardoc/trunk/d6/d18/a01925.html *TODO: Add correct link to (generated?) source code documentation.*
 
 ### Testing
 `make test` will run all tests available for Specification class these are all unit tests.

SAS/ResourceAssignment/OTDBtoRATaskStatusPropagator/doc/otdb_to_ra_task_status_propagator.md

@@ -26,7 +26,7 @@ This services originated when we started the [Resource Assignment](@ref resource
 We followed the same design choices as for the other [Resource Assignment](@ref resource_assignment) services: small, communicate via the messagebus, event driven. It makes use of common components like the OTDBBusListener and RARPC.
 
 ### Source Code
-- [Source code in svn trunk](https://svn.astron.nl/LOFAR/trunk/SAS/ResourceAssignment/OTDBtoRATaskStatusPropagator)
+- [Source code in Git](https://git.astron.nl/ro/lofar/-/tree/master/ResourceAssignment/OTDBtoRATaskStatusPropagator)
 - \ref OTDBtoRATaskStatusPropagator Source code documentation
 
 ### Testing
@@ -37,8 +37,9 @@ We followed the same design choices as for the other [Resource Assignment](@ref
 - This package builds as part of the RA_Services subsystem, see [RA Build & Deploy instructions](@ref resource_assignment_build_and_deploy)
 - We use standard Lofar CMake to build this package. Command line build instructions from scratch:
   ```bash
-  svn co https://svn.astron.nl/LOFAR/trunk/
-  cd trunk
+  git clone https://git.astron.nl/ro/lofar.git <my_source_dir>
+  cd <my_source_dir>
+  git checkout <some_created_branch>
   mkdir -p build/gnu_debug
   cd build/gnu_debug
   cmake -DBUILD_PACKAGES="OTDBtoRATaskStatusPropagator" -DUSE_LOG4CPLUS=OFF ../..

SAS/ResourceAssignment/RATaskSpecifiedService/doc/RATaskSpecifiedService.md

@@ -15,7 +15,7 @@
 - Auke Klazema <klazema@astron.nl>
 
 ### Overview
-- Find diagrams (in graphml/odf format) can be found in the [SVN documentation on SAS redesign for responsive telescope](https://svn.astron.nl/LOFAR/trunk//SAS/doc/SAS_redesign_for_responsive_telescope/)
+- Find diagrams (in graphml/odf format) can be found in the [SVN documentation on SAS redesign for responsive telescope](https://git.astron.nl/ro/lofar.git/tree/-/master/SAS/doc/SAS_redesign_for_responsive_telescope/)
 - Find outdated diagrams in png format in the wiki page [resource assigner redesign](https://www.astron.nl/lofarwiki/doku.php?id=rrr:redesign_resource_assignment_system). This service fits in the OTDB Task Watcher in the first diagram, and in the ResourceAssignService of the detailed view. It writes to the lofar.ra.notification bus.
 
 - - -
@@ -30,8 +30,8 @@ meetings with stakeholders.*
 - *todo: Add technical considerations and design choices here*
 
 ### Source Code
-- [Source code](https://svn.astron.nl/LOFAR/trunk/SAS/ResourceAssignment/RATaskSpecifiedService/)
-- [Documentation](https://svn.astron.nl/lofardoc/trunk/) *todo:* fix link
+- [Source code](https://git.astron.nl/ro/lofar/-/tree/master/SAS/ResourceAssignment/RATaskSpecifiedService/)
+- [Documentation](https://svn.astron.nl/lofardoc/trunk/) *TODO: Add correct link to (generated?) source code documentation.*
 
 ### Testing
 - For unit testing run: ctest -V -R tRATaskSpecified

SAS/ResourceAssignment/RAtoOTDBTaskSpecificationPropagator/doc/RAtoOTDBTaskSpecificationPropagator.md

@@ -24,7 +24,7 @@ This services originated when we started the [Resource Assignment](@ref resource
 We followed the same design choices as for the other [Resource Assignment](@ref resource_assignment) services: small, communicate via the messagebus, event driven.
 
 ### Source Code
-- [source code in svn trunk](https://svn.astron.nl/LOFAR/trunk/SAS/ResourceAssignment/RAtoOTDBTaskSpecificationPropagator)
+- [source code in Git](https://git.astron.nl/ro/lofar/-/tree/master/SAS/ResourceAssignment/RAtoOTDBTaskSpecificationPropagator)
 - \ref RAtoOTDBTaskSpecificationPropagator Source code documentation
 
 ### Testing
@@ -46,8 +46,9 @@ We followed the same design choices as for the other [Resource Assignment](@ref
 - This package builds as part of the RA_Services subsystem, see [RA Build & Deploy instructions](@ref resource_assignment_build_and_deploy)
 - We use standard Lofar CMake to build this package. Command line build instructions from scratch:
   ```bash
-  svn co https://svn.astron.nl/LOFAR/trunk/
-  cd trunk
+  git clone https://git.astron.nl/ro/lofar.git <my_source_dir>
+  cd <my_source_dir>
+  git checkout <some_created_branch>
   mkdir -p build/gnu_debug
   cd build/gnu_debug
   cmake -DBUILD_PACKAGES="RAtoOTDBTaskSpecificationPropagator" -DUSE_LOG4CPLUS=OFF ../..