VEGAS Pulsar Project Meeting - Sprint Review: 2017 May 1st 2:00 - 3:00pm ET

Present

  • Laura, Jason, Mark, Joe, Ryan, Natalia

Sprint Story Overview

  • VE-226: Continue work on spectral line modes in VPM branch (IN PROGRESS)
  • VE-215: Spectral line regression testing (INCOMPLETE)
  • VE-216: Continue work on Matrix book keeping (IN PROGRESS)
  • VE-227: Continue Manager/Matrix interface work (IN PROGRESS)
  • VE-231: Shared memory bug on dev-test (IN PROGRESS)
  • VE-228: 32-channel BOF files (IN PROGRESS)
  • VE-229: Update existing BOFs with delay register and wrap behavior improvements (IN PROGRESS)
  • VE-222: Upgrade post-processing scripts to handle multi-bank data with overlapping frequency coverage (IN PROGRESS)
  • VE-230: High time resolution modes

Story Details

VE-226: Continue work on spectral line modes in VPM branch

  • Ray not present but Joe reports that he has a manager version with the mode parameter as an enum.

VE-216: Continue work on Matrix book keeping

  • Testing switching book keeping.

VE-227: Continue Manager/Matrix interface work

  • Defined all interactions between manager and matrix.
  • Will allow one to run "classic" HPC or Matrix HPC, which will be helpful for regression testing.

VE-231: Shared memory bug on dev-test

  • Two issues
    • Could not compile due to cfitsio version conflict.
    • Configures for GUPPI shared memory parameters but needs VEGAS version.
    • Both of these should be fairly easy to fix.

VE-228: 32-channel BOF files

  • Randy and Jason a i0800x0032 BOF and emailed Natalia for testing. Randy not present; Jason not sure of status of other modes.

VE-229: Update existing BOFs with delay register and wrap behavior improvements

  • Luke building a c0800x4096 BOF with fixes and a 24-tap PFB.

VE-230: High time resolution modes

  • No updates.

VE-222: Upgrade post-processing scripts to handle multi-bank data with overlapping frequency coverage

  • On hold while Ryan was on vacation. Ryan needs to make sure data from different files are being collected properly using MPI.

VE-215: Spectral line regression testing

  • Waiting on release candidate. Target date for testing is May 4th.

Additional Work

  • Identified hardware for second bank of development environment. Has necessary memory, GPU, and 10-gig card. Not sure where it came from but Dave Woody scrounged it up. Dave and Wolfgang are working on set up and software team can then configure as necessary.
  • Jason also located the additional 10-gig switch, which is curently in the beamformer rack. Beamformer team will be shipping their own within a week or two, at which point this switch will become available.

VEGAS Pulsar Project Meeting - Sprint Planning: 2017 April 3rd 2:00 - 3:00pm ET

Note: The team's "velocity" has been consistent at 11--13 points per sprint. We should aim for 12 points per sprint for planning purposes.

Backlog

  • Prepare a release candidate for the re-based VPM branch that can run spectral line modes as expected
  • Spectral line regression tests of release candidate
  • Various Matrix work
  • Continue work on high time resolution modes
  • 32-channel BOF files
  • BOF file cleanup and improvements
  • Post processing scripts for multi-bank data
  • Fix shared memory bugs in dev-test (related to cfitsio and software versions)

Critical Issues

  • M&C system and regression tests
  • Manager parameters and interface with CLEO
    • This may be close to done on the manager side. Will need to coordinate with Ron to make sure that CLEO has everything it needs to build GUI.

New Stories

  • Joe will continue Matrix work for bookkeeping and FITS writer, as well as LBW spectral line mode work.
    • Will need to pull Ray's changes for mode enums in manager.
    • May be able to start on pulsar modes.
-- RyanLynch - 2017-05-01

This topic: CICADA > VegasPulsarModes > VegasPulsarProjectMeetings2017 > VegasPulsarProjectMeeting2017May01
Topic revision: 2017-05-01, RyanLynch
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding NRAO Public Wiki? Send feedback