Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1440

Further elaboration of LOW station model simulations

Details

    • Enabler
    • Not Assigned
    • PI9
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      The aim is to bring the SKA-LOW receive path model to a point at which it enables us to answer questions that have a material design impact, such as:

      • Do we need to do direct delay measurement?
      • What compute capacity in MCCS do we need?
      • What is the max gain variation allowed for the performance of the laser diode?
      Show
      The aim is to bring the SKA-LOW receive path model to a point at which it enables us to answer questions that have a material design impact, such as: Do we need to do direct delay measurement? What compute capacity in MCCS do we need? What is the max gain variation allowed for the performance of the laser diode?
    • Hide
      • Model parameters loaded with production data
      • Set of predicted complex gain curves for a limited set of frequency and temperature (realistic) conditions.
      • Comparison of predicted delay over frequency with measured delay over frequency (from AAVS data).
      • Short report that summarises finding with regards to temperature stability - what are the dominant contributors (both intra-station and inter-station).
      • Prioritised list of test cases to answer specific design questions, for future work.
      Show
      Model parameters loaded with production data Set of predicted complex gain curves for a limited set of frequency and temperature (realistic) conditions. Comparison of predicted delay over frequency with measured delay over frequency (from AAVS data). Short report that summarises finding with regards to temperature stability - what are the dominant contributors (both intra-station and inter-station). Prioritised list of test cases to answer specific design questions, for future work.
    • 2
    • 2
    • 30
    • Team_SCHAAP
    • Sprint 5
    • Hide
      Show
      the model (available via the SKA repo at https://gitlab.com/ska-telescope/sim/ska-sim-low/-/tree/master/matlab ) has been updated to work with measured temperature curves and set component tolerances based on s-parameter measurements when available. the Confluence page describing the model ( https://confluence.skatelescope.org/display/TDT/Signal+Chain+Behavioural+Modeling ) has been updated accordingly. the aforementioned Confluence page includes an assessment of the key contributors to the static and dynamic behaviour of the receive path gains. priorities for the next PI will be discussed on Thursday, February 25.
    • 12.1
    • Stories Completed, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria
    • PI22 - UNCOVERED

    Description

      Timeboxed activity to continue work done for SP-1203 (described in the demo found here: https://confluence.skatelescope.org/display/SE/2020-11-11+DP+ART+System+Demo+8.5) 

      This is an Exploration Enabler to further improve our understanding of LOW Calibration and stability requirements. This is an interaction between array-level calibration and station level calibration required for two different operating modes: 

      1. Imaging
      2. Tied-array beamforming

      Also, see discussion at https://confluence.skatelescope.org/display/TDT/Questions+to+address+using+signal+chain+model

       


       

      Notes (from Daniel Hayden, slightly edited by Ben Mort):

      We need to know how big the gain variations at station level can be before it results in:

      • Unacceptable imaging performance and,
      • Unacceptable tied array beam performance.

      We're interested in the effect of both

      • the variation of the mean complex gain itself and,
      • the variation of complex gains of individual receive paths with respect to the mean.

      Although AAVS results seem to suggest we don't need direct delay measurement for every signal chain in a station, we should confirm this intuition quantitatively. 

      There are two steps:

      1. Complete development of Stefan's model for a single station. Remaining steps here are input realistic values for production tolerances and temperature data. The model should be able to show the effect of both variations within a station and variation between stations.
      2. To feed this model's output as input to an array level simulation.

      The first step at minimum is a good candidate for a PI9 Feature.

      Possible stretch goals:

      • Produce a Python version of the model.
      • Do we want to model with a full set of individual EEPs in OSKAR?

      Notes from meeting 3 Dec 2020 to scope Feature

      1: validate model using INAF production data compared to (e.g. AAVS) behaviour.

      2: using model with realistic temperature curves determine expected variability due to temperature.

      We want to understand variation 'between' stations as well, and what the big contributors to this are. 

      Prove that can be put into the array model, but analysis not needed.

      Prioritised list of test cases to answer specific questions, as input for next PI.

      Dependency with Curtin (Marcin?) and INAF? to help with validation of model?

      Acceptance criteria

      • Model parameters loaded with production data
      • Set of predicted complex gain curves for a limited set of frequency and temperature (realistic) conditions.
      • Comparison of predicted delay over frequency with measured delay over frequency (from AAVS data).
      • Short report that summarises finding with regards to temperature stability - what are the dominant contributors (both intra-station and inter-station).
      • Prioritised list of test cases to answer specific design questions, for future work.

      Attachments

        Issue Links

          Structure

            Activity

              People

                d.hayden Hayden, Daniel
                s.wijnholds Stefan Wijnholds
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete47.0
                  Total47.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel