Roadmap

Milestone: LWA-SV Support

15 months late (02/01/16 17:00:00)

10%

Number of tickets:
closed:
1
active:
9
Total:
10

Full support for LWA-SV is slated for LSL version 1.2.0. This will require a number of changes to the existing LSL 1.1.0 branch, including:

  • support for the station itself,
  • support for the new data formats at LWA-SV,
  • support for the new observing modes at LWA-SV, and
  • support for the new MCS metadata formats.

The goal is to make support for LWA-SV seamless in LSL so that it is easy to deal with both stations using common software.

There will also need to be changes to the Commissioning and SessionSchedules? extensions to support the new station. For Commissioning there needs to be new tools to deal with TBF, COR, and DRX8 data. TBF can be based off TBW and DRX8 off DRX. For SessionSchedules? that changes are needed to support generating SDFs for two stations and implementing the correct limits for each.

Milestone: Python 3 Support

5 months late (12/01/16 17:00:00)

0%

Number of tickets:
closed:
0
active:
1
Total:
1

Update LSL to work under Python 3.

There are several simple ways to improve the performance of the more computationally intensive functions in LSL. Some of the ideas are:

  1. Reduce the number of array copies in functions like lsl.correlator.fx.FXMaster()
  2. Change the OpenMP loop structure in lsl.correlator._core so that it performs better with DRX data
  3. Unify the structure of lsl.correlator._core with lsl.correlator._spec

Other things that might change in LSL are:

  1. Switch from the FFTW fftwf_complex type over to the native C type. If this happens it will also hit the pulsar extension.
  2. Decide between using direct memory access for NumPy? data and the various access macros.
Note: See TracRoadmap for help on using the roadmap.