An error occurred fetching the project authors.
  1. 07 Dec, 2023 1 commit
  2. 29 Nov, 2023 1 commit
  3. 28 Nov, 2023 2 commits
  4. 03 Nov, 2023 1 commit
  5. 10 Oct, 2023 1 commit
  6. 06 Oct, 2023 1 commit
  7. 29 Sep, 2023 1 commit
  8. 25 Sep, 2023 5 commits
  9. 04 Sep, 2023 1 commit
  10. 10 Jul, 2023 1 commit
  11. 12 Jun, 2023 1 commit
  12. 15 May, 2023 1 commit
    • Raymond Knopp's avatar
      Add new parameter tx_amp_backoff_dB to L1 section of configuration file · 139cdc0d
      Raymond Knopp authored
      Provides the backoff from full-scale output at the L1 entity
      (frequency-domain samples). Default is, 36 dBFS, which is the correct
      value when using the OAI RU entity. For O-RAN RU, this value should be
      set according to the O-RU manufacturer requirements. For example 12
      would corresponding to 14-bit input level (6 dB/bit).
      
      Applies the TX amp backoff to PBCH, PDCCH and CSI
      139cdc0d
  13. 19 Apr, 2023 2 commits
  14. 17 Apr, 2023 1 commit
  15. 05 Apr, 2023 1 commit
    • Cedric Roux's avatar
      bugfix: change memory management of interface between PHY and MAC scheduler · 733c7e5e
      Cedric Roux authored
      This commit fixes a bug caused by global variables in the gNB_MAC_INST
      structure used to transfer MAC scheduler's results to the PHY layer.
      
      When using several threads in the PHY layer, it may happen that the
      MAC scheduler is called a second time by the second PHY thread for the
      next slot before the content of the global variables in the gNB_MAC_INST
      structure used to store the result of the MAC scheduler for the current
      slot have been consumed by the first thread, leading to unpredictable
      results (all of them certainly wrong).
      
      The solution is to introduce a small memory management module for the
      interface between the PHY threads and the MAC scheduler. The MAC
      scheduler now fills the data structures passed to it, and not a
      global variable anymore. The PHY layer manages the structures and
      ensures that no data is overwritten before being fully consumed by
      the various threads of the PHY layer.
      
      Some care has to be taken because several PHY threads will access the
      same structures at the same time for a given slot (in read mode, so
      it's okay). A mechanism of reference counting has thus been introduced.
      
      Only one CC is supported. This restriction should not be too hard
      to remove if/when needed. (The code before this commit does not seem
      to work for more than one CC anyway.)
      733c7e5e
  16. 27 Mar, 2023 5 commits
  17. 23 Mar, 2023 1 commit
    • Cedric Roux's avatar
      bugfix: LDPC decoding in the gNB: clear d properly · a4718d4a
      Cedric Roux authored
      The d array has to be cleared at the first usage, which may not necessarily
      be when new_rx is true. For example, in case of DTX detected for a first
      transmission, the next transmission won't have new_rx true, so d won't be
      cleared, containing data from a previous transmission. Or when a LDPC
      decoding is cancelled for a segment when new_rx is true, a decoding for
      a retransmission will not clear d because then new_rx will not be true.
      (Yes, the logic of cancellation will be changed in the future, but the
      changes will be orthogonal to the ones of this commit.)
      
      new_rx is removed.
      a4718d4a
  18. 15 Mar, 2023 1 commit
    • Melissa Elkadi's avatar
      int32_t to c16_t conversion · 4dd579e0
      Melissa Elkadi authored
      This commit includes changes to the function
      footprints for vaiours NR UE and gNB functions.
      It does not updated the LTE code. For functions
      shared by both LTE and 5G, we maintained the original
      LTE footprint and argument structure.
      
      Several of the simulators that use these functions
      have been updated as well. The specific usage of these
      functions which index into the int32_t buffers and
      treat the first int16_t and the real and the second
      as the complex should be modified in the near future.
      4dd579e0
  19. 07 Mar, 2023 1 commit
  20. 06 Mar, 2023 1 commit
  21. 21 Feb, 2023 1 commit
  22. 23 Jan, 2023 5 commits
  23. 23 Dec, 2022 1 commit
  24. 23 Nov, 2022 1 commit
  25. 11 Nov, 2022 1 commit
  26. 29 Oct, 2022 1 commit