Private:atsc meeting minutes

15 June 2010

• Attendees: Cheng, Bassam, Kaushik, Gordon.
• Scribe: Kaushik
• Summary:
  • No need to study dvbsnoop. It does not serve our purpose. Try to Install dvbSAM instead. Try a ghost install and ask for an arrangement from the IT guys.
  • Refer fatcaps source code for help on DeltaT calculation.
  • No need to read data aggregator.

• Tasks and deadlines (for the next 1 week):
• Kaushik:

1. Disable dependencies on libraries so one could compile the source on any machine other than the base station. Once it is possible to compile the source code as such, send an email update.
2. Finish writing the APIs on the transmitter class to access the PSI/SI tables.
3. Integrate xerces. Add a README file for any specific instructions on installing libraries that may be needed for compilation.

• Gordon:

1. Try installing dvbSAM and analyze the ts packets generated to see if the MPE and MPE-FEC sections are generated correctly.
2. Study fatcaps code to find a way to calculate DeltaT.

• Bassam:

1. Work with Kaushik to integrate Burst class with RTP StreamReader.
2. Check out an old version of the code to look for the source of pcapReader or look at the code for mp4Reader.

8 June 2010

• Attendees: Cheng, Som, Kaushik, Gordon.
• Scribe: Kaushik
• Summary:
  • Add the environment set up configurations to the make files to set up the environment.
  • The current code creates a test file and also sends bursts over the modulator. Add a compile flag to turn off the modulator initiation. For the time being the integrated code should generate a test ts file.
  • The test ts file may be tested using the evaluation version of dvbSAM.
  • Document and run unit tests for each module. Update the test cases in the Design document. Integrate all code in the next week.
  • Each PSI/SI table could have multiple packets. The transmitter checks the time stamp to send each packet and then sends the next available table based on time.
  • Try and create valid ts file by next meeting.

• Tasks and deadlines (for the next 1 week):
• Som:

1. Work on code integration with the remaining modules in the base station.
2. Update makefiles to set up the environment. Also create the compile flag to disable modulator initiation.

• Kaushik:

1. Update document with possible unit test cases.
2. Finish integration tasks and then design two APIs in the transmitter class to send PSI/SI tables.

• Gordon:

1. Finish integration tasks.
2. Add unit test cases to the design document.
3. Explore the scheduler to figure how to calculate Delta-T.

2 June 2010

• Attendees: Cheng, Som, Bassam, Kaushik, Gordon.
• Scribe: Kaushik
• Summary:
  • The old PHP GUI does not have provisions for using XML based configuration files.
  • The old testbed does not work with the GUI.
  • Decision about configuration:
    • Configure the base station by manually editing the XML files for now.
    • Load/Save XML file from GUI later.
  • The PSI/SI Table sections should only generate the section files. There is no need to convert the section files to ts files.
  • The PSI/SI module should be able to directly pass the configuration to the Transmitter.
  • The streaming packets received should contain/retain the IP header.
  • The streaming functionality should be the task of the read() function in the BurstReader.
  • FECEncoder code may be verified using Divicatch Analyzer.

• Tasks and deadlines (for the next 1 week):
• Som:

1. Create a separate directory in svn so everyone could submit their code.
2. Work on code integration with the remaining modules in the base station.
3. Help Bassam in integrating the streaming code with the stream reader in the base station.

• Bassam:

1. Store the current implementation of the stream receiver implemented using RTP libraries in a directory on svn for future reference.
2. Implement a stream reader from scratch with no dependency on any RTP libraries. The stream reader should retain the IP Headers.
3. Integrate the stream reader into the read function in BurstReader.

• Kaushik:

1. Finish integrating pack() function with the other tables.
2. Integrate PSI/SI table module with ConfMgr module to read table entries (configuration) from XML files.
3. Investigate how to pass section files directly to the transmitter.

• Gordon:

1. Integrate classes with Som's code.
2. Put some time aside for verifying the FEC encapsulation and the error checking using the analyzer. (To be done after integration)

• All:
• In next week's meeting everyone should have an idea of how to integrate their modules with the base station code.

25 May 2010

• Attendees: Mohamed, Som, Bassam, Kaushik, Gordon.
• Scribe: Kaushik
• Summary:
  • All must keep updating the Wiki page with their notes, summary of work, challenges faced, approaches taken or any other information that may be useful or relevant to the project.
  • All code must be written in C++.
  • All configuration information shall be stored in a single XML file by the Configuration Manager.
  • Whenever a configuration is modified and the new configuration is loaded, it shall also be saved.
  • There shall be separate RTP buffers for each stream and the RTP client shall support streaming from multiple channels.
  • Discuss issues with other team members within the week. Work as a team!

• Tasks and deadlines:
• Som:

1. Complete Configuration Manager. (Deadline: 1 week)
2. Consult Cong to better understand the interaction of the current web interface with the configuration manager.

• Bassam:

1. Finish implementation of StreamReader class in the base station to receive streaming data (support multiple streams) from Darwin and pass it to the BurstReader class for further processing. (Deadline: 1 week)

• Kaushik:

1. Finish developing PSI/SI tables and pack function. (Deadline: 1 week)
2. Write and execute test cases for verification of compliance of PSI/SI tables thus developed with DVB-H standard.

• Gordon:

1. Implement FECHeader class (Deadline: 1 week)

• Overview of Project Plan
  • The base station should be up and running with the new code in three weeks.
  • Week 1 will be spent in finishing the assigned tasks for this week.
  • Week 2 will be spent in code reviews and cross-testing of modules between team members. Gordon will test Bassam's code and vice versa, while Som will test Kaushik's code and vice versa.
  • Week 3 will be spent in integration of the modules and testing the system as a whole.
  • Each module should be well documented and Bassam, Gordon and Kaushik should hand over their module documentation to Som so he can update the current design document with the changes that were introduced in the process of development.

18 May 2010

• Attendees: Mohamed, Som, Bassam, Kaushik, Gordon.
• Scribe: Kaushik

• Summary:
  • All must keep updating the Wiki page with their notes, summary of work, challenges faced, approaches taken or any other information that may be useful or relevant to the project.
  • When developing, it is very important to keep the robustness of the code in mind. The code should also be well documented and maintainable.
  • New directory structure for source code repository (version control) is expected to be ready by next week.
  • Discussed an issue with inserting XML library APIs in ConfMgr's load and saveas methods. Som to investigate further.

• Tasks and deadlines:
• Som:

1. Continue working on the new directory structure (svn structure and design). Document the changes or new additions. (Deadline: 1 week)
2. Continue working on the Configuration Manager. (Deadline: 1 week)
3. Integrate all modules and build them together. (Deadline: 2 weeks)
4. Investigate how the web-interface for the testbed will modify configuration using XML configuration files.

• Bassam:

1. Implement a StreamReader class in the base station to receive streaming data (support multiple streams) from Darwin and pass it to the BurstReader class for further processing. (Deadline: 1 week)
2. Investigate possibility of using suggested RTP library (ORTP) to use for processing streaming data.

• Kaushik:

1. Implement classes for the remaining PSI/SI tables. (Deadline: 1 week)
2. Write and execute test cases for verification of compliance of PSI/SI tables thus developed with DVB-H standard. (Deadline: 1 week)
3. Follow class diagram in the design document and make changes if and when necessary and beneficial.

• Gordon:

1. Study the DVB-H standard and testbed design document to understand the role and requirement of FEC encoding. (Deadline: 1 week)
2. Understand relevant implementation requirements and propose a design for the changes required to make open source FEC library compliant with the DVB-H standard. Keep Cheng in the loop during this activity. (Deadline: 1 week)
3. Start implementation of the decided changes.

11 May 2010

• Attendees: Mohamed, Som, Bassam, Kaushik, Gordon.
• Scribe: Kaushik

• Summary:
  • Important to under stand and retain the big picture of the goal of the project.
  • ChengHsin Hsu to collaborate part-time.
  • Update Wiki page with related documents, links or files that you come across. Do write a brief note about the relevance or take-away of the posting.
  • Try and have the system up and running with the new code for FEC, Streaming and PSI/SI in three weeks.
  • While performing your current set of tasks (for DVB-H project) keep in mind that it is desirable to reuse as much of the current work as possible for the implementation of the ATSC Mobile TV project.
  • Guidelines for posting progress
    • Update your progress by the end of day on every Monday.
    • Write concise but informative notes in your progress summary. For example, mention the test cases when you say "tested communication module."

• Tasks and deadlines:
• Som:

1. Redesign the class hierarchy to align better with the current implementation since the current design is more complicated than the implementation. (Deadline: 2 weeks)

• Bassam:

1. Implement the streaming server using RTP and other related protocols to stream videos to a mobile device in C++. Use available tools and APIs. (Deadline: 2 weeks)

• Kaushik:

1. Implement the generation and packing of each of the PSI and SI tables using the current design document and existing Python source code in C++. (Deadline: 2 weeks)

• Gordon:

1. Implement FEC component of the system using C++. (Deadline: 2 weeks)