From d93a3b6c3f0533f9fb4e00eeb4bb9da3cba264cb Mon Sep 17 00:00:00 2001 From: Carles Fernandez Date: Wed, 9 May 2018 20:20:57 +0200 Subject: [PATCH] Switch to https://gnss-sdr.org --- AUTHORS | 37 +-- CONTRIBUTING.md | 12 +- MANIFEST.md | 13 +- README.md | 50 +-- conf/front-end-cal.conf | 35 +-- conf/gnss-sdr.conf | 3 +- ...nss-sdr_GLONASS_L1_CA_GPS_L1_CA_ibyte.conf | 2 +- .../gnss-sdr_GLONASS_L1_CA_GPS_L2C_ibyte.conf | 2 +- conf/gnss-sdr_GLONASS_L1_CA_ibyte.conf | 2 +- .../gnss-sdr_GLONASS_L1_CA_ibyte_coh_trk.conf | 2 +- ...nss-sdr_GLONASS_L2_CA_GPS_L1_CA_ibyte.conf | 2 +- .../gnss-sdr_GLONASS_L2_CA_GPS_L2C_ibyte.conf | 2 +- conf/gnss-sdr_GLONASS_L2_CA_ibyte.conf | 2 +- .../gnss-sdr_GLONASS_L2_CA_ibyte_coh_trk.conf | 2 +- ...gnss-sdr_GPS_L1_2ch_fmcomms2_realtime.conf | 2 +- conf/gnss-sdr_GPS_L1_CA_ibyte.conf | 2 +- conf/gnss-sdr_GPS_L1_FPGA.conf | 3 +- conf/gnss-sdr_GPS_L1_GN3S_realtime.conf | 2 +- conf/gnss-sdr_GPS_L1_LimeSDR.conf | 2 +- conf/gnss-sdr_GPS_L1_SPIR.conf | 4 +- conf/gnss-sdr_GPS_L1_USRP_X300_realtime.conf | 2 +- conf/gnss-sdr_GPS_L1_USRP_realtime.conf | 2 +- conf/gnss-sdr_GPS_L1_acq_QuickSync.conf | 2 +- conf/gnss-sdr_GPS_L1_bladeRF.conf | 2 +- conf/gnss-sdr_GPS_L1_fmcomms2_realtime.conf | 2 +- conf/gnss-sdr_GPS_L1_gr_complex.conf | 2 +- conf/gnss-sdr_GPS_L1_gr_complex_gpu.conf | 2 +- conf/gnss-sdr_GPS_L1_ishort.conf | 2 +- conf/gnss-sdr_GPS_L1_nsr.conf | 2 +- conf/gnss-sdr_GPS_L1_nsr_twobit_packed.conf | 2 +- conf/gnss-sdr_GPS_L1_plutosdr_realtime.conf | 2 +- ...-sdr_GPS_L1_pulse_blanking_gr_complex.conf | 2 +- conf/gnss-sdr_GPS_L1_rtl_tcp_realtime.conf | 2 +- conf/gnss-sdr_GPS_L1_rtlsdr_realtime.conf | 14 +- conf/gnss-sdr_GPS_L1_two_bits_cpx.conf | 2 +- conf/gnss-sdr_GPS_L2C_USRP1_realtime.conf | 2 +- conf/gnss-sdr_GPS_L2C_USRP_X300_realtime.conf | 2 +- ...nss-sdr_Galileo_E1_USRP_X300_realtime.conf | 3 + conf/gnss-sdr_Galileo_E1_acq_QuickSync.conf | 2 +- conf/gnss-sdr_Galileo_E1_ishort.conf | 4 +- conf/gnss-sdr_Galileo_E1_nsr.conf | 2 +- conf/gnss-sdr_Galileo_E5a.conf | 3 + conf/gnss-sdr_Galileo_E5a_IFEN_CTTC.conf | 3 + conf/gnss-sdr_Hybrid_byte.conf | 2 +- conf/gnss-sdr_Hybrid_byte_sim.conf | 2 +- conf/gnss-sdr_Hybrid_gr_complex.conf | 2 +- conf/gnss-sdr_Hybrid_ishort.conf | 2 +- conf/gnss-sdr_Hybrid_nsr.conf | 2 +- ...r_galileo_E1_extended_correlator_byte.conf | 2 +- ...galileo_E1_extended_correlator_labsat.conf | 2 +- ...nnel_GPS_L1_Flexiband_bin_file_III_1a.conf | 2 +- ...nnel_GPS_L1_Flexiband_realtime_III_1a.conf | 4 +- ...nnel_GPS_L1_Flexiband_realtime_III_1b.conf | 4 +- ...annel_GPS_L1_Flexiband_realtime_II_3b.conf | 4 +- ...hannel_GPS_L1_Flexiband_realtime_I_1b.conf | 2 +- ...l_GPS_L1_L2_Flexiband_realtime_III_1b.conf | 2 +- ...Galileo_E1B_Flexiband_bin_file_III_1b.conf | 3 +- ...ultichannel_GPS_L1_USRP_X300_realtime.conf | 2 +- ...el_GPS_L2_M_Flexiband_bin_file_III_1b.conf | 2 +- ...S_L2_M_Flexiband_bin_file_III_1b_real.conf | 4 +- ..._all_in_one_Flexiband_bin_file_III_1b.conf | 2 +- conf/gnss-sdr_multisource_Hybrid_ishort.conf | 2 +- conf/gnss-sdr_multisource_Hybrid_nsr.conf | 4 +- docs/PULL_REQUEST_TEMPLATE.md | 8 +- docs/doxygen/other/main_page.dox | 291 +++++++++--------- docs/manpage/front-end-cal-manpage | 8 +- docs/manpage/gnss-sdr-manpage | 18 +- src/algorithms/PVT/libs/rinex_printer.cc | 36 +-- .../volk_gnsssdr/README.md | 14 +- .../volk_gnsssdr-config-info-manpage | 4 +- .../Packaging/volk_gnsssdr_profile-manpage | 6 +- 71 files changed, 339 insertions(+), 341 deletions(-) diff --git a/AUTHORS b/AUTHORS index 17aa5fa4b..20a6511a7 100644 --- a/AUTHORS +++ b/AUTHORS @@ -1,34 +1,34 @@ GNSS-SDR Authorship ------------------------------------------------------------------------------ -The GNSS-SDR project is hosted and sponsored by the Centre Tecnologic de -Telecomunicacions de Catalunya (CTTC), a non-profit research foundation located -in Castelldefels (40.396764 N, 3.713379 E), 20 km south of Barcelona, Spain. -GNSS-SDR is the by-product of GNSS research conducted at the Communications -Systems Division of CTTC, and it is the combined effort of students, +The GNSS-SDR project is hosted and sponsored by the Centre Tecnologic de +Telecomunicacions de Catalunya (CTTC), a non-profit research foundation located +in Castelldefels (40.396764 N, 3.713379 E), 20 km south of Barcelona, Spain. +GNSS-SDR is the by-product of GNSS research conducted at the Communications +Systems Division of CTTC, and it is the combined effort of students, software engineers and researchers from different institutions around the World. Contact Information ------------------------------------------------------------------------------ - GNSS-SDR Homepage + GNSS-SDR Homepage ---------------------------- - http://gnss-sdr.org - - + https://gnss-sdr.org + + CTTC Homepage ---------------------------- http://www.cttc.cat - - - Mailing Lists + + + Mailing Lists ---------------------------- - gnss-sdr-developers@lists.sourceforge.net + gnss-sdr-developers@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/gnss-sdr-developers - - + + Email ---------------------------- - Inquiries beyond the mailing list can be sent to carles.fernandez@cttc.cat + Inquiries beyond the mailing list can be sent to carles.fernandez@cttc.cat List of authors @@ -40,7 +40,7 @@ Antonio Ramos antonio.ramos@cttc.es Developer Marc Majoral marc.majoral@cttc.cat Developer Pau Closas pau.closas@northeastern.edu Consultant Jordi Vila-Valls jordi.vila@cttc.cat Consultant -Carlos Aviles carlos.avilesr@googlemail.com Contributor +Carlos Aviles carlos.avilesr@googlemail.com Contributor David Pubill david.pubill@cttc.cat Contributor Mara Branzanti mara.branzanti@gmail.com Contributor Marc Molina marc.molina.pena@gmail.com Contributor @@ -54,6 +54,3 @@ Fran Fabra fabra@ice.csic.es Contributor Cillian O'Driscoll cillian.odriscoll@gmail.com Contributor Gabriel Araujo gabriel.araujo.5000@gmail.com Contributor Carlos Paniego carpanie@hotmail.com Artwork - - - diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 262feeb0c..06f37b0a2 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -128,7 +128,7 @@ $ git pull --rebase upstream next ### How to submit a pull request -Before submitting your code, please be sure to [apply clang-format](http://gnss-sdr.org/coding-style/#use-tools-for-automated-code-formatting). +Before submitting your code, please be sure to [apply clang-format](https://gnss-sdr.org/coding-style/#use-tools-for-automated-code-formatting). When the contribution is ready, you can [submit a pull request](https://github.com/gnss-sdr/gnss-sdr/compare/). Head to your @@ -146,24 +146,24 @@ accepted: * Avoid platform-dependent code. If your code require external dependencies, they must be available as packages in [Debian OldStable](https://wiki.debian.org/DebianOldStable). * Write tests. - * Follow our [coding style guide](http://gnss-sdr.org/coding-style/). + * Follow our [coding style guide](https://gnss-sdr.org/coding-style/). * Write a descriptive and detailed summary. Please consider that reviewing pull requests is hard, so include as much information as possible to make your pull request's intent clear. For more details about Git usage, please check out [our -tutorial](http://gnss-sdr.org/docs/tutorials/using-git/). +tutorial](https://gnss-sdr.org/docs/tutorials/using-git/). ## Contributing to the website -The content of http://gnss-sdr.org lives in a GitHub repository at +The content of https://gnss-sdr.org lives in a GitHub repository at https://github.com/gnss-sdr/geniuss-place You can fork that repository, reproduce the entire website on your computer using [Jekyll](https://jekyllrb.com/), do changes and submit pull requests, just as explained above. For more details, please check -out [how to contribute](http://gnss-sdr.org/contribute/). +out [how to contribute](https://gnss-sdr.org/contribute/). Last but not the least, you can leave your comments on the website. @@ -173,6 +173,6 @@ Last but not the least, you can leave your comments on the website. ![GeNiuSS -contributes](http://gnss-sdr.org/assets/images/geniuss-contribute.png) +contributes](https://gnss-sdr.org/assets/images/geniuss-contribute.png) Thanks for your contribution to GNSS-SDR! diff --git a/MANIFEST.md b/MANIFEST.md index 1248e47aa..f78022b17 100644 --- a/MANIFEST.md +++ b/MANIFEST.md @@ -14,13 +14,12 @@ copyright_owner: dependencies: gnuradio (>= 3.7.3), armadillo, gflags, glog, gnutls license: GPLv3+ repo: https://github.com/gnss-sdr/gnss-sdr -website: http://gnss-sdr.org +website: https://gnss-sdr.org icon: http://a.fsdn.com/con/app/proj/gnss-sdr/screenshots/logo400x400.jpg --- -Global Navigation Satellite Systems receiver defined by software. It performs all the signal -processing from raw signal samples up to the computation of the Position-Velocity-Time solution, -including code and phase observables. It is able to work with raw data files or, if there is -computational power enough, in real time with suitable radiofrequency front-ends. This software +Global Navigation Satellite Systems receiver defined by software. It performs all the signal +processing from raw signal samples up to the computation of the Position-Velocity-Time solution, +including code and phase observables. It is able to work with raw data files or, if there is +computational power enough, in real time with suitable radiofrequency front-ends. This software is mainly developed at [CTTC](http://www.cttc.es "Centre Tecnologic de Telecomunicacions de Catalunya") -with contributions from around the world. More info at [gnss-sdr.org](http://gnss-sdr.org "GNSS-SDR's Homepage"). - +with contributions from around the world. More info at [gnss-sdr.org](https://gnss-sdr.org "GNSS-SDR's Homepage"). diff --git a/README.md b/README.md index ddb36c7c9..98ae27efa 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -[![](./docs/doxygen/images/gnss-sdr_logo.png)](http://gnss-sdr.org "GNSS-SDR website") +[![](./docs/doxygen/images/gnss-sdr_logo.png)](https://gnss-sdr.org "GNSS-SDR website") [![License: GPL v3](https://img.shields.io/badge/License-GPL%20v3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0) @@ -19,14 +19,14 @@ In the L5 band (centered at 1176.45 MHz): - 🛰 GPS L5 :white_check_mark: - 🛰 Galileo E5a :white_check_mark: -GNSS-SDR provides interfaces for a wide range of radio frequency front-ends, generates processing outputs in standard formats, allows for the full inspection of the whole signal processing chain, and offers a framework for the development of new features. Please visit [http://gnss-sdr.org](http://gnss-sdr.org "GNSS-SDR website") for more information about this open source software-defined GNSS receiver. +GNSS-SDR provides interfaces for a wide range of radio frequency front-ends, generates processing outputs in standard formats, allows for the full inspection of the whole signal processing chain, and offers a framework for the development of new features. Please visit [https://gnss-sdr.org](https://gnss-sdr.org "GNSS-SDR website") for more information about this open source software-defined GNSS receiver. # How to build GNSS-SDR -This section describes how to set up the compilation environment in GNU/Linux or [macOS / Mac OS X](#macosx), and to build GNSS-SDR. See also our [build and install page](http://gnss-sdr.org/build-and-install/ "GNSS-SDR's Build and Install"). +This section describes how to set up the compilation environment in GNU/Linux or [macOS / Mac OS X](#macosx), and to build GNSS-SDR. See also our [build and install page](https://gnss-sdr.org/build-and-install/ "GNSS-SDR's Build and Install"). GNU/Linux @@ -286,7 +286,7 @@ By default, you will be in the 'master' branch of the Git repository, which corr $ git checkout next ~~~~~~ -More information about GNSS-SDR-specific Git usage and pointers to further readings can be found at our [Git tutorial](http://gnss-sdr.org/docs/tutorials/using-git/ "Using Git"). +More information about GNSS-SDR-specific Git usage and pointers to further readings can be found at our [Git tutorial](https://gnss-sdr.org/docs/tutorials/using-git/ "Using Git"). ### Build and install GNSS-SDR @@ -507,7 +507,7 @@ $ sudo make install Using this option, all SIMD instructions are exclusively accessed via VOLK, which automatically includes versions of each function for different SIMD instruction sets, then detects at runtime which to use, or if there are none, substitutes a generic, non-SIMD implementation. -More details can be found in our tutorial about [GNSS-SDR configuration options at building time](http://gnss-sdr.org/docs/tutorials/using-git/ "Configuration options at building time"). +More details can be found in our tutorial about [GNSS-SDR configuration options at building time](https://gnss-sdr.org/docs/tutorials/using-git/ "Configuration options at building time"). macOS and Mac OS X @@ -648,7 +648,7 @@ Other builds * **Snap packages**: [Snaps](http://snapcraft.io) are universal Linux packages aimed to work on any distribution or device, from IoT devices to servers, desktops to mobile devices. Visit [https://github.com/carlesfernandez/snapcraft-sandbox](https://github.com/carlesfernandez/snapcraft-sandbox) for instructions. -* **GNSS-SDR in embedded platforms**: we provide a Software Development Kit (SDK) based on [OpenEmbedded](http://www.openembedded.org/wiki/Main_Page) for cross-compiling GNSS-SDR in your desktop computer and for producing executables that can run in embedded platforms, such as a Zedboard or a Raspberry Pi 3. Visit [Cross-compiling GNSS-SDR](http://gnss-sdr.org/docs/tutorials/cross-compiling/) for instructions. +* **GNSS-SDR in embedded platforms**: we provide a Software Development Kit (SDK) based on [OpenEmbedded](http://www.openembedded.org/wiki/Main_Page) for cross-compiling GNSS-SDR in your desktop computer and for producing executables that can run in embedded platforms, such as a Zedboard or a Raspberry Pi 3. Visit [Cross-compiling GNSS-SDR](https://gnss-sdr.org/docs/tutorials/cross-compiling/) for instructions. Updating GNSS-SDR @@ -680,9 +680,9 @@ Before rebuilding the source code, it is safe (and recommended) to remove the re $ rm -rf gnss-sdr/build/* ~~~~~~ -If you are interested in contributing to the development of GNSS-SDR, please check out [how to do it](http://gnss-sdr.org/contribute/ "How to contribute to GNSS-SDR source code"). +If you are interested in contributing to the development of GNSS-SDR, please check out [how to do it](https://gnss-sdr.org/contribute/ "How to contribute to GNSS-SDR source code"). -There is a more controlled way to upgrade your repository, which is to use the Git commands ```fetch``` and ```merge```, as described in our [Git Tutorial](http://gnss-sdr.org/docs/tutorials/using-git/ "Using Git"). +There is a more controlled way to upgrade your repository, which is to use the Git commands ```fetch``` and ```merge```, as described in our [Git Tutorial](https://gnss-sdr.org/docs/tutorials/using-git/ "Using Git"). @@ -712,7 +712,7 @@ We use a [DBSRX2](https://www.ettus.com/product/details/DBSRX2) to do the task, ```$ gnss-sdr --config_file=/path/to/my_receiver.conf``` The program reports the current status in text mode, directly to the terminal window. If all goes well, and GNSS-SDR is able to successfully track and decode at least 4 satellites, you will get PVT fixes. The program will write .kml, .geojson and RINEX files in the folder from which ```gnss-sdr``` was run. In addition to the console output, GNSS-SDR also writes log files at /tmp/ (configurable with the commandline flag ```./gnss-sdr --log_dir=/path/to/log```). -For more information, check out our [quick start guide](http://gnss-sdr.org/quick-start-guide/). +For more information, check out our [quick start guide](https://gnss-sdr.org/quick-start-guide/). Using GNSS-SDR @@ -772,7 +772,7 @@ Since the configuration is just a set of property names and values without any m Hence, the application defines a simple accessor class to fetch the configuration pairs of values and passes them to a factory class called [GNSSBlockFactory](./src/core/receiver/gnss_block_factory.h). This factory decides, according to the configuration, which class needs to be instantiated and which parameters should be passed to the constructor. Hence, the factory encapsulates the complexity of blocks' instantiation. With that approach, adding a new block that requires new parameters will be as simple as adding the block class and modifying the factory to be able to instantiate it. This loose coupling between the blocks' implementations and the syntax of the configuration enables extending the application capacities in a high degree. It also allows producing fully customized receivers, for instance a testbed for acquisition algorithms, and to place observers at any point of the receiver chain. -More information can be found at the [Control Plane page](http://gnss-sdr.org/docs/control-plane/). +More information can be found at the [Control Plane page](https://gnss-sdr.org/docs/control-plane/). Signal Processing plane @@ -800,7 +800,7 @@ Internally, GNSS-SDR makes use of the complex data types defined by [VOLK](http: - **`gr_complex`**: Complex samples, with real and imaginary parts of type `float`. C++ type name: `std::complex`. -More information about the available processing blocks and their configuration parameters can be found at the [Signal Processing Blocks documentation page](http://gnss-sdr.org/docs/sp-blocks/). +More information about the available processing blocks and their configuration parameters can be found at the [Signal Processing Blocks documentation page](https://gnss-sdr.org/docs/sp-blocks/). ### Signal Source @@ -994,7 +994,7 @@ SignalSource.dump1=false ~~~~~~ -More documentation and examples are available at the [Signal Source Blocks page](http://gnss-sdr.org/docs/sp-blocks/signal-source/). +More documentation and examples are available at the [Signal Source Blocks page](https://gnss-sdr.org/docs/sp-blocks/signal-source/). ### Signal Conditioner @@ -1015,7 +1015,7 @@ If you need to adapt some aspect of your signal, you can enable the Signal Condi SignalConditioner.implementation=Signal_Conditioner ~~~~~~ -More documentation at the [Signal Conditioner Blocks page](http://gnss-sdr.org/docs/sp-blocks/signal-conditioner/). +More documentation at the [Signal Conditioner Blocks page](https://gnss-sdr.org/docs/sp-blocks/signal-conditioner/). #### Data type adapter @@ -1027,7 +1027,7 @@ This block changes the type of input data samples. If your signal source deliver DataTypeAdapter.implementation=Ishort_To_Complex ~~~~~~ -More documentation at the [Data Type Adapter Blocks page](http://gnss-sdr.org/docs/sp-blocks/data-type-adapter/). +More documentation at the [Data Type Adapter Blocks page](https://gnss-sdr.org/docs/sp-blocks/data-type-adapter/). #### Input filter @@ -1082,7 +1082,7 @@ InputFilter.IF=0 InputFilter.decimation_factor=1 ~~~~~~ -More documentation at the [Input Filter Blocks page](http://gnss-sdr.org/docs/sp-blocks/input-filter/). +More documentation at the [Input Filter Blocks page](https://gnss-sdr.org/docs/sp-blocks/input-filter/). #### Resampler @@ -1100,7 +1100,7 @@ Resampler.sample_freq_in=8000000 ; sample frequency of the input signal Resampler.sample_freq_out=4000000 ; desired sample frequency of the output signal ~~~~~~ -More documentation at the [Resampler Blocks page](http://gnss-sdr.org/docs/sp-blocks/resampler/). +More documentation at the [Resampler Blocks page](https://gnss-sdr.org/docs/sp-blocks/resampler/). ### Channel @@ -1150,7 +1150,7 @@ This module is also in charge of managing the interplay between acquisition and The abstract class [ChannelInterface](./src/core/interfaces/channel_interface.h) represents an interface to a channel GNSS block. Check [Channel](./src/algorithms/channel/adapters/channel.h) for an actual implementation. -More documentation at the [Channels page](http://gnss-sdr.org/docs/sp-blocks/channels/). +More documentation at the [Channels page](https://gnss-sdr.org/docs/sp-blocks/channels/). @@ -1201,7 +1201,7 @@ Acquisition_1B.dump=false Acquisition_1B.dump_filename=./acq_dump.dat ~~~~~~ -More documentation at the [Acquisition Blocks page](http://gnss-sdr.org/docs/sp-blocks/acquisition/). +More documentation at the [Acquisition Blocks page](https://gnss-sdr.org/docs/sp-blocks/acquisition/). #### Tracking @@ -1251,7 +1251,7 @@ Tracking_1B.dump=false Tracking_1B.dump_filename=../data/veml_tracking_ch_ ~~~~~~ -More documentation at the [Tracking Blocks page](http://gnss-sdr.org/docs/sp-blocks/tracking/). +More documentation at the [Tracking Blocks page](https://gnss-sdr.org/docs/sp-blocks/tracking/). #### Decoding of the navigation message @@ -1279,7 +1279,7 @@ TelemetryDecoder_1B.implementation=Galileo_E1B_Telemetry_Decoder TelemetryDecoder_1B.dump=false ~~~~~~ -More documentation at the [Telemetry Decoder Blocks page](http://gnss-sdr.org/docs/sp-blocks/telemetry-decoder/). +More documentation at the [Telemetry Decoder Blocks page](https://gnss-sdr.org/docs/sp-blocks/telemetry-decoder/). #### Observables @@ -1297,7 +1297,7 @@ Observables.dump=false Observables.dump_filename=./observables.dat ~~~~~~ -More documentation at the [Observables Blocks page](http://gnss-sdr.org/docs/sp-blocks/observables/). +More documentation at the [Observables Blocks page](https://gnss-sdr.org/docs/sp-blocks/observables/). #### Computation of Position, Velocity and Time @@ -1354,7 +1354,7 @@ PVT.rtcm_station_id=1111 In order to get well-formatted GeoJSON, KML and RINEX files, always terminate ```gnss-sdr``` execution by pressing key ```q``` and then key ```ENTER```. Those files will be automatically deleted if no position fix have been obtained during the execution of the software receiver. -More documentation at the [PVT Blocks page](http://gnss-sdr.org/docs/sp-blocks/pvt/). +More documentation at the [PVT Blocks page](https://gnss-sdr.org/docs/sp-blocks/pvt/). About the software license @@ -1393,7 +1393,7 @@ For LaTeX users, this is the BibTeX entry for your convenience: ~~~~~~ -There is a list of papers related to GNSS-SDR in our [publications page](http://gnss-sdr.org/publications/ "Publications"). +There is a list of papers related to GNSS-SDR in our [publications page](https://gnss-sdr.org/publications/ "Publications"). @@ -1404,9 +1404,9 @@ In order to start using GNSS-SDR, you may want to populate ```gnss-sdr/data``` f Another interesting option is working in real-time with an RF front-end. We provide drivers for UHD-compatible hardware such as the [USRP family](http://www.ettus.com/product), for OsmoSDR and other front-ends (HackRF, bladeRF, LimeSDR), for the GN3S v2 USB dongle and for some DVB-T USB dongles. Start with a low number of channels and then increase it in order to test how many channels your processor can handle in real-time. -You can find more information at the [GNSS-SDR Documentation page](http://gnss-sdr.org/docs/) or directly asking to the [GNSS-SDR Developers mailing list](http://lists.sourceforge.net/lists/listinfo/gnss-sdr-developers). +You can find more information at the [GNSS-SDR Documentation page](https://gnss-sdr.org/docs/) or directly asking to the [GNSS-SDR Developers mailing list](http://lists.sourceforge.net/lists/listinfo/gnss-sdr-developers). -You are also very welcome to contribute to the project, there are many ways to [participate in GNSS-SDR](http://gnss-sdr.org/contribute/). If you need some special feature not yet implemented, the Developer Team would love to be hired for developing it. Please do not hesitate to [contact them](http://gnss-sdr.org/team/). +You are also very welcome to contribute to the project, there are many ways to [participate in GNSS-SDR](https://gnss-sdr.org/contribute/). If you need some special feature not yet implemented, the Developer Team would love to be hired for developing it. Please do not hesitate to [contact them](https://gnss-sdr.org/team/). **Enjoy GNSS-SDR!** diff --git a/conf/front-end-cal.conf b/conf/front-end-cal.conf index 6ef6ec846..106b8d736 100644 --- a/conf/front-end-cal.conf +++ b/conf/front-end-cal.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Default configuration file ; You can define your own front-end calibration tool configuration and invoke it by doing @@ -21,7 +21,7 @@ GNSS-SDR.init_altitude_m=10 ; Mozoncillo ;GNSS-SDR.init_latitude_deg=41.14534824586196 -;GNSS-SDR.init_longitude_deg=-4.187125019737464 +;GNSS-SDR.init_longitude_deg=-4.187125019737464 ;GNSS-SDR.init_altitude_m=900 @@ -45,28 +45,28 @@ GNSS-SDR.SUPL_CI=40184 ;######### SIGNAL_SOURCE CONFIG ############ SignalSource.implementation=Osmosdr_Signal_Source -;#freq: RF front-end center frequency in [Hz] +;#freq: RF front-end center frequency in [Hz] SignalSource.freq=1575420000 ;#item_type: Type and resolution for each of the signal samples. Use only gr_complex in this version. SignalSource.item_type=gr_complex -;#sampling_frequency: Original Signal sampling frequency in samples per second +;#sampling_frequency: Original Signal sampling frequency in samples per second SignalSource.sampling_frequency=2000000 -;#gain: Front-end Gain in [dB] -SignalSource.gain=40 +;#gain: Front-end Gain in [dB] +SignalSource.gain=40 SignalSource.rf_gain=40 SignalSource.if_gain=30 SignalSource.AGC_enabled=false -;# Please note that the new RTL-SDR Blog V3 dongles ship a < 1 PPM +;# Please note that the new RTL-SDR Blog V3 dongles ship a < 1 PPM ;# temperature compensated oscillator (TCXO), which is well suited for GNSS ;# signal processing, and a 4.5 V powered bias-tee to feed an active antenna. -;# Whether the bias-tee is turned off before reception depends on which version -;# of gr-osmosdr was used when compiling GNSS-SDR. With an old version -;# (for example, v0.1.4-8), the utility rtl_biast may be used to switch the -;# bias-tee, and then call gnss-sdr. +;# Whether the bias-tee is turned off before reception depends on which version +;# of gr-osmosdr was used when compiling GNSS-SDR. With an old version +;# (for example, v0.1.4-8), the utility rtl_biast may be used to switch the +;# bias-tee, and then call gnss-sdr. ;# See https://github.com/rtlsdrblog/rtl_biast ;# After reception the bias-tee is switched off automatically by the program. -;# With newer versions of gr-osmosdr (>= 0.1.4-13), the bias-tee can be +;# With newer versions of gr-osmosdr (>= 0.1.4-13), the bias-tee can be ;# activated by uncommenting the following line: ;SignalSource.osmosdr_args=rtl,bias=1 @@ -82,7 +82,7 @@ SignalSource.dump=false SignalSource.dump_filename=../data/signal_source.dat ;######### SIGNAL_CONDITIONER CONFIG ############ -;## It holds blocks to change data type, filter and resample input data. +;## It holds blocks to change data type, filter and resample input data. ;#implementation: Use [Pass_Through] or [Signal_Conditioner] ;#[Pass_Through] disables this block and the [DataTypeAdapter], [InputFilter] and [Resampler] blocks @@ -108,7 +108,7 @@ DataTypeAdapter.dump_filename=../data/data_type_adapter.dat InputFilter.implementation=Freq_Xlating_Fir_Filter -;#The following options are used in the filter design of Fir_Filter and Freq_Xlating_Fir_Filter implementation. +;#The following options are used in the filter design of Fir_Filter and Freq_Xlating_Fir_Filter implementation. ;#These options are based on parameters of gnuradio's function: gr_remez. ;#This function calculates the optimal (in the Chebyshev/minimax sense) FIR filter impulse response given a set of band edges, ;#the desired response on those bands, and the weight given to the error in those bands. @@ -151,7 +151,7 @@ InputFilter.ampl2_end=0.0 InputFilter.band1_error=1.0 InputFilter.band2_error=1.0 -;#filter_type: one of "bandpass", "hilbert" or "differentiator" +;#filter_type: one of "bandpass", "hilbert" or "differentiator" InputFilter.filter_type=bandpass ;#grid_density: determines how accurately the filter will be constructed. @@ -182,7 +182,7 @@ Resampler.implementation=Pass_Through Acquisition_1C.implementation=GPS_L1_CA_PCPS_Acquisition_Fine_Doppler ;#item_type: Type and resolution for each of the signal samples. Use only gr_complex in this version. Acquisition.item_type=gr_complex -;#if: Signal intermediate frequency in [Hz] +;#if: Signal intermediate frequency in [Hz] Acquisition.if=0 ;#sampled_ms: Signal block duration for the acquisition signal detection [ms] Acquisition.sampled_ms=1 @@ -196,8 +196,7 @@ Acquisition.doppler_min=-100000 Acquisition.doppler_step=500 ;#maximum dwells Acquisition.max_dwells=15 -;#dump: Enable or disable the acquisition internal data file logging [true] or [false] +;#dump: Enable or disable the acquisition internal data file logging [true] or [false] Acquisition.dump=false ;#filename: Log path and filename Acquisition.dump_filename=./acq_dump.dat - diff --git a/conf/gnss-sdr.conf b/conf/gnss-sdr.conf index e9a05e798..4c9ae11a4 100644 --- a/conf/gnss-sdr.conf +++ b/conf/gnss-sdr.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Default configuration file ; You can define your own receiver and invoke it by doing @@ -141,4 +141,3 @@ PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false PVT.dump_filename=./PVT - diff --git a/conf/gnss-sdr_GLONASS_L1_CA_GPS_L1_CA_ibyte.conf b/conf/gnss-sdr_GLONASS_L1_CA_GPS_L1_CA_ibyte.conf index f042def9c..88c8741b6 100644 --- a/conf/gnss-sdr_GLONASS_L1_CA_GPS_L1_CA_ibyte.conf +++ b/conf/gnss-sdr_GLONASS_L1_CA_GPS_L1_CA_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L1_CA_GPS_L2C_ibyte.conf b/conf/gnss-sdr_GLONASS_L1_CA_GPS_L2C_ibyte.conf index 09bddfb46..435194b75 100644 --- a/conf/gnss-sdr_GLONASS_L1_CA_GPS_L2C_ibyte.conf +++ b/conf/gnss-sdr_GLONASS_L1_CA_GPS_L2C_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L1_CA_ibyte.conf b/conf/gnss-sdr_GLONASS_L1_CA_ibyte.conf index 077d3dd1e..1e4b6a24b 100644 --- a/conf/gnss-sdr_GLONASS_L1_CA_ibyte.conf +++ b/conf/gnss-sdr_GLONASS_L1_CA_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L1_CA_ibyte_coh_trk.conf b/conf/gnss-sdr_GLONASS_L1_CA_ibyte_coh_trk.conf index ca1197a6d..6e30d5566 100644 --- a/conf/gnss-sdr_GLONASS_L1_CA_ibyte_coh_trk.conf +++ b/conf/gnss-sdr_GLONASS_L1_CA_ibyte_coh_trk.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L2_CA_GPS_L1_CA_ibyte.conf b/conf/gnss-sdr_GLONASS_L2_CA_GPS_L1_CA_ibyte.conf index 7e4e9e03f..3c56e6132 100644 --- a/conf/gnss-sdr_GLONASS_L2_CA_GPS_L1_CA_ibyte.conf +++ b/conf/gnss-sdr_GLONASS_L2_CA_GPS_L1_CA_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L2_CA_GPS_L2C_ibyte.conf b/conf/gnss-sdr_GLONASS_L2_CA_GPS_L2C_ibyte.conf index c3ab7cb9c..10df72ae2 100644 --- a/conf/gnss-sdr_GLONASS_L2_CA_GPS_L2C_ibyte.conf +++ b/conf/gnss-sdr_GLONASS_L2_CA_GPS_L2C_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L2_CA_ibyte.conf b/conf/gnss-sdr_GLONASS_L2_CA_ibyte.conf index 7cc44a0a4..39b6fa5ab 100644 --- a/conf/gnss-sdr_GLONASS_L2_CA_ibyte.conf +++ b/conf/gnss-sdr_GLONASS_L2_CA_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GLONASS_L2_CA_ibyte_coh_trk.conf b/conf/gnss-sdr_GLONASS_L2_CA_ibyte_coh_trk.conf index ca1197a6d..6e30d5566 100644 --- a/conf/gnss-sdr_GLONASS_L2_CA_ibyte_coh_trk.conf +++ b/conf/gnss-sdr_GLONASS_L2_CA_ibyte_coh_trk.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GPS_L1_2ch_fmcomms2_realtime.conf b/conf/gnss-sdr_GPS_L1_2ch_fmcomms2_realtime.conf index f53fe2ea6..cd3345904 100644 --- a/conf/gnss-sdr_GPS_L1_2ch_fmcomms2_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_2ch_fmcomms2_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_CA_ibyte.conf b/conf/gnss-sdr_GPS_L1_CA_ibyte.conf index 959181078..da4b273c2 100644 --- a/conf/gnss-sdr_GPS_L1_CA_ibyte.conf +++ b/conf/gnss-sdr_GPS_L1_CA_ibyte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GPS_L1_FPGA.conf b/conf/gnss-sdr_GPS_L1_FPGA.conf index c6bb2edfc..70ec83ed5 100644 --- a/conf/gnss-sdr_GPS_L1_FPGA.conf +++ b/conf/gnss-sdr_GPS_L1_FPGA.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -82,4 +82,3 @@ PVT.flag_rtcm_server=false PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false - diff --git a/conf/gnss-sdr_GPS_L1_GN3S_realtime.conf b/conf/gnss-sdr_GPS_L1_GN3S_realtime.conf index bc99d4a28..9982a1cbd 100644 --- a/conf/gnss-sdr_GPS_L1_GN3S_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_GN3S_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_LimeSDR.conf b/conf/gnss-sdr_GPS_L1_LimeSDR.conf index ab1242bc7..c50572aef 100644 --- a/conf/gnss-sdr_GPS_L1_LimeSDR.conf +++ b/conf/gnss-sdr_GPS_L1_LimeSDR.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GPS_L1_SPIR.conf b/conf/gnss-sdr_GPS_L1_SPIR.conf index 6f3affed4..f6fa9a076 100644 --- a/conf/gnss-sdr_GPS_L1_SPIR.conf +++ b/conf/gnss-sdr_GPS_L1_SPIR.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -133,5 +133,3 @@ PVT.flag_nmea_tty_port=true; PVT.nmea_dump_devname=/dev/pts/4 PVT.dump=false PVT.dump_filename=./PVT - - diff --git a/conf/gnss-sdr_GPS_L1_USRP_X300_realtime.conf b/conf/gnss-sdr_GPS_L1_USRP_X300_realtime.conf index 89f84fd77..ba96a533e 100644 --- a/conf/gnss-sdr_GPS_L1_USRP_X300_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_USRP_X300_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Configuration file for using USRP X300 as a RF front-end for GPS L1 signals. ; Set SignalSource.device_address to the IP address of your device diff --git a/conf/gnss-sdr_GPS_L1_USRP_realtime.conf b/conf/gnss-sdr_GPS_L1_USRP_realtime.conf index 1cb41801f..b432eb6b2 100644 --- a/conf/gnss-sdr_GPS_L1_USRP_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_USRP_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Configuration file for using USRP 1 as a RF front-end for GPS L1 signals. ; Run: diff --git a/conf/gnss-sdr_GPS_L1_acq_QuickSync.conf b/conf/gnss-sdr_GPS_L1_acq_QuickSync.conf index 1f74645fb..fd7b5d8ff 100644 --- a/conf/gnss-sdr_GPS_L1_acq_QuickSync.conf +++ b/conf/gnss-sdr_GPS_L1_acq_QuickSync.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_bladeRF.conf b/conf/gnss-sdr_GPS_L1_bladeRF.conf index 48017a8ec..80e9ddda8 100644 --- a/conf/gnss-sdr_GPS_L1_bladeRF.conf +++ b/conf/gnss-sdr_GPS_L1_bladeRF.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ [GNSS-SDR] diff --git a/conf/gnss-sdr_GPS_L1_fmcomms2_realtime.conf b/conf/gnss-sdr_GPS_L1_fmcomms2_realtime.conf index 17880d8a2..3de8486d8 100644 --- a/conf/gnss-sdr_GPS_L1_fmcomms2_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_fmcomms2_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_gr_complex.conf b/conf/gnss-sdr_GPS_L1_gr_complex.conf index 0cf4d146c..7f83c666c 100644 --- a/conf/gnss-sdr_GPS_L1_gr_complex.conf +++ b/conf/gnss-sdr_GPS_L1_gr_complex.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_gr_complex_gpu.conf b/conf/gnss-sdr_GPS_L1_gr_complex_gpu.conf index 7ecb75715..33c3a07b6 100644 --- a/conf/gnss-sdr_GPS_L1_gr_complex_gpu.conf +++ b/conf/gnss-sdr_GPS_L1_gr_complex_gpu.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_ishort.conf b/conf/gnss-sdr_GPS_L1_ishort.conf index a9528d183..373049a25 100644 --- a/conf/gnss-sdr_GPS_L1_ishort.conf +++ b/conf/gnss-sdr_GPS_L1_ishort.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_nsr.conf b/conf/gnss-sdr_GPS_L1_nsr.conf index 5e2bee6ba..2b3d3f5f4 100644 --- a/conf/gnss-sdr_GPS_L1_nsr.conf +++ b/conf/gnss-sdr_GPS_L1_nsr.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Sample configuration file for IFEN SX-NSR software receiver front-end ; http://www.ifen.com/products/sx-scientific-gnss-solutions/nsr-software-receiver.html diff --git a/conf/gnss-sdr_GPS_L1_nsr_twobit_packed.conf b/conf/gnss-sdr_GPS_L1_nsr_twobit_packed.conf index dffa01314..d31885566 100644 --- a/conf/gnss-sdr_GPS_L1_nsr_twobit_packed.conf +++ b/conf/gnss-sdr_GPS_L1_nsr_twobit_packed.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Sample configuration file for IFEN SX-NSR software receiver front-end ; http://www.ifen.com/products/sx-scientific-gnss-solutions/nsr-software-receiver.html diff --git a/conf/gnss-sdr_GPS_L1_plutosdr_realtime.conf b/conf/gnss-sdr_GPS_L1_plutosdr_realtime.conf index d3be2c6b6..fa8996dc7 100644 --- a/conf/gnss-sdr_GPS_L1_plutosdr_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_plutosdr_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_pulse_blanking_gr_complex.conf b/conf/gnss-sdr_GPS_L1_pulse_blanking_gr_complex.conf index 4f68bdb08..e186f1da7 100644 --- a/conf/gnss-sdr_GPS_L1_pulse_blanking_gr_complex.conf +++ b/conf/gnss-sdr_GPS_L1_pulse_blanking_gr_complex.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_rtl_tcp_realtime.conf b/conf/gnss-sdr_GPS_L1_rtl_tcp_realtime.conf index 01b30c02a..91b952ad0 100644 --- a/conf/gnss-sdr_GPS_L1_rtl_tcp_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_rtl_tcp_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L1_rtlsdr_realtime.conf b/conf/gnss-sdr_GPS_L1_rtlsdr_realtime.conf index 18d783741..f3252578b 100644 --- a/conf/gnss-sdr_GPS_L1_rtlsdr_realtime.conf +++ b/conf/gnss-sdr_GPS_L1_rtlsdr_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -45,16 +45,16 @@ SignalSource.dump=false SignalSource.dump_filename=../data/signal_source.dat SignalSource.enable_throttle_control=false -;# Please note that the new RTL-SDR Blog V3 dongles ship a < 1 PPM +;# Please note that the new RTL-SDR Blog V3 dongles ship a < 1 PPM ;# temperature compensated oscillator (TCXO), which is well suited for GNSS ;# signal processing, and a 4.5 V powered bias-tee to feed an active antenna. -;# Whether the bias-tee is turned off before reception depends on which version -;# of gr-osmosdr was used when compiling GNSS-SDR. With an old version -;# (for example, v0.1.4-8), the utility rtl_biast may be used to switch the -;# bias-tee, and then call gnss-sdr. +;# Whether the bias-tee is turned off before reception depends on which version +;# of gr-osmosdr was used when compiling GNSS-SDR. With an old version +;# (for example, v0.1.4-8), the utility rtl_biast may be used to switch the +;# bias-tee, and then call gnss-sdr. ;# See https://github.com/rtlsdrblog/rtl_biast ;# After reception the bias-tee is switched off automatically by the program. -;# With newer versions of gr-osmosdr (>= 0.1.4-13), the bias-tee can be +;# With newer versions of gr-osmosdr (>= 0.1.4-13), the bias-tee can be ;# activated by uncommenting the following line: ;SignalSource.osmosdr_args=rtl,bias=1 diff --git a/conf/gnss-sdr_GPS_L1_two_bits_cpx.conf b/conf/gnss-sdr_GPS_L1_two_bits_cpx.conf index 1cf1ac378..84753bee7 100644 --- a/conf/gnss-sdr_GPS_L1_two_bits_cpx.conf +++ b/conf/gnss-sdr_GPS_L1_two_bits_cpx.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_GPS_L2C_USRP1_realtime.conf b/conf/gnss-sdr_GPS_L2C_USRP1_realtime.conf index 362e747a3..6d61e063b 100644 --- a/conf/gnss-sdr_GPS_L2C_USRP1_realtime.conf +++ b/conf/gnss-sdr_GPS_L2C_USRP1_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Configuration file for using USRP1 as a RF front-end for GPS L2C signals ; Run: diff --git a/conf/gnss-sdr_GPS_L2C_USRP_X300_realtime.conf b/conf/gnss-sdr_GPS_L2C_USRP_X300_realtime.conf index 1572b45cd..55a84a13e 100644 --- a/conf/gnss-sdr_GPS_L2C_USRP_X300_realtime.conf +++ b/conf/gnss-sdr_GPS_L2C_USRP_X300_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; Configuration file for using USRP X300 as a RF front-end for GPS L2C signals ; Set SignalSource.device_address to the IP address of your device diff --git a/conf/gnss-sdr_Galileo_E1_USRP_X300_realtime.conf b/conf/gnss-sdr_Galileo_E1_USRP_X300_realtime.conf index aad3dd417..2207039da 100644 --- a/conf/gnss-sdr_Galileo_E1_USRP_X300_realtime.conf +++ b/conf/gnss-sdr_Galileo_E1_USRP_X300_realtime.conf @@ -1,3 +1,6 @@ +; This is a GNSS-SDR configuration file +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ + ; Configuration file for using USRP X300 as a RF front-end for Galileo E1 signals. ; Set SignalSource.device_address to the IP address of your device ; and run: diff --git a/conf/gnss-sdr_Galileo_E1_acq_QuickSync.conf b/conf/gnss-sdr_Galileo_E1_acq_QuickSync.conf index 2653a1402..8ed21451f 100644 --- a/conf/gnss-sdr_Galileo_E1_acq_QuickSync.conf +++ b/conf/gnss-sdr_Galileo_E1_acq_QuickSync.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_Galileo_E1_ishort.conf b/conf/gnss-sdr_Galileo_E1_ishort.conf index 22a64245d..ff0f52a5a 100644 --- a/conf/gnss-sdr_Galileo_E1_ishort.conf +++ b/conf/gnss-sdr_Galileo_E1_ishort.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -104,4 +104,4 @@ PVT.rtcm_MSM_rate_ms=1000 PVT.flag_rtcm_tty_port=false; PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false -PVT.dump_filename=./PVT \ No newline at end of file +PVT.dump_filename=./PVT diff --git a/conf/gnss-sdr_Galileo_E1_nsr.conf b/conf/gnss-sdr_Galileo_E1_nsr.conf index 7350f5314..b95b2a972 100644 --- a/conf/gnss-sdr_Galileo_E1_nsr.conf +++ b/conf/gnss-sdr_Galileo_E1_nsr.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_Galileo_E5a.conf b/conf/gnss-sdr_Galileo_E5a.conf index 5ab3096c3..c4df4139f 100644 --- a/conf/gnss-sdr_Galileo_E5a.conf +++ b/conf/gnss-sdr_Galileo_E5a.conf @@ -1,3 +1,6 @@ +; This is a GNSS-SDR configuration file +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ + ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf ; diff --git a/conf/gnss-sdr_Galileo_E5a_IFEN_CTTC.conf b/conf/gnss-sdr_Galileo_E5a_IFEN_CTTC.conf index e884778d2..f66079cb4 100644 --- a/conf/gnss-sdr_Galileo_E5a_IFEN_CTTC.conf +++ b/conf/gnss-sdr_Galileo_E5a_IFEN_CTTC.conf @@ -1,3 +1,6 @@ +; This is a GNSS-SDR configuration file +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ + ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf ; diff --git a/conf/gnss-sdr_Hybrid_byte.conf b/conf/gnss-sdr_Hybrid_byte.conf index bf50bcb30..a70b62820 100644 --- a/conf/gnss-sdr_Hybrid_byte.conf +++ b/conf/gnss-sdr_Hybrid_byte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_Hybrid_byte_sim.conf b/conf/gnss-sdr_Hybrid_byte_sim.conf index 60cca8e00..cd5ce2f3c 100644 --- a/conf/gnss-sdr_Hybrid_byte_sim.conf +++ b/conf/gnss-sdr_Hybrid_byte_sim.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_Hybrid_gr_complex.conf b/conf/gnss-sdr_Hybrid_gr_complex.conf index dbd9d8286..14fee756d 100644 --- a/conf/gnss-sdr_Hybrid_gr_complex.conf +++ b/conf/gnss-sdr_Hybrid_gr_complex.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_Hybrid_ishort.conf b/conf/gnss-sdr_Hybrid_ishort.conf index 6fc17c35c..55a70b7a2 100644 --- a/conf/gnss-sdr_Hybrid_ishort.conf +++ b/conf/gnss-sdr_Hybrid_ishort.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_Hybrid_nsr.conf b/conf/gnss-sdr_Hybrid_nsr.conf index 682482991..934ca2ffd 100644 --- a/conf/gnss-sdr_Hybrid_nsr.conf +++ b/conf/gnss-sdr_Hybrid_nsr.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_galileo_E1_extended_correlator_byte.conf b/conf/gnss-sdr_galileo_E1_extended_correlator_byte.conf index 18d9f5307..aea77c99c 100644 --- a/conf/gnss-sdr_galileo_E1_extended_correlator_byte.conf +++ b/conf/gnss-sdr_galileo_E1_extended_correlator_byte.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_galileo_E1_extended_correlator_labsat.conf b/conf/gnss-sdr_galileo_E1_extended_correlator_labsat.conf index cfbd1f73c..2a63b36b6 100644 --- a/conf/gnss-sdr_galileo_E1_extended_correlator_labsat.conf +++ b/conf/gnss-sdr_galileo_E1_extended_correlator_labsat.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_bin_file_III_1a.conf b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_bin_file_III_1a.conf index 2180d8ccb..7b978be5b 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_bin_file_III_1a.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_bin_file_III_1a.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1a.conf b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1a.conf index e53db62e7..bb5d4327e 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1a.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1a.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -185,4 +185,4 @@ PVT.flag_rtcm_server=true PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false -PVT.dump_filename=./PVT \ No newline at end of file +PVT.dump_filename=./PVT diff --git a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1b.conf b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1b.conf index aa0e26be4..2ef22b956 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1b.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_III_1b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -184,4 +184,4 @@ PVT.flag_rtcm_server=true PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false -PVT.dump_filename=./PVT \ No newline at end of file +PVT.dump_filename=./PVT diff --git a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_II_3b.conf b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_II_3b.conf index 7a7627cef..1d7fa6097 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_II_3b.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_II_3b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -191,4 +191,4 @@ PVT.flag_rtcm_server=true PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false -PVT.dump_filename=./PVT \ No newline at end of file +PVT.dump_filename=./PVT diff --git a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_I_1b.conf b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_I_1b.conf index 3dd9d76cd..2072f8c7d 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_I_1b.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_Flexiband_realtime_I_1b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multichannel_GPS_L1_L2_Flexiband_realtime_III_1b.conf b/conf/gnss-sdr_multichannel_GPS_L1_L2_Flexiband_realtime_III_1b.conf index 1513e6c8b..3094d8c97 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_L2_Flexiband_realtime_III_1b.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_L2_Flexiband_realtime_III_1b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multichannel_GPS_L1_L2_Galileo_E1B_Flexiband_bin_file_III_1b.conf b/conf/gnss-sdr_multichannel_GPS_L1_L2_Galileo_E1B_Flexiband_bin_file_III_1b.conf index 349b2f2b3..720c68fa9 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_L2_Galileo_E1B_Flexiband_bin_file_III_1b.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_L2_Galileo_E1B_Flexiband_bin_file_III_1b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -278,4 +278,3 @@ PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false PVT.dump_filename=./PVT - diff --git a/conf/gnss-sdr_multichannel_GPS_L1_USRP_X300_realtime.conf b/conf/gnss-sdr_multichannel_GPS_L1_USRP_X300_realtime.conf index c2216e648..411a712ab 100644 --- a/conf/gnss-sdr_multichannel_GPS_L1_USRP_X300_realtime.conf +++ b/conf/gnss-sdr_multichannel_GPS_L1_USRP_X300_realtime.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b.conf b/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b.conf index 9c899e6ca..fb6fae1c2 100644 --- a/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b.conf +++ b/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b_real.conf b/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b_real.conf index ab8bbaed6..6d62e65b3 100644 --- a/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b_real.conf +++ b/conf/gnss-sdr_multichannel_GPS_L2_M_Flexiband_bin_file_III_1b_real.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf @@ -253,4 +253,4 @@ PVT.flag_rtcm_server=false PVT.flag_rtcm_tty_port=false PVT.rtcm_dump_devname=/dev/pts/1 PVT.dump=false -PVT.dump_filename=./PVT \ No newline at end of file +PVT.dump_filename=./PVT diff --git a/conf/gnss-sdr_multichannel_all_in_one_Flexiband_bin_file_III_1b.conf b/conf/gnss-sdr_multichannel_all_in_one_Flexiband_bin_file_III_1b.conf index 26fa98a81..50e49f2e9 100644 --- a/conf/gnss-sdr_multichannel_all_in_one_Flexiband_bin_file_III_1b.conf +++ b/conf/gnss-sdr_multichannel_all_in_one_Flexiband_bin_file_III_1b.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multisource_Hybrid_ishort.conf b/conf/gnss-sdr_multisource_Hybrid_ishort.conf index 60f03431b..3394aff23 100644 --- a/conf/gnss-sdr_multisource_Hybrid_ishort.conf +++ b/conf/gnss-sdr_multisource_Hybrid_ishort.conf @@ -1,5 +1,5 @@ ; This is a GNSS-SDR configuration file -; The configuration API is described at http://gnss-sdr.org/docs/sp-blocks/ +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf diff --git a/conf/gnss-sdr_multisource_Hybrid_nsr.conf b/conf/gnss-sdr_multisource_Hybrid_nsr.conf index 8c035713e..aecb783a6 100644 --- a/conf/gnss-sdr_multisource_Hybrid_nsr.conf +++ b/conf/gnss-sdr_multisource_Hybrid_nsr.conf @@ -1,4 +1,6 @@ -; Default configuration file +; This is a GNSS-SDR configuration file +; The configuration API is described at https://gnss-sdr.org/docs/sp-blocks/ + ; You can define your own receiver and invoke it by doing ; gnss-sdr --config_file=my_GNSS_SDR_configuration.conf ; diff --git a/docs/PULL_REQUEST_TEMPLATE.md b/docs/PULL_REQUEST_TEMPLATE.md index bb69db911..0ab14dff6 100644 --- a/docs/PULL_REQUEST_TEMPLATE.md +++ b/docs/PULL_REQUEST_TEMPLATE.md @@ -1,12 +1,12 @@ -:+1::tada: Hello, and thanks for contributing to [GNSS-SDR](http://gnss-sdr.org)! :tada::+1: +:+1::tada: Hello, and thanks for contributing to [GNSS-SDR](https://gnss-sdr.org)! :tada::+1: Before submitting your pull request, please make sure the following is done: 1. You undertake the [Contributor Covenant Code of Conduct](https://github.com/gnss-sdr/gnss-sdr/blob/master/CODE_OF_CONDUCT.md). 2. If you are a first-time contributor, after your pull request you will be asked to sign an Individual Contributor License Agreement ([CLA](https://en.wikipedia.org/wiki/Contributor_License_Agreement)) before your code gets accepted into `master`. This license is for your protection as a Contributor as well as for the protection of [CTTC](http://www.cttc.es/); it does not change your rights to use your own contributions for any other purpose. Except for the license granted therein to CTTC and recipients of software distributed by CTTC, you reserve all right, title, and interest in and to your contributions. The information you provide in that CLA will be maintained in accordance with [CTTC's privacy policy](http://www.cttc.es/privacy/). 3. You have read the [Contributing Guidelines](https://github.com/gnss-sdr/gnss-sdr/blob/master/CONTRIBUTING.md). - 4. You have read the [coding style guide](http://gnss-sdr.org/coding-style/). - 5. Specifically, you have read [about clang-format](http://gnss-sdr.org/coding-style/#use-tools-for-automated-code-formatting) and you have applied it. + 4. You have read the [coding style guide](https://gnss-sdr.org/coding-style/). + 5. Specifically, you have read [about clang-format](https://gnss-sdr.org/coding-style/#use-tools-for-automated-code-formatting) and you have applied it. 6. You have forked the [gnss-sdr upstream repository](https://github.com/gnss-sdr/gnss-sdr) and have created your branch from `next` (or any other currently living branch in the upstream repository). 7. Please include a description of your changes here. -**Please feel free to delete this line and the above text once you have read it and in case you want to go on with your pull request.** \ No newline at end of file +**Please feel free to delete this line and the above text once you have read it and in case you want to go on with your pull request.** diff --git a/docs/doxygen/other/main_page.dox b/docs/doxygen/other/main_page.dox index edb07f998..10d95dbcc 100644 --- a/docs/doxygen/other/main_page.dox +++ b/docs/doxygen/other/main_page.dox @@ -26,7 +26,7 @@ Welcome to GNSS-SDR! GNSS-SDR is an open-source GNSS software receiver freely available to the research community. This project provides a common framework for GNSS signal processing which can operate in a variety of computer platforms. This tool is intended to foster collaboration, increase awareness, and reduce development costs in the field of GNSS receiver design and customized use of GNSS signals. For details about GNSS-SDR and using it, please see the main project page or browse the code at the main project page or browse the code at the Sourceforge project page. You could be also interested in subscribing to the mailing list. @@ -56,15 +56,15 @@ More details on GNSS-SDR signal processing blocks: \section overview Overview -GNSS-SDR provides an interface to different suitable RF front-ends and implements all the receiver chain up to the navigation solution. -Its design allows any kind of customization, including interchangeability of signal sources, signal processing algorithms, -interoperability with other systems, output formats, and offers interfaces to all the intermediate signals, parameters and variables. -The goal is to write efficient and truly reusable code, easy to read and maintain, with fewer bugs, and producing highly optimized executables -in a variety of hardware platforms and operating systems. In that sense, the challenge consists of defining a gentle balance within level -of abstraction and performance. GNSS-SDR runs in a personal computer and provides interfaces through USB and Ethernet +GNSS-SDR provides an interface to different suitable RF front-ends and implements all the receiver chain up to the navigation solution. +Its design allows any kind of customization, including interchangeability of signal sources, signal processing algorithms, +interoperability with other systems, output formats, and offers interfaces to all the intermediate signals, parameters and variables. +The goal is to write efficient and truly reusable code, easy to read and maintain, with fewer bugs, and producing highly optimized executables +in a variety of hardware platforms and operating systems. In that sense, the challenge consists of defining a gentle balance within level +of abstraction and performance. GNSS-SDR runs in a personal computer and provides interfaces through USB and Ethernet buses to a variety of either commercially available or custom-made RF front-ends, adapting the processing algorithms to different sampling frequencies, intermediate - frequencies and sample resolutions. This makes possible rapid prototyping of specific receivers intended, for instance, to geodetic applications, - observation of the ionospheric impact on navigation signals, GNSS reflectometry, signal quality monitoring, or carrier-phase based navigation techniques. + frequencies and sample resolutions. This makes possible rapid prototyping of specific receivers intended, for instance, to geodetic applications, + observation of the ionospheric impact on navigation signals, GNSS reflectometry, signal quality monitoring, or carrier-phase based navigation techniques. \image html overview.png \image latex overview.png "Overview" width=12cm @@ -73,8 +73,8 @@ As signal inputs, it accepts: \li Raw data file captured with a data grabber (digitized at some intermediate frequency or directly at baseband). \li Any suitable RF configuration that can be driven by the Universal Software Radio Peripheral Hardware Driver (UHD). This includes all current and future Ettus Research products. The USRP1 + DBSRX 2.2 daughterboard is an example of working configuration for GPS L1 C/A and Galileo E1B and E1C signals. -\li The GN3S v2 USB dongle (GN3S v3 might work with small modifications). -\li Experimentally, with some USB DVB-T dongles based on the Realtek RTL2832U chipset. +\li The GN3S v2 USB dongle (GN3S v3 might work with small modifications). +\li Experimentally, with some USB DVB-T dongles based on the Realtek RTL2832U chipset. \li For mathematical representations of the targeted signals, check out the \ref the_signal_model page. As outputs, it provides: @@ -85,13 +85,13 @@ As outputs, it provides: \li Position, Velocity and Time solution in KML format and NMEA -\section build Building GNSS-SDR +\section build Building GNSS-SDR -In principle, GNSS-SDR can be built in any Unix-like system. In practice, it depends on being able to install all the required dependencies. See the building guide page for details about the project's +In principle, GNSS-SDR can be built in any Unix-like system. In practice, it depends on being able to install all the required dependencies. See the building guide page for details about the project's dependencies and build process. Mainly, it consists on installing GNU Radio plus some few more libraries: \li Gflags, a library that implements commandline flags processing, -\li Glog, a library that implements application-level logging, +\li Glog, a library that implements application-level logging, \li Armadillo, a C++ linear algebra library, \li Googletest, Google's framework for writing C++ tests (requires definition of the GTEST_DIR variable), @@ -100,7 +100,7 @@ and, optionally, After all dependencies are installed, clone the GNSS-SDR repository: \verbatim -$ git clone git://git.code.sf.net/p/gnss-sdr/cttc gnss-sdr +$ git clone git://git.code.sf.net/p/gnss-sdr/cttc gnss-sdr \endverbatim This will create a folder named gnss-sdr with the following structure: @@ -111,7 +111,7 @@ This will create a folder named gnss-sdr with the following structure: |---conf <- Configuration files. Each file represents one receiver. |---data <- Populate this folder with your captured data. |---docs <- Contains documentation-related files - |---install <- Executables + |---install <- Executables |---src <- Source code folder |-----algorithms |-------PVT @@ -149,8 +149,8 @@ You can run them from that folder, but if you prefer to install gnss-sdr on your $ sudo make install \endverbatim -This will make a copy of the conf/ folder into /usr/local/share/gnss-sdr/conf for your reference. -We suggest to create a working directory at your preferred location and store your own configuration and data files there. +This will make a copy of the conf/ folder into /usr/local/share/gnss-sdr/conf for your reference. +We suggest to create a working directory at your preferred location and store your own configuration and data files there. You can create the documentation by doing: @@ -158,7 +158,7 @@ You can create the documentation by doing: $ make doc \endverbatim -from the gnss-sdr/build folder. In both cases, Doxygen will generate HTML documentation that can be +from the gnss-sdr/build folder. In both cases, Doxygen will generate HTML documentation that can be retrieved pointing your browser of preference to gnss-sdr/docs/html/index.html. There are two more extra targets available. From the gnss-sdr/build folder: @@ -207,7 +207,7 @@ You can also check The Git Boo With GNSS-SDR, you can define you own receiver, work with captured raw data or from a RF front-end, dump into files intermediate signals, or tune every single algorithm used in the \ref signal_processing. All the configuration is done in a single file. Those configuration files reside at the gnss-sdr/conf folder. By default, the executable gnss-sdr will read the configuration -available at gnss-sdr/conf/gnss-sdr.conf. You can edit that file to fit your needs, or even better, define a new my_receiver.conf file with your own configuration. +available at gnss-sdr/conf/gnss-sdr.conf. You can edit that file to fit your needs, or even better, define a new my_receiver.conf file with your own configuration. This new receiver can be done by invoking gnss-sdr with the --config_file flag pointing to your configuration file: \verbatim $ gnss-sdr --config_file=../conf/my_receiver.conf @@ -224,41 +224,41 @@ $ gnss-sdr --config_file=../conf/my_receiver.conf --signal_source=../data/my_cap \endverbatim This will override the SignalSource.filename specified in the configuration file. -You can get a complete list of available commandline flags by doing: +You can get a complete list of available commandline flags by doing: \verbatim $ gnss-sdr --help \endverbatim For general usage of commandline flags, see how to use Google Commandline Flags. \section control_plane Control plane -GNSS-SDR's main method initializes the logging library, processes the command line flags, if any, provided by the user and instantiates a ControlThread object. -Its constructor reads the configuration file, creates a control queue and creates a flowgraph according to the configuration. Then, the program's main method -calls the run() method of the instantiated object, an action that connects the flowgraph and starts running it. After that, and until a stop message is received, -it reads control messages sent by the receiver's modules through a safe-thread queue and processes them. Finally, when a stop message is received, the main +GNSS-SDR's main method initializes the logging library, processes the command line flags, if any, provided by the user and instantiates a ControlThread object. +Its constructor reads the configuration file, creates a control queue and creates a flowgraph according to the configuration. Then, the program's main method +calls the run() method of the instantiated object, an action that connects the flowgraph and starts running it. After that, and until a stop message is received, +it reads control messages sent by the receiver's modules through a safe-thread queue and processes them. Finally, when a stop message is received, the main method executes the destructor of the ControlThread object, which deallocates memory, does other cleanup and exits the program. -The GNSSFlowgraph class is responsible for preparing the graph of blocks according to the configuration, running it, modifying it during run-time and stopping it. -Blocks are identified by its role. This class knows which roles it has to instantiate and how to connect them. -It relies on the configuration to get the correct instances of the roles it needs and then it applies the connections between GNU Radio blocks to make the -graph ready to be started. The complexity related to managing the blocks and the data stream is handled by GNU Radio's gr::top_block class. GNSSFlowgraph wraps -the gr::top_block instance so we can take advantage of the \ref gnss_block_factory, the configuration system and the processing blocks. This class is also responsible -for applying changes to the configuration of the flowgraph during run-time, dynamically reconfiguring channels: it selects the strategy for selecting satellites. -This can range from a sequential search over all the satellites' ID to smarter approaches that determine what are the satellites most likely in-view based on rough +The GNSSFlowgraph class is responsible for preparing the graph of blocks according to the configuration, running it, modifying it during run-time and stopping it. +Blocks are identified by its role. This class knows which roles it has to instantiate and how to connect them. +It relies on the configuration to get the correct instances of the roles it needs and then it applies the connections between GNU Radio blocks to make the +graph ready to be started. The complexity related to managing the blocks and the data stream is handled by GNU Radio's gr::top_block class. GNSSFlowgraph wraps +the gr::top_block instance so we can take advantage of the \ref gnss_block_factory, the configuration system and the processing blocks. This class is also responsible +for applying changes to the configuration of the flowgraph during run-time, dynamically reconfiguring channels: it selects the strategy for selecting satellites. +This can range from a sequential search over all the satellites' ID to smarter approaches that determine what are the satellites most likely in-view based on rough estimations of the receiver position in order to avoid searching satellites in the other side of the Earth. The Control Plane is in charge of creating a flowgraph according to the configuration and then managing the modules. Configuration allows users to define in an easy way their own -custom receiver by specifying the flowgraph (type of signal source, number of channels, algorithms to be used for each channel and each module, strategies for -satellite selection, type of output format, etc.). Since it is difficult to foresee what future module implementations will be needed in terms of configuration, -we used a very simple approach that can be extended without a major impact in the code. This can be achieved by simply mapping the names of the variables in the +custom receiver by specifying the flowgraph (type of signal source, number of channels, algorithms to be used for each channel and each module, strategies for +satellite selection, type of output format, etc.). Since it is difficult to foresee what future module implementations will be needed in terms of configuration, +we used a very simple approach that can be extended without a major impact in the code. This can be achieved by simply mapping the names of the variables in the modules with the names of the parameters in the configuration. \subsection configuration Configuration -Properties are passed around within the program using the ConfigurationInterface class. There are two implementations of this interface: FileConfiguration and -InMemoryConfiguration. FileConfiguration reads the properties (pairs of property name and value) from a file and stores them internally. InMemoryConfiguration does -not read from a file; it remains empty after instantiation and property values and names are set using the set property method. FileConfiguration is intended to be -used in the actual GNSS-SDR application whereas InMemoryConfiguration is intended to be used in tests to avoid file-dependency in the file system. Classes that -need to read configuration parameters will receive instances of ConfigurationInterface from where they will fetch the values. For instance, parameters related +Properties are passed around within the program using the ConfigurationInterface class. There are two implementations of this interface: FileConfiguration and +InMemoryConfiguration. FileConfiguration reads the properties (pairs of property name and value) from a file and stores them internally. InMemoryConfiguration does +not read from a file; it remains empty after instantiation and property values and names are set using the set property method. FileConfiguration is intended to be +used in the actual GNSS-SDR application whereas InMemoryConfiguration is intended to be used in tests to avoid file-dependency in the file system. Classes that +need to read configuration parameters will receive instances of ConfigurationInterface from where they will fetch the values. For instance, parameters related to SignalSource should look like this: \verbatim @@ -266,80 +266,80 @@ SignalSource.parameter1=value1 SignalSource.parameter2=value2 \endverbatim -The name of these parameters can be anything but one reserved word: implementation. This parameter indicates in its value the name of the class that has to be instantiated -by the factory for that role. For instance, if our signal source is providing data already at baseband and thus we want to use the implementation Pass_Through for module SignalConditioner, the corresponding line in the +The name of these parameters can be anything but one reserved word: implementation. This parameter indicates in its value the name of the class that has to be instantiated +by the factory for that role. For instance, if our signal source is providing data already at baseband and thus we want to use the implementation Pass_Through for module SignalConditioner, the corresponding line in the configuration file would be \verbatim SignalConditioner.implementation=Pass_Through \endverbatim -Since the configuration is just a set of property names and values without any meaning or syntax, the system is very versatile and easily extendable. Adding new -properties to the system only implies modifications in the classes that will make use of these properties. In addition, the configuration files are not checked +Since the configuration is just a set of property names and values without any meaning or syntax, the system is very versatile and easily extendable. Adding new +properties to the system only implies modifications in the classes that will make use of these properties. In addition, the configuration files are not checked against any strict syntax so it is always in a correct status (as long as it contains pairs of property names and values in INI format). \subsection gnss_block_factory GNSS block factory -Hence, the application defines a simple accessor class to fetch the configuration pairs of values and passes them to a factory class called GNSSBlockFactory. -This factory decides, according to the configuration, which class needs to be instantiated and which parameters should be passed to the constructor. Hence, the factory -encapsulates the complexity of blocks' instantiation. With that approach, adding a new block that requires new parameters will be as simple as adding the block -class and modifying the factory to be able to instantiate it. This loose coupling between the blocks' implementations and the syntax of the configuration -enables extending the application capacities in a high degree. It also allows to produce fully customized receivers, for instance a testbed for acquisition +Hence, the application defines a simple accessor class to fetch the configuration pairs of values and passes them to a factory class called GNSSBlockFactory. +This factory decides, according to the configuration, which class needs to be instantiated and which parameters should be passed to the constructor. Hence, the factory +encapsulates the complexity of blocks' instantiation. With that approach, adding a new block that requires new parameters will be as simple as adding the block +class and modifying the factory to be able to instantiate it. This loose coupling between the blocks' implementations and the syntax of the configuration +enables extending the application capacities in a high degree. It also allows to produce fully customized receivers, for instance a testbed for acquisition algorithms, and to place observers at any point of the receiver chain. \section signal_processing Signal Processing plane -GNU Radio's class gr::basic_block is the abstract base class for all signal processing blocks, a bare abstraction of an entity that has a name and a set of -inputs and outputs. It is never instantiated directly; rather, this is the abstract parent class of both gr::hier_block2, which is a recursive container that -adds or removes processing or hierarchical blocks to the internal graph, and gr::block, which is the abstract base class for all the processing blocks. +GNU Radio's class gr::basic_block is the abstract base class for all signal processing blocks, a bare abstraction of an entity that has a name and a set of +inputs and outputs. It is never instantiated directly; rather, this is the abstract parent class of both gr::hier_block2, which is a recursive container that +adds or removes processing or hierarchical blocks to the internal graph, and gr::block, which is the abstract base class for all the processing blocks. \image html ClassHierarchy.png \image latex ClassHierarchy.png "Class hierarchy of signal processing blocks" width=12cm -A signal processing flow is constructed by creating a tree of hierarchical blocks, which at any level may also contain terminal nodes that actually implement signal +A signal processing flow is constructed by creating a tree of hierarchical blocks, which at any level may also contain terminal nodes that actually implement signal processing functions. -Class gr::top_block is the top-level hierarchical block representing a flowgraph. It defines GNU Radio runtime functions used during the execution of the -program: run(), start(), stop(), wait(), etc. A a subclass called GNSSBlockInterface is the common interface for all the GNSS-SDR modules. It defines pure virtual +Class gr::top_block is the top-level hierarchical block representing a flowgraph. It defines GNU Radio runtime functions used during the execution of the +program: run(), start(), stop(), wait(), etc. A a subclass called GNSSBlockInterface is the common interface for all the GNSS-SDR modules. It defines pure virtual methods, that are required to be implemented by a derived class. -Subclassing GNSSBlockInterface, we defined interfaces for the GNSS receiver blocks depicted in the figure above. This hierarchy provides the definition of different -algorithms and different implementations, which will be instantiated according to the configuration. This strategy allows -multiple implementations sharing a common interface, achieving the objective of decoupling interfaces from implementations: it defines a family of algorithms, encapsulates each one, +Subclassing GNSSBlockInterface, we defined interfaces for the GNSS receiver blocks depicted in the figure above. This hierarchy provides the definition of different +algorithms and different implementations, which will be instantiated according to the configuration. This strategy allows +multiple implementations sharing a common interface, achieving the objective of decoupling interfaces from implementations: it defines a family of algorithms, encapsulates each one, and makes them interchangeable. Hence, we let the algorithm vary independently from the program that uses it. \subsection signal_source Signal Source -The input of a software receiver are the raw bits that come out from the front-end's analog-to-digital converter (ADC). -Those bits can be read from a file stored in the hard disk or directly in real-time from a hardware device through USB or Ethernet buses. +The input of a software receiver are the raw bits that come out from the front-end's analog-to-digital converter (ADC). +Those bits can be read from a file stored in the hard disk or directly in real-time from a hardware device through USB or Ethernet buses. -The Signal Source module is in charge of implementing the hardware driver, that is, the portion of the code that communicates with the RF front-end and receives -the samples coming from the ADC. This communication is usually performed through USB or Ethernet buses. Since real-time processing requires a highly optimized -implementation of the whole receiver, this module also allows to read samples from a file stored in a hard disk, and thus processing without time constraints. -Relevant parameters of those samples are the intermediate frequency (or baseband I&Q components), the sampling rate and number of bits per sample, that must be +The Signal Source module is in charge of implementing the hardware driver, that is, the portion of the code that communicates with the RF front-end and receives +the samples coming from the ADC. This communication is usually performed through USB or Ethernet buses. Since real-time processing requires a highly optimized +implementation of the whole receiver, this module also allows to read samples from a file stored in a hard disk, and thus processing without time constraints. +Relevant parameters of those samples are the intermediate frequency (or baseband I&Q components), the sampling rate and number of bits per sample, that must be specified by the user in the configuration file. This module also performs bit-depth adaptation, since most of the existing RF front-ends provide samples quantized with 2 or 3 bits, while operations inside - the processor are performed on 32- or 64-bit words, depending on its architecture. Although there are implementations of the most intensive computational - processes (mainly correlation) that take advantage of specific data types and architectures for the sake of - efficiency, the approach is processor-specific and hardly portable. We suggest to keep signal samples in standard data types and letting the compiler + the processor are performed on 32- or 64-bit words, depending on its architecture. Although there are implementations of the most intensive computational + processes (mainly correlation) that take advantage of specific data types and architectures for the sake of + efficiency, the approach is processor-specific and hardly portable. We suggest to keep signal samples in standard data types and letting the compiler select the best library version (implemented using SIMD or any other processor-specific technology) of the required routines for a given processor. - + Example: FileSignalSource -The user can configure the receiver for reading from a file, setting in the configuration file the data file location, sample format, +The user can configure the receiver for reading from a file, setting in the configuration file the data file location, sample format, and the sampling frequency and intermediate frequency at what the signal was originally captured. - + \verbatim ;######### SIGNAL_SOURCE CONFIG ############ SignalSource.implementation=File_Signal_Source SignalSource.filename=/home/user/gnss-sdr/data/my_capture.dat SignalSource.item_type=gr_complex SignalSource.sampling_frequency=4000000 ; Sampling frequency in [Hz] -SignalSource.freq=1575420000 ; RF front-end center frequency in [Hz] -\endverbatim +SignalSource.freq=1575420000 ; RF front-end center frequency in [Hz] +\endverbatim Example: UhdSignalSource @@ -349,7 +349,7 @@ The user may prefer to use a UHD-compatible RF front-end and try real-time proce SignalSource.implementation=UHD_Signal_Source SignalSource.item_type=gr_complex SignalSource.sampling_frequency=4000000 ; Sampling frequency in [Hz] -SignalSource.freq=1575420000 ; RF front-end center frequency in [Hz] +SignalSource.freq=1575420000 ; RF front-end center frequency in [Hz] SignalSource.gain=60 ; Front-end gain in dB SignalSource.subdevice=B:0 ; UHD subdevice specification (for USRP1 use A:0 or B:0) \endverbatim @@ -358,8 +358,8 @@ Other examples are available at gnss-sdr/conf. \subsection signal_conditioner Signal Conditioner The signal conditioner is in charge of resampling the signal and delivering a reference sample rate to the downstream processing blocks, acting as - a facade between the signal source and the synchronization channels, providing a simplified interface to the input signal. - In case of multiband front-ends, this module would be in charge of providing a separated data stream for each band. + a facade between the signal source and the synchronization channels, providing a simplified interface to the input signal. + In case of multiband front-ends, this module would be in charge of providing a separated data stream for each band. \subsection channel Channel @@ -368,31 +368,31 @@ A channel encapsulates all signal processing devoted to a single satellite. Thus channels is selectable by the user in the configuration file, this approach helps improving the scalability and maintainability of the receiver. This module is also in charge of managing the interplay between acquisition and tracking. Acquisition can be initialized in several ways, depending on -the prior information available (called cold start when the receiver has no information about its position nor the satellites almanac; warm start when -a rough location and the approximate time of day are available, and the receiver has a recently recorded almanac broadcast; or hot start when the receiver +the prior information available (called cold start when the receiver has no information about its position nor the satellites almanac; warm start when +a rough location and the approximate time of day are available, and the receiver has a recently recorded almanac broadcast; or hot start when the receiver was tracking a satellite and the signal line of sight broke for a short period of time, but the ephemeris and almanac data is still valid, or this information -is provided by other means), and an acquisition process can finish deciding that the satellite is not present, that longer integration is needed in order to +is provided by other means), and an acquisition process can finish deciding that the satellite is not present, that longer integration is needed in order to confirm the presence of the satellite, or declaring the satellite present. In the latter case, acquisition process should stop and trigger the tracking module with coarse estimations of the synchronization parameters. The mathematical abstraction used to design this logic is known as finite state machine (FSM), that is -a behavior model composed of a finite number of states, transitions between those states, and actions. For the implementation, we used the -Boost.Statechart library, +a behavior model composed of a finite number of states, transitions between those states, and actions. For the implementation, we used the +Boost.Statechart library, which provides desirable features such as support for asynchronous state machines, multi-threading, type-safety, error handling and compile-time validation. - + The abstract class ChannelInterface represents an interface to a channel GNSS block. Check Channel for an actual implementation. - + \subsubsection acquisition Acquisition -The first task of a GNSS receiver is to detect the presence or absence of in-view satellites. This is done by the acquisition system process, which also provides a coarse estimation of two signal parameters: the frequency shift +The first task of a GNSS receiver is to detect the presence or absence of in-view satellites. This is done by the acquisition system process, which also provides a coarse estimation of two signal parameters: the frequency shift with respect to the nominal IF frequency, and a delay term which allows the receiver to create a local code aligned with the incoming code. -AcquisitionInterface is the common interface for all the acquisition algorithms and their corresponding implementations. Algorithms' interface, that may vary -depending on the use of information external to the receiver, such as in Assisted GNSS, is defined in classes referred to as adapters. -These adapters wrap the GNU Radio blocks interface into a compatible interface expected by AcquisitionInterface. This allows the use of existing GNU Radio blocks -derived from gr::block, and ensures that newly developed implementations will also be reusable in other GNU Radio-based applications. +AcquisitionInterface is the common interface for all the acquisition algorithms and their corresponding implementations. Algorithms' interface, that may vary +depending on the use of information external to the receiver, such as in Assisted GNSS, is defined in classes referred to as adapters. +These adapters wrap the GNU Radio blocks interface into a compatible interface expected by AcquisitionInterface. This allows the use of existing GNU Radio blocks +derived from gr::block, and ensures that newly developed implementations will also be reusable in other GNU Radio-based applications. Moreover, it adds still another layer of abstraction, since each given acquisition algorithm can have different implementations (for instance using different numerical libraries). In such a way, implementations can be continuously improved without having any impact neither on the algorithm interface nor the general acquisition interface. Check GpsL1CaPcpsAcquisition and GalileoE1PcpsAmbiguousAcquisition for examples of adapters from a Parallel Code Phase Search (PCPS) acquisition block, and pcps_acquisition_cc for an example of a block implementation. The source code of all the available acquisition algorithms is located at: - + \verbatim |-gnss-sdr |---src @@ -406,13 +406,13 @@ The user can select a given implementation for the algorithm to be used in each \verbatim ;######### ACQUISITION GLOBAL CONFIG ############ -;#dump: Enable or disable the acquisition internal data file logging [true] or [false] +;#dump: Enable or disable the acquisition internal data file logging [true] or [false] Acquisition.dump=false ;#filename: Log path and filename Acquisition.dump_filename=./acq_dump.dat ;#item_type: Type and resolution for each of the signal samples. Use only gr_complex in this version. Acquisition.item_type=gr_complex -;#if: Signal intermediate frequency in [Hz] +;#if: Signal intermediate frequency in [Hz] Acquisition.if=0 ;#sampled_ms: Signal block duration for the acquisition signal detection [ms] Acquisition.sampled_ms=1 @@ -420,8 +420,8 @@ Acquisition.sampled_ms=1 Acquisition.implementation=GPS_L1_CA_PCPS_Acquisition ;#threshold: Acquisition threshold Acquisition.threshold=0.005 -;#pfa: Acquisition false alarm probability. This option overrides the threshold option. -;Only use with implementations: [GPS_L1_CA_PCPS_Acquisition] or [Galileo_E1_PCPS_Ambiguous_Acquisition] +;#pfa: Acquisition false alarm probability. This option overrides the threshold option. +;Only use with implementations: [GPS_L1_CA_PCPS_Acquisition] or [Galileo_E1_PCPS_Ambiguous_Acquisition] Acquisition.pfa=0.0001 ;#doppler_max: Maximum expected Doppler shift [Hz] Acquisition.doppler_max=10000 @@ -429,7 +429,7 @@ Acquisition.doppler_max=10000 Acquisition.doppler_step=500 ;######### ACQUISITION CHANNELS CONFIG ###### -;#The following options are specific to each channel and overwrite the generic options +;#The following options are specific to each channel and overwrite the generic options ;######### ACQUISITION CH 0 CONFIG ############ @@ -455,12 +455,12 @@ Acquisition.doppler_step=500 \subsubsection tracking Tracking When a satellite is declared present, the parameters estimated by the acquisition module are then fed to the receiver tracking module, which represents the second stage of the signal processing unit, aiming to perform a local search for accurate estimates of code delay and carrier phase, and following their eventual - variations. + variations. -Again, a class hierarchy consisting of a TrackingInterface class and subclasses implementing algorithms provides a way of testing different approaches, -with full access to their parameters. Check GpsL1CaDllPllTracking or GalileoE1DllPllVemlTracking for examples of adapters, and Gps_L1_Ca_Dll_Pll_Tracking_cc for an example +Again, a class hierarchy consisting of a TrackingInterface class and subclasses implementing algorithms provides a way of testing different approaches, +with full access to their parameters. Check GpsL1CaDllPllTracking or GalileoE1DllPllVemlTracking for examples of adapters, and Gps_L1_Ca_Dll_Pll_Tracking_cc for an example of a signal processing block implementation. There are also available some useful classes and functions for signal tracking; take a look at Correlator, lock_detectors.h, tracking_discriminators.h or -tracking_2nd_DLL_filter.h. +tracking_2nd_DLL_filter.h. The source code of all the available tracking algorithms is located at: \verbatim @@ -482,10 +482,10 @@ Tracking.implementation=GPS_L1_CA_DLL_PLL_Tracking ;#item_type: Type and resolution for each of the signal samples. Use only [gr_complex] in this version. Tracking.item_type=gr_complex -;#sampling_frequency: Signal Intermediate Frequency in [Hz] +;#sampling_frequency: Signal Intermediate Frequency in [Hz] Tracking.if=0 -;#dump: Enable or disable the Tracking internal binary data file logging [true] or [false] +;#dump: Enable or disable the Tracking internal binary data file logging [true] or [false] Tracking.dump=false ;#dump_filename: Log path and filename. Notice that the tracking channel will add "x.dat" where x is the channel number. @@ -508,11 +508,11 @@ Tracking.early_late_space_chips=0.5; \endverbatim \subsubsection decoding Decoding of the navigation message -Most of GNSS signal links are modulated by a navigation message containing the time the message was transmitted, orbital parameters of satellites -(also known as ephemeris) and an almanac (information about the general system health, rough orbits of all satellites in the network as well as data related to -error correction). Navigation data bits are structured in words, pages, subframes, frames and superframes. Sometimes, bits corresponding to a single parameter are -spread over different words, and values extracted from different frames are required for proper decoding. Some words are for synchronization purposes, others for -error control an others contain actual information. There are also error control mechanisms, from parity checks to forward error correction (FEC) encoding and +Most of GNSS signal links are modulated by a navigation message containing the time the message was transmitted, orbital parameters of satellites +(also known as ephemeris) and an almanac (information about the general system health, rough orbits of all satellites in the network as well as data related to +error correction). Navigation data bits are structured in words, pages, subframes, frames and superframes. Sometimes, bits corresponding to a single parameter are +spread over different words, and values extracted from different frames are required for proper decoding. Some words are for synchronization purposes, others for +error control an others contain actual information. There are also error control mechanisms, from parity checks to forward error correction (FEC) encoding and interleaving, depending on the system. All this decoding complexity is managed by a finite state machine implemented with the Boost.Statechart library. The common interface is TelemetryDecoderInterface. Check GpsL1CaTelemetryDecoder for an example of the GPS L1 NAV message decoding adapter, and gps_l1_ca_telemetry_decoder_cc @@ -527,13 +527,13 @@ TelemetryDecoder.dump=false See the \ref reference_docs for more information about the signal format. \subsection observables Observables -GNSS systems provide different kinds of observations. The most commonly used are the code observations, also called pseudoranges. The pseudo comes from +GNSS systems provide different kinds of observations. The most commonly used are the code observations, also called pseudoranges. The pseudo comes from the fact that on the receiver side the clock error is unknown and thus the measurement is not a pure range observation. High accuracy applications also use the carrier phase observations, which are based on measuring the difference between the carrier phase transmitted by the GNSS satellites and the phase of the carrier generated in the receiver. Both observables are computed from the outputs of the tracking module and the decoding of the navigation message. This module collects all the data provided by every tracked channel, aligns all received data into a coherent set, and computes the observables. -The common interface is ObservablesInterface. +The common interface is ObservablesInterface. Configuration example: \verbatim @@ -541,7 +541,7 @@ Configuration example: ;#implementation: Use [GPS_L1_CA_Observables] for GPS L1 C/A. Observables.implementation=GPS_L1_CA_Observables -;#dump: Enable or disable the Observables internal binary data file logging [true] or [false] +;#dump: Enable or disable the Observables internal binary data file logging [true] or [false] Observables.dump=false ;#dump_filename: Log path and filename. @@ -567,24 +567,24 @@ PVT.flag_nmea_tty_port=true; ;#nmea_dump_devname: serial device descriptor for NMEA logging PVT.nmea_dump_devname=/dev/pts/4 -;#dump: Enable or disable the PVT internal binary data file logging [true] or [false] +;#dump: Enable or disable the PVT internal binary data file logging [true] or [false] PVT.dump=false \endverbatim This implementation allows tuning of the following parameters: \verbatim PVT.averaging_depth=10 ; Number of PVT observations in the moving average algorithm -PVT.flag_averaging=true ; Enables the PVT averaging between output intervals (arithmetic mean) [true] or [false] +PVT.flag_averaging=true ; Enables the PVT averaging between output intervals (arithmetic mean) [true] or [false] PVT.output_rate_ms=100 ; Period in [ms] between two PVT outputs PVT.display_rate_ms=500 ; Position console print (std::out) interval [ms]. -PVT.dump=false ; Enable or disable the PVT internal binary data file logging [true] or [false] +PVT.dump=false ; Enable or disable the PVT internal binary data file logging [true] or [false] PVT.dump_filename=./PVT ; Log path and filename without extension. \endverbatim \section license About the software license -GNSS-SDR is released under the General Public License (GPL) v3, thus securing practical usability, inspection, -and continuous improvement by the research community, allowing the discussion based on tangible code and the analysis of results obtained with real signals. +GNSS-SDR is released under the General Public License (GPL) v3, thus securing practical usability, inspection, +and continuous improvement by the research community, allowing the discussion based on tangible code and the analysis of results obtained with real signals. The GPL implies that: \li Copies may be distributed free of charge or for money, but the source code has to be shipped or provided free of charge (or at cost price) on demand. The receiver of the source code has the same rights meaning he can share copies free of charge or resell. @@ -600,8 +600,8 @@ If you use GNSS-SDR to produce a research paper or Thesis, we would appreciate i \li \anchor Navitec2012 C. Fernández-Prades, J. Arribas, L. Esteve, D. Pubill, P. Closas, An Open Source Galileo E1 Software Receiver, in Proc. of the 6th ESA Workshop on Satellite Navigation Technologies (NAVITEC 2012), ESTEC, Noordwijk, The Netherlands, Dec. 2012. \li J. Arribas, GNSS Array-based Acquisition: Theory and Implementation, PhD Thesis, Universitat Politècnica de Catalunya, Barcelona, Spain, June 2012. -\li C. Fernández-Prades, J. Arribas, P. Closas, C. Avilés, and L. Esteve, GNSS-SDR: an open source tool for researchers and developers, in Proc. of the ION GNSS 2011 Conference, Portland, Oregon, Sept. 19-23, 2011. -\li C. Fernández-Prades, C. Avilés, L. Esteve, J. Arribas, and P. Closas, Design patterns for GNSS software receivers, in Proc. of the 5th ESA Workshop on Satellite Navigation Technologies (NAVITEC'2010), ESTEC, Noordwijk, The Netherlands, Dec. 2010. DOI:10.1109/NAVITEC.2010.5707981 +\li C. Fernández-Prades, J. Arribas, P. Closas, C. Avilés, and L. Esteve, GNSS-SDR: an open source tool for researchers and developers, in Proc. of the ION GNSS 2011 Conference, Portland, Oregon, Sept. 19-23, 2011. +\li C. Fernández-Prades, C. Avilés, L. Esteve, J. Arribas, and P. Closas, Design patterns for GNSS software receivers, in Proc. of the 5th ESA Workshop on Satellite Navigation Technologies (NAVITEC'2010), ESTEC, Noordwijk, The Netherlands, Dec. 2010. DOI:10.1109/NAVITEC.2010.5707981 For LaTeX users, these are the BibTeX cites for your convenience: @@ -609,12 +609,12 @@ For LaTeX users, these are the BibTeX cites for your convenience: @INPROCEEDINGS{GNSS-SDR12 author = {C.~{Fern\'{a}ndez--Prades} and J.~Arribas and L.~Esteve and D.~Pubill and P.~Closas}, title = {An Open Source {G}alileo {E1} Software Receiver}, - booktitle = {Proc. of the 6th ESA Workshop on Satellite Navigation Technologies (NAVITEC'2012)}, - year = {2012}, - address = {ESTEC, Noordwijk, The Netherlands}, + booktitle = {Proc. of the 6th ESA Workshop on Satellite Navigation Technologies (NAVITEC'2012)}, + year = {2012}, + address = {ESTEC, Noordwijk, The Netherlands}, month = {Dec.} } \endverbatim - + \verbatim @PHDTHESIS{Arribas12, author = {J.~Arribas}, @@ -624,48 +624,45 @@ For LaTeX users, these are the BibTeX cites for your convenience: address = {Barcelona, Spain}, month = {June} } \endverbatim - + \verbatim -@INPROCEEDINGS{GNSS-SDR11, - AUTHOR = {C.~{Fern\'{a}ndez--Prades} and J.~Arribas and P.~Closas and C.~Avil\'{e}s and L.~Esteve}, - TITLE = {{GNSS-SDR}: An Open Source Tool For Researchers and Developers}, - BOOKTITLE = {Proc. of the ION GNSS 2011 Conference}, - YEAR = {2011}, - address = {Portland, Oregon}, - month = {Sept.} } +@INPROCEEDINGS{GNSS-SDR11, + AUTHOR = {C.~{Fern\'{a}ndez--Prades} and J.~Arribas and P.~Closas and C.~Avil\'{e}s and L.~Esteve}, + TITLE = {{GNSS-SDR}: An Open Source Tool For Researchers and Developers}, + BOOKTITLE = {Proc. of the ION GNSS 2011 Conference}, + YEAR = {2011}, + address = {Portland, Oregon}, + month = {Sept.} } \endverbatim - + \verbatim -@INPROCEEDINGS{GNSS-SDR10, - AUTHOR = {C.~{Fern\'{a}ndez--Prades} and C.~Avil\'{e}s and L.~Esteve and J.~Arribas and P.~Closas}, - TITLE = {Design patterns for {GNSS} software receivers}, - BOOKTITLE = {Proc. of the 5th ESA Workshop on Satellite Navigation Technologies (NAVITEC'2010)}, - YEAR = {2010}, - address = {ESTEC, Noordwijk, The Netherlands}, - month = {Dec.}, - note = {DOI:10.1109/NAVITEC.2010.5707981} } +@INPROCEEDINGS{GNSS-SDR10, + AUTHOR = {C.~{Fern\'{a}ndez--Prades} and C.~Avil\'{e}s and L.~Esteve and J.~Arribas and P.~Closas}, + TITLE = {Design patterns for {GNSS} software receivers}, + BOOKTITLE = {Proc. of the 5th ESA Workshop on Satellite Navigation Technologies (NAVITEC'2010)}, + YEAR = {2010}, + address = {ESTEC, Noordwijk, The Netherlands}, + month = {Dec.}, + note = {DOI:10.1109/NAVITEC.2010.5707981} } \endverbatim \section now_what Ok, now what? -In order to start using GNSS-SDR, you may want to populate gnss-sdr/data folder (or anywhere else on your system) with raw data files. By "raw data" we mean the output -of a Radio Frequency front-end's Analog-to_Digital converter. GNSS-SDR needs signal samples already in baseband or in passband, at a suitable intemediate frequency (on the order of MHz). +In order to start using GNSS-SDR, you may want to populate gnss-sdr/data folder (or anywhere else on your system) with raw data files. By "raw data" we mean the output +of a Radio Frequency front-end's Analog-to_Digital converter. GNSS-SDR needs signal samples already in baseband or in passband, at a suitable intemediate frequency (on the order of MHz). Prepare your configuration file, and then you are ready for going to the gnss-sdr/install folder, running ./gnss-sdr, and see how the file is processed. Please ask the Developer Team for a signal sample if you need one, and they will do their best ;-) Another interesting option is working in real-time with a RF front-end. We provide drivers for UHD-compatible hardware (see \ref signal_source), for the GN3S v2 USB dongle and for some DVB-T USB dongles. Start with a low number of channels and then increase it in order to test how many channels your processor can handle in real-time. -You can find more information at the GNSS-SDR Documentation page or directly asking to the -GNSS-SDR Developers mailing list. - -You are also very welcome to contribute to the project, there are many ways to participate in GNSS-SDR. -If you need some special feature not yet implemented, the Developer Team would love to be hired for developing it. -Please do not hesitate to contact them. +You can find more information at the GNSS-SDR Documentation page or directly asking to the +GNSS-SDR Developers mailing list. -Enjoy GNSS-SDR! +You are also very welcome to contribute to the project, there are many ways to participate in GNSS-SDR. +If you need some special feature not yet implemented, the Developer Team would love to be hired for developing it. +Please do not hesitate to contact them. + +Enjoy GNSS-SDR! The Developer Team. */ - - - diff --git a/docs/manpage/front-end-cal-manpage b/docs/manpage/front-end-cal-manpage index 13d639c57..a79ac3699 100644 --- a/docs/manpage/front-end-cal-manpage +++ b/docs/manpage/front-end-cal-manpage @@ -17,9 +17,9 @@ The crystal oscillator that ships with the RTL2832U family devices exhibits limi \fBfront\-end\-cal\fR takes the following options: .TP \fB\-config_file=\fR\fI\fR Set the configuration file. -.TP +.TP \fB\-signal_source=\fR\fI\fR If defined, path to the file containing the signal samples (overrides the data file specified in the configuration file). -.TP +.TP \fB\-log_dir=\fR\fI\fR If defined, overrides the default directory where logs are saved. .TP \fB\-version\fR Print program version and exit. @@ -32,10 +32,10 @@ Example of configuration file available at: ${prefix}/share/gnss\-sdr/conf/front \.TP [1] C. Fernandez\-Prades, J. Arribas, P. Closas, \fITurning a Television into a GNSS Receiver\fR, in Proceedings of ION GNSS+, 15\-16 September 2013, Nashville, Tennessee (USA). A draft copy is freely available at http://www.cttc.es/publication/turning\-a\-television\-into\-a\-gnss\-receiver/ \.TP -Check http://gnss\\-sdr.org for more information. +Check https://gnss\\-sdr.org for more information. .SH BUGS No known bugs. .SH AUTHOR Javier Arribas (javier.arribas@cttc.es) \.TP -This software has been developed at CTTC (Centre Tecnologic de Telecomunicacions de Catalunya, http://www.cttc.es) with contributions from around the world. \ No newline at end of file +This software has been developed at CTTC (Centre Tecnologic de Telecomunicacions de Catalunya, http://www.cttc.es) with contributions from around the world. diff --git a/docs/manpage/gnss-sdr-manpage b/docs/manpage/gnss-sdr-manpage index 997df725d..5ca98ccb7 100644 --- a/docs/manpage/gnss-sdr-manpage +++ b/docs/manpage/gnss-sdr-manpage @@ -6,7 +6,7 @@ .SH SYNOPSIS \fBgnss\-sdr \-c=\fR\fI\fR [OPTION]... .SH DESCRIPTION -\fBgnss\-sdr\fR is a Global Navigation Satellite Systems Software Defined Receiver written in C++. It implements all the signal processing chain, taking as input raw samples coming from the output of an Analog\-to\-Digital Converter, and processing them up to the computation of the Position\-Velocity\-Time solution, including the generation of code and phase measurements. +\fBgnss\-sdr\fR is a Global Navigation Satellite Systems Software Defined Receiver written in C++. It implements all the signal processing chain, taking as input raw samples coming from the output of an Analog\-to\-Digital Converter, and processing them up to the computation of the Position\-Velocity\-Time solution, including the generation of code and phase measurements. \.TP \fBgnss\-sdr\fR is able to work with raw data files or, if there is computational power enough, in real time with suitable radio frequency front\-ends. The whole receiver is defined in a single configuration file, and therefore users can define theirs. \.TP @@ -26,10 +26,10 @@ gnss\-sdr \-\-c /home/user/rx.conf .TP \fB\-c=\fR\fI\fR or \fB\-config_file=\fR\fI\fR Set the configuration file. This flag is mandatory. -.TP -\fB\-s=\fR\fI\fR or \fB\-signal_source=\fR\fI\fR +.TP +\fB\-s=\fR\fI\fR or \fB\-signal_source=\fR\fI\fR If defined, path to the file containing the signal samples (overrides the data file specified in the configuration file). -.TP +.TP \fB\-log_dir=\fR\fI\fR If defined, overrides the default directory where logs are saved. .TP @@ -43,13 +43,13 @@ If defined, sets the frequency step in the search grid, in Hz (overrides the con Number of correlators outputs (one per integration time) used for CN0 estimation. It defaults to 20 outputs. .TP \fB\-cn0_min=\fR\fI\fR -Minimum valid CN0 (in dB-Hz). It defaults to 25 dB-Hz. +Minimum valid CN0 (in dB-Hz). It defaults to 25 dB-Hz. If set, it overrides the configuration file. .TP \fB\-max_lock_fail=\fR\fI\fR -Number of lock failures before dropping satellite. It defaults to 50 failures. +Maximum number of lock failures before dropping a satellite. It defaults to 50 failures. If set, it overrides the configuration file. .TP \fB\-carrier_lock_th=\fR\fI\fR -Carrier lock error threshold (in rad). It defaults to 0.85 rad (48.7 degrees). +Carrier lock error threshold (in rad). It defaults to 0.85 rad (48.7 degrees). If set, it overrides the configuration file. .TP \fB\-dll_bw_hz=\fR\fI\fR If defined, bandwidth of the DLL low pass filter, in Hz (overrides the configuration file). @@ -70,10 +70,10 @@ Print all the available commandline flags and exit. \.TP Examples of configuration files available at: ${prefix}/share/gnss\-sdr/conf, where ${prefix} uses to be /usr or /usr/local. \.TP -Check http://gnss\-sdr.org for more information. +Check https://gnss\-sdr.org for more information. .SH BUGS Please report bugs at https://github.com/gnss-sdr/gnss-sdr/issues .SH AUTHOR Carles Fernandez\-Prades (carles.fernandez@cttc.es) \.TP -This software package has been developed at CTTC (Centre Tecnologic de Telecomunicacions de Catalunya, http://www.cttc.es) with contributions from around the world. \ No newline at end of file +This software package has been developed at CTTC (Centre Tecnologic de Telecomunicacions de Catalunya, http://www.cttc.es) with contributions from around the world. diff --git a/src/algorithms/PVT/libs/rinex_printer.cc b/src/algorithms/PVT/libs/rinex_printer.cc index fa6b1296c..e5dc5c65f 100644 --- a/src/algorithms/PVT/libs/rinex_printer.cc +++ b/src/algorithms/PVT/libs/rinex_printer.cc @@ -415,7 +415,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Glonass_Gnav_Utc_M // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -524,7 +524,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Gps_Iono& gps_iono // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -648,7 +648,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Gps_CNAV_Iono& gps // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -774,7 +774,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Galileo_Iono& gali // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -881,7 +881,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Galileo_Iono& iono // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -987,7 +987,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Gps_CNAV_Iono& ion // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -1116,7 +1116,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Gps_Iono& iono, co // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -1280,7 +1280,7 @@ void Rinex_Printer::rinex_nav_header(std::fstream& out, const Gps_Iono& gps_iono // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -1463,7 +1463,7 @@ void Rinex_Printer::rinex_sbs_header(std::fstream& out) // -------- Line COMMENT 2 line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -3277,7 +3277,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Glonass_Gnav_Ephem // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -3599,7 +3599,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Gps_Ephemeris& gps // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -3952,7 +3952,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Gps_CNAV_Ephemeris // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -4270,7 +4270,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Galileo_Ephemeris& // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -4590,7 +4590,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Gps_Ephemeris& eph // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -4844,7 +4844,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Gps_CNAV_Ephemeris // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -5056,7 +5056,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Gps_Ephemeris& eph // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -5282,7 +5282,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Galileo_Ephemeris& // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; @@ -5546,7 +5546,7 @@ void Rinex_Printer::rinex_obs_header(std::fstream& out, const Gps_Ephemeris& gps // -------- Line COMMENT line.clear(); - line += Rinex_Printer::leftJustify("See http://gnss-sdr.org", 60); + line += Rinex_Printer::leftJustify("See https://gnss-sdr.org", 60); line += Rinex_Printer::leftJustify("COMMENT", 20); Rinex_Printer::lengthCheck(line); out << line << std::endl; diff --git a/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/README.md b/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/README.md index 3b5e14513..f37cc5b35 100644 --- a/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/README.md +++ b/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/README.md @@ -20,10 +20,10 @@ sets. Then, the application ```volk_gnsssdr_profile``` runs some iterations of all versions that your machine can execute and annotates which is the fastest, which will then be selected at runtime when executing GNSS-SDR. In this way, we can address at the same time -[portability](http://gnss-sdr.org/design-forces/portability/) (by +[portability](https://gnss-sdr.org/design-forces/portability/) (by creating executables that will run in nearly all processor architectures) and -[efficiency](http://gnss-sdr.org/design-forces/efficiency/) (by +[efficiency](https://gnss-sdr.org/design-forces/efficiency/) (by providing custom implementations specially designed to take advantage of the specific processor that is running the code). @@ -44,21 +44,21 @@ independently of GNSS-SDR. First, make sure that the required dependencies are installed in your machine: -~~~~~~ +~~~~~~ $ sudo apt-get install cmake python-mako python-six libboost-dev \ libboost-filesystem-dev libboost-system-dev -~~~~~~ +~~~~~~ In order to build and install the library, go to the base folder of the source code and do: -~~~~~~ +~~~~~~ $ mkdir build $ cd build $ cmake .. $ make $ sudo make install -~~~~~~ +~~~~~~ That's it! @@ -66,7 +66,7 @@ Before its first use, please execute ```volk_gnsssdr_profile``` to let your system know which is the fastest available implementation. This only has to be done once: -~~~~~~ +~~~~~~ $ volk_gnsssdr_profile ~~~~~~ diff --git a/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr-config-info-manpage b/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr-config-info-manpage index be69e4aba..48de3376a 100644 --- a/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr-config-info-manpage +++ b/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr-config-info-manpage @@ -33,8 +33,8 @@ This program prints configuration information for the Vector-Optimized Library o .BR volk_gnsssdr_profile (1) .BR gnss-sdr (1) \.TP -Check http://gnss-sdr.org for more information. +Check https://gnss\-sdr.org for more information. .SH BUGS No known bugs. .SH AUTHOR -Carles Fernandez-Prades (carles.fernandez@cttc.es) \ No newline at end of file +Carles Fernandez-Prades (carles.fernandez@cttc.es) diff --git a/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr_profile-manpage b/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr_profile-manpage index 159bbfee1..186bcb9c9 100644 --- a/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr_profile-manpage +++ b/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/cmake/Packaging/volk_gnsssdr_profile-manpage @@ -10,7 +10,7 @@ The Vector-Optimized Library of Kernels of GNSS-SDR (VOLK_GNSSSDR) is a software .TP Processors providing SIMD instruction sets compute with multiple processing elements that perform the same operation on multiple data points simultaneously, thus exploiting data-level parallelism, an can be found in most modern desktop and laptop personal computers. In a nutshell, VOLK_GNSSSDR implements in assembly language optimized versions of computationally-intensive operations for different processor architectures that are commonly found in modern computers. In order to use the most optimized version for the specific processor(s) of the host machine running the software receiver (that is, the implementation than runs the fastest). .TP -\fBvolk_gnsssdr_profile\fR is a program that tests all known VOLK_GNSSSDR kernels (that is, basic processing components like adders, multipliers, correlators, and much more) for each architecture supported by the host machine, measuring their performance. When finished, the profiler writes to $HOME/.volk_gnsssdr/volk_gnsssdr_config the best architecture for each VOLK_GSSSDR function. This file is read when using a function to know the best version to execute. +\fBvolk_gnsssdr_profile\fR is a program that tests all known VOLK_GNSSSDR kernels (that is, basic processing components like adders, multipliers, correlators, and much more) for each architecture supported by the host machine, measuring their performance. When finished, the profiler writes to $HOME/.volk_gnsssdr/volk_gnsssdr_config the best architecture for each VOLK_GSSSDR function. This file is read when using a function to know the best version to execute. .SH OPTIONS \fBvolk_gnsssdr_profile\fR takes the following options: .TP @@ -34,7 +34,7 @@ Processors providing SIMD instruction sets compute with multiple processing elem .SH SEE ALSO .BR gnss-sdr (1) \.TP -Check http://gnss-sdr.org for more information. +Check https://gnss\-sdr.org for more information. .SH HISTORY This library was originally developed by Andres Cecilia Luque in the framework of the Summer of Code in Space program (SOCIS 2014) by the European Space Agency (ESA), and then integrated into \fBgnss-sdr\fR. This software is based on the VOLK library http://libvolk.org/ .SH BUGS @@ -42,4 +42,4 @@ No known bugs. .SH AUTHOR Andres Cecilia Luque (a.cecilia.luque@gmail.com) \.TP -Carles Fernandez-Prades (carles.fernandez@cttc.es) \ No newline at end of file +Carles Fernandez-Prades (carles.fernandez@cttc.es)