Mroda/v5

.github/workflows/auto_approve.yml

@@ -0,0 +1,19 @@
+name: Auto approve
+
+on:
+  workflow_dispatch:
+    inputs: 
+      pullRequestNumber:
+        description: Pull request number to auto-approve
+        required: false
+
+jobs:
+  auto-approve:
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+    steps:
+    - uses: hmarr/auto-approve-action@v2
+      with:
+        github-token: ${{ secrets.GITHUB_TOKEN }}
+        pull-request-number: ${{ github.event.inputs.pullRequestNumber }}

.github/workflows/dunedaq-v4-cpp-ci.yml

@@ -0,0 +1,88 @@
+name: build-develop
+
+# Controls when the action will run. Workflow runs when manually triggered using the UI
+# or API.
+on:
+  push:
+    branches: 
+      - production/v4
+      - patch/*
+      - prep-release/*
+    paths-ignore:
+      - 'docs/**'
+      - '.github/**'
+  pull_request:
+    branches: [ production/v4 ]
+  schedule:
+    - cron: "0 9 * * *"
+
+  workflow_dispatch:
+
+
+jobs:
+  Build_against_dev_release:
+    name: build_against_dev_on_${{ matrix.os_name }}
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        include:
+          - image: "ghcr.io/dune-daq/nightly-release-alma9:production_v4"
+            os_name: "a9"
+    container:
+      image: ${{ matrix.image }}
+    defaults:
+      run:
+        shell: bash
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+    # Runs a single command using the runners shell
+
+    - name: Checkout daq-release
+      uses: actions/checkout@v3
+      with:
+        repository: DUNE-DAQ/daq-release
+        path: daq-release
+
+    - name: setup dev area
+      run: |
+          export REPO=$(echo '${{ github.repository }}' | awk -F '/' '{print $2}')
+          source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh
+          setup_dbt latest_v4 || true
+          release_name="last_fddaq"
+
+          dbt-create -n $release_name dev-${{ matrix.os_name }}
+
+    - name: checkout package for CI
+      uses: actions/checkout@v3
+      with:
+        path: ${{ github.repository }}
+
+    - name: setup build env, build the repo against the development release
+      run: |
+          export REPO=$(echo '${{ github.repository }}' | awk -F '/' '{print $2}')
+          cd $GITHUB_WORKSPACE/dev-${{ matrix.os_name }}
+          source env.sh || true
+
+          spack unload $REPO || true
+          cp -pr $GITHUB_WORKSPACE/DUNE-DAQ/$REPO $GITHUB_WORKSPACE/dev-${{ matrix.os_name }}/sourcecode
+          dbt-build # --unittest # --lint
+
+    - name: upload build log file
+      uses: actions/upload-artifact@v4
+      with:
+        name: build_log_${{ matrix.os_name }}
+        path: ${{ github.workspace }}/dev-${{ matrix.os_name }}/log/build*.log
+
+    # - name: upload linter output file
+    #   uses: actions/upload-artifact@v4
+    #   with:
+    #     name: linting_log_${{ matrix.os_name }}
+    #     path: ${{ github.workspace }}/dev-${{ matrix.os_name }}/log/linting*
+
+    # - name: upload unittest output file
+    #   uses: actions/upload-artifact@v4
+    #   with:
+    #     name: unit_tests_log_${{ matrix.os_name }}
+    #     path: ${{ github.workspace }}/dev-${{ matrix.os_name }}/log/unit_tests*

.github/workflows/track_new_issues.yml

@@ -0,0 +1,40 @@
+name: Add issue to project
+on:
+  issues:
+    types:
+      - opened   
+
+jobs:
+  track_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Get project data
+        env:
+          GITHUB_TOKEN: ${{ secrets.BOT_CI_ISSUES }}
+          ORGANIZATION: DUNE-DAQ
+          PROJECT_NUMBER: 5
+        run: |
+          gh api graphql -f query='
+            query($org: String!, $number: Int!) {
+              organization(login: $org){
+                projectV2(number: $number) {
+                  id
+                }
+              }
+            }' -f org=$ORGANIZATION -F number=$PROJECT_NUMBER > project_data.json
+
+          echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
+
+      - name: Add issue to project
+        env:
+          GITHUB_TOKEN: ${{ secrets.BOT_CI_ISSUES }}
+          ISSUE_ID: ${{ github.event.issue.node_id }}
+        run: |
+          item_id="$( gh api graphql -f query='
+            mutation($project:ID!, $issue:ID!) {
+              addProjectV2ItemById(input: {projectId: $project, contentId: $issue}) {
+                item {
+                  id
+                }
+              }
+            }' -f project=$PROJECT_ID -f issue=$ISSUE_ID --jq '.data.addProjectV2ItemById.item.id')"        

.github/workflows/track_new_prs.yml

@@ -0,0 +1,40 @@
+name: Add pull request to project
+on:
+  pull_request:
+    types:
+      - opened
+jobs:
+  track_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Get project data
+        env:
+          GITHUB_TOKEN: ${{ secrets.BOT_CI_ISSUES }}
+          ORGANIZATION: DUNE-DAQ
+          PROJECT_NUMBER: 5
+        run: |
+          gh api graphql -f query='
+            query($org: String!, $number: Int!) {
+              organization(login: $org){
+                projectV2(number: $number) {
+                  id
+                }
+              }
+            }' -f org=$ORGANIZATION -F number=$PROJECT_NUMBER > project_data.json
+
+          echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
+
+      - name: Add issue to project
+        env:
+          GITHUB_TOKEN: ${{ secrets.BOT_CI_ISSUES }}
+        run: |
+            PR_NUMBER=${{ github.event.pull_request.number }}
+            node_id=`curl -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/${{ github.repository }}/pulls/${PR_NUMBER} | jq '.node_id'`
+            item_id="$( gh api graphql -f query='
+            mutation($project:ID!, $issue:ID!) {
+              addProjectV2ItemById(input: {projectId: $project, contentId: $issue}) {
+                item {
+                  id
+                }
+              }
+            }' -f project=$PROJECT_ID -f issue=$node_id --jq '.data.addProjectV2ItemById.item.id')"    

CMakeLists.txt

@@ -0,0 +1,46 @@
+
+cmake_minimum_required(VERSION 3.12)
+project(daphnemodules VERSION 1.5.0)
+
+find_package(daq-cmake REQUIRED)
+
+daq_setup_environment()
+
+find_package(appmodel REQUIRED)
+find_package(conffwk REQUIRED)
+find_package(appfwk REQUIRED)
+find_package(opmonlib REQUIRED)
+find_package(fmt REQUIRED)
+find_package(Boost COMPONENTS unit_test_framework REQUIRED)
+
+##############################################################################
+
+
+# See https://dune-daq-sw.readthedocs.io/en/latest/packages/daq-cmake/#daq_codegen
+daq_protobuf_codegen( opmon/*.proto )
+
+##############################################################################
+
+
+# See https://dune-daq-sw.readthedocs.io/en/latest/packages/daq-cmake/#daq_add_library
+
+daq_add_library( *.cpp LINK_LIBRARIES appfwk::appfwk fmt::fmt) # Any source files and/or dependent libraries to link in not yet determined
+##############################################################################
+
+
+# See https://dune-daq-sw.readthedocs.io/en/latest/packages/daq-cmake/#daq_add_plugin
+
+daq_add_plugin(DaphneV2ControllerModule duneDAQModule LINK_LIBRARIES daphnemodules appmodel::appmodel)
+
+##############################################################################
+
+
+# See https://dune-daq-sw.readthedocs.io/en/latest/packages/daq-cmake/#daq_add_unit_test
+
+daq_add_unit_test(DaphneInterface_test LINK_LIBRARIES daphnemodules) 
+
+##############################################################################
+# daq_add_application(daphne_controller_test controller_test.cxx TEST LINK_LIBRARIES daphnemodules)
+
+daq_install()
+

cmake/daphnemodulesConfig.cmake.in

@@ -0,0 +1,37 @@
+
+@PACKAGE_INIT@
+
+include(CMakeFindDependencyMacro)
+
+# Insert find_dependency() calls for your package's dependencies in
+# the place of this comment. Make sure they match up with the
+# find_package calls in your package's CMakeLists.txt file
+
+find_package(appmodel)
+find_package(appfwk)
+find_package(opmonlib)
+find_package(fmt)
+find_package(Boost COMPONENTS unit_test_framework)
+
+
+# Figure out whether or not this dependency is an installed package or
+# in repo form
+
+if (EXISTS ${CMAKE_SOURCE_DIR}/@PROJECT_NAME@)
+
+message(STATUS "Project \"@PROJECT_NAME@\" will be treated as repo (found in ${CMAKE_SOURCE_DIR}/@PROJECT_NAME@)")
+add_library(@PROJECT_NAME@::@PROJECT_NAME@ ALIAS @PROJECT_NAME@)
+
+get_filename_component(@PROJECT_NAME@_DAQSHARE "${CMAKE_CURRENT_LIST_FILE}" DIRECTORY)
+
+else()
+
+message(STATUS "Project \"@PROJECT_NAME@\" will be treated as installed package (found in ${CMAKE_CURRENT_LIST_DIR})")
+set_and_check(targets_file ${CMAKE_CURRENT_LIST_DIR}/@[email protected])
+include(${targets_file})
+
+set(@PROJECT_NAME@_DAQSHARE "${CMAKE_CURRENT_LIST_DIR}/../../../share")
+
+endif()
+
+check_required_components(@PROJECT_NAME@)

docs/README.md

@@ -1,48 +1 @@
-/**
-
-@mainpage DAPHNE-libs
-@author Manuel Arroyave (marroyav)
-
-@description This is a collection of libraries to monitor, config and spy daphne registers.  
-All the libraries are based in oei, a class with 4 functions to read and write registers via ETH.  
-
-Basic functionality would support endpoint status.  
-Endpoint_status.hpp seems like the library to test integration since it's only readout  
-and returns feedback about the status of the timing endpoint.  
-
-Stand alone applications:  
-testip.cpp          -------> pings to every daphne board and prints success or fail  
-gateware.cpp        -------> takes ip address and ask for the gateware running on each daphne  
-endpoint_status.cpp -------> prints clk and timing variables on terminal  
-clocks.cpp          -------> execute clk config for all daphne boards. (requires echo after)  
-ts.cpp              -------> Prints 4 consecutive ts from each board  
-select_mode.cpp     -------> Configures all daphnes in default data stream config  
-read20.cpp          -------> Prints 20 words from the spy buffer at the output of the 0 transceiver  
-
-These are based in hpp files with functions to automatize sending commands for specific interfaces  
-
-The Booting procedure for all DAPHNEs in the detector is as follows:
-
-1. Power on
-2. Check ping on IP Address ----> send warnings and set a vector only with pingable IP Addresses
-3. Check firmware version   ----> warning if it's different among the set of running daphnes
-4. Check timing registers   ----> set timing to work with timing interface
-5. Send Echo/Alignment command from timing interface (calls a bash script by hand?)
-6. Check endpoint           ----> send warnings if state is not good to go
-6. Align the AFEs and check ----> send warnings if registers are not 0x3f80
-7. Set analog chain         ----> this process takes some time (~few min)
-8. Fine tunning the offset  ----> we can skip it but It might improve dynamic range in some channels
-
-Calibration:
-
-We might need several (tens of) runs for calibration  
-Procedure is very easy from DAQ point of view:  
-Is it possible to automatize this and scan using one variable of the calibration module?  
-
-1. Configure calibration module
-2. Configure DAPHNE
-3. Lauch run
-4. save metadata (configuration parameters)
-
-*/
-
+# No Official User Documentation Has Been Written Yet (Tue Feb 20 17:12:47 CET 2024)

docs/README_old.md

@@ -0,0 +1,48 @@
+/**
+
+@mainpage DAPHNE-libs
+@author Manuel Arroyave (marroyav)
+
+@description This is a collection of libraries to monitor, config and spy daphne registers.  
+All the libraries are based in oei, a class with 4 functions to read and write registers via ETH.  
+
+Basic functionality would support endpoint status.  
+Endpoint_status.hpp seems like the library to test integration since it's only readout  
+and returns feedback about the status of the timing endpoint.  
+
+Stand alone applications:  
+testip.cpp          -------> pings to every daphne board and prints success or fail  
+gateware.cpp        -------> takes ip address and ask for the gateware running on each daphne  
+endpoint_status.cpp -------> prints clk and timing variables on terminal  
+clocks.cpp          -------> execute clk config for all daphne boards. (requires echo after)  
+ts.cpp              -------> Prints 4 consecutive ts from each board  
+select_mode.cpp     -------> Configures all daphnes in default data stream config  
+read20.cpp          -------> Prints 20 words from the spy buffer at the output of the 0 transceiver  
+
+These are based in hpp files with functions to automatize sending commands for specific interfaces  
+
+The Booting procedure for all DAPHNEs in the detector is as follows:
+
+1. Power on
+2. Check ping on IP Address ----> send warnings and set a vector only with pingable IP Addresses
+3. Check firmware version   ----> warning if it's different among the set of running daphnes
+4. Check timing registers   ----> set timing to work with timing interface
+5. Send Echo/Alignment command from timing interface (calls a bash script by hand?)
+6. Check endpoint           ----> send warnings if state is not good to go
+6. Align the AFEs and check ----> send warnings if registers are not 0x3f80
+7. Set analog chain         ----> this process takes some time (~few min)
+8. Fine tunning the offset  ----> we can skip it but It might improve dynamic range in some channels
+
+Calibration:
+
+We might need several (tens of) runs for calibration  
+Procedure is very easy from DAQ point of view:  
+Is it possible to automatize this and scan using one variable of the calibration module?  
+
+1. Configure calibration module
+2. Configure DAPHNE
+3. Lauch run
+4. save metadata (configuration parameters)
+
+*/
+