Actions
Task #3509
closed[ndnrtc-client] Headless client
Start date:
03/04/2016
Due date:
03/11/2016
% Done:
100%
Estimated time:
Description
These are brief requirements for the headless consumer:
- ability to consume audio/video streams this is pretty straightforward. we also should provide a function of writing decoded video to a file (.yuv or argb) which can be later used by producer as well.
- configuration file there’s an example of configuration file (it’s parsed by libconfig++ library). I suggest using it and update if needed. invoking application should be as simple as this: $ ndnrtc-headless -c config.cfg
- statistics gathering ...query statistics and save them to a .stat files. I suggest to make selecting statistics configurable. I.e. somewhere in configuration file we provide a list of which statistics we want the app to track and a file name; and they are gathered in captioned tab-delimited files which will be easy to import in matlab/excel or similar. Should look something like that:
stat { buffer.stat: “buf est, buf tar, buf play”; playback.stat: “skipped no, incomplete, total”; ... }
This should give us enough flexibility to test gathering different sets of metrics to analyze streaming efficiency and troubleshoot faster.
Updated by Peter Gusev over 8 years ago
- Category set to Task
- Assignee set to Peter Gusev
- Priority changed from Normal to High
Updated by Jeff Burke over 8 years ago
- Blocks Feature #3481: Test NDN-RTC performance in Mini-NDN added
Updated by Jeff Burke over 8 years ago
- Blocks Feature #3480: Create simple simulation to assess NFD performance for NDN-RTC type traffic added
Updated by Peter Gusev over 8 years ago
- Subject changed from [ndnrtc-client] Headless consumer to [ndnrtc-client] Headless client
- % Done changed from 0 to 60
Updated by Jeff Burke over 8 years ago
- Blocks Feature #3479: Use real NDN-RTC to drive ndnSIM simulation added
Updated by Peter Gusev about 8 years ago
- Status changed from New to Closed
- % Done changed from 60 to 100
Headless client was implemented and can be found in the dev branch of NDN-RTC
Actions