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

Enable use of BDA-capable solver

Details

    • Enabler
    • Should have
    • PI11
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      By enabling using BDA-ed visibilities for calibration without expanding the data to full resolution, the solver needs to handle fewer visibilities, thereby saving I/O and, hopefully, processing resources in direction-dependent calibration.

      Show
      By enabling using BDA-ed visibilities for calibration without expanding the data to full resolution, the solver needs to handle fewer visibilities, thereby saving I/O and, hopefully, processing resources in direction-dependent calibration.
    • Hide
      • BDA-ed observed visibilities and BDA-ed model visibilities can be fed to the BDA-capable solver in DP3.
      • A performance comparison is made between the BDA-capable solver and the regular solver (after expansion of the data) based on the same set of BDA-ed visibilities.
      • The results are presented in a demo.
      Show
      BDA-ed observed visibilities and BDA-ed model visibilities can be fed to the BDA-capable solver in DP3. A performance comparison is made between the BDA-capable solver and the regular solver (after expansion of the data) based on the same set of BDA-ed visibilities. The results are presented in a demo.
    • 2
    • 2
    • 7.5
    • Team_SCHAAP
    • Sprint 4
    • Hide
      • BDA-ed measured visibilities and BDA-ed predicted visibilities can be fed to several BDA-enabled direction-dependent gain solvers.
      • This was demonstrated during System Demo 11.5 (see https://confluence.skatelescope.org/display/SE/2021-08-18+DP+ART+System+Demo+11.5 ).
      • Runtime comparison seems to indicate that the BDA-capable solver is slower than the regular solver that works with full resolution data. However, this is not due to the solver but due to the BDA predict as indicated by the timing results added to AST-397. The time actually spent in solving is smaller than in the full-resolution case, so the obvious next step is to improve the BDA predict step.
      Show
      BDA-ed measured visibilities and BDA-ed predicted visibilities can be fed to several BDA-enabled direction-dependent gain solvers. This was demonstrated during System Demo 11.5 (see https://confluence.skatelescope.org/display/SE/2021-08-18+DP+ART+System+Demo+11.5 ). Runtime comparison seems to indicate that the BDA-capable solver is slower than the regular solver that works with full resolution data. However, this is not due to the solver but due to the BDA predict as indicated by the timing results added to AST-397. The time actually spent in solving is smaller than in the full-resolution case, so the obvious next step is to improve the BDA predict step.
    • 14.2
    • Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
    • PI22 - UNCOVERED

    Description

      As a pipeline user, I want to be able to use the BDA-capable solver developed in PI10, so that I can calibrate using BDA-ed data without expanding the data to full resolution.

      Attachments

        Issue Links

          Structure

            Activity

              People

                b.mort Mort, Ben
                s.wijnholds Stefan Wijnholds
                Votes:
                0 Vote for this issue
                Watchers:
                0 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
                  Complete821.0
                  Total821.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel