Loading...

Change Owns to Parent Ofs

Set start and due date...

Xporter

XML

Word

Printable

Details

Type: Enabler
Priority: Should have
Fix Version/s: PI11
Component/s: COM SDP SW
Labels:
None

ARTs:

Data Processing
Benefit hypothesis:

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.
Acceptance criteria:
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.
Feature Points:
2
Initial Size:
2
WSJF:
7.5
Epic Link:
SDP Initial workflows
Agile Teams:

Team_SCHAAP
Due Sprint:
Sprint 4
Story Point Burn-up:
Overdue:
Outcomes:
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.
Resolved PI.Sprint:
14.2

Feature Checklist:

Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

Demos:
- DP_ART_11.5
Requirement Status:

PI24 - 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

mentioned in: Page Loading...

Structure

Activity

People

Assignee:: Mort, Ben

Reporter:: Wijnholds, Stefan

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Feature Progress

Story Point Burn-up: (100.00%)

Feature Estimate: 2.0

	Issues	Story Points
To Do	0	0.0
In Progress	0	0.0
Complete	8	21.0
Total	8	21.0

Dates

Created:: 20/May/21 3:20 PM

Updated:: 15/Apr/24 9:48 AM

Resolved:: 01/Apr/22 2:44 PM

Enable use of BDA-capable solver