How to use the SiGe GN3S Sampler v2 as RF front-end for GNSS-SDR
How to use a cheap DVB-T USB dongle as a RF front-end for navigation
How to observe the internals of the software receiver.
The recommended workflow for creating a new signal processing block is the following:
Write the test for your signal processing block.
Write the test src/test/gnss_block/my_block_test.cc You can find examples of from existing blocks’ tests at src/test/gnss_block/
Add an #include to src/tests/test_main.cc pointing to your test:
Instructions for adding your own processing blocks
Instructions for building the source code
Profiling is a dynamic program analysis that measures the usage of memory, the usage of particular instructions, and frequency and duration of function calls during the execution. It is important for identifying computational bottlenecks, and helps the developers to focus their optimization efforts by spotting the critical sections of code. We suggest the use of a couple of open source tools for software profiling that use different techniques, in the hope of taking advantage of their complementary nature and obtain a better insight about how the code is performing.
How to measure software performace and identify bottlenecks.
For bug reporting, we use the bug tracking system provided by SourceForge. It provides a clear centralized overview and keeps track of bugs, feature requests, solutions and updates, and allows users who find a problem to search for it in the database or submit it if it is not already there. This database is the major component of a bug tracking system, and records facts about known bugs. Facts may include the time a bug was reported, its severity, the erroneous program behavior, and details on how to reproduce the bug; as well as the identity of the person who reported it and any programmers who may be working on fixing it. The bug tracking system support the concept of the life cycle for a bug (open - pending - closed), which is tracked through status assigned to the bug.
Rules and good practices when spotting errors in the source code.
Guidelines for contributing, sending patches, and so on.
Brief description about the internal processes going on when the receiver is running.