The following is a proposal for discussion.
The firmware group and testing group can make considerable progress with the Dealer/Player software. So, urgent upgrades of the VEGAS Manager are not vital. However, I (RichardPrestage) feel like it would be worthwhile starting this software development as soon as possible. I understand the desire would be to do this in an "agile" fashion, although I think some upfront specification is required. Not necessarily in the following order, I think we need to do the following:
Start a framework of a Coherent Pulsar Backend within the VEGAS Manager
Specify what additional parameters will be required in the Manager. As far as possible, these should be existing parameters, but we may need new ones. Hopefully, this would largely be a matter of mapping guppi.xx parameters to vegas.xxx parameters
Add these to the VEGAS Coordinator / Manager
Build a fully functioning Manager, utilizing DIBAS HPC software and PSRFITS writing threads
Add any required functionality to the config_tool
Test the Manager with the existing BOF files
At a later date, upgrade the Manager to use the Matrix framework
We agreed that this work should start now. Justin will be developing the Manager.
Pulsar modes will be developed on a branch of VEGAS, synced up as necessary.
Ray will add stories in PT as necessary.
MRs will be written to provide requirements.
We agreed at this point to start with the paramaters required for the Manager; config_tool keywords will be addressed later.
Action: Paul to take the lead on an MR describing the required parameters.
"Mode" will become a character string, and use the naming convention discussed earlier.
Action: Richard to resend link to previous discussions.
We agreed that the character strings for the config_tool keyword for the number of channels (e.g. "medium-low") should be deprecated. Interger values (e.g. 512) are currently accepted, and this convention will be used for VPM.
Action: Melinda to find Joe's earlier document on required pulsar parameters.