Multiple Inconsistencies Between Configuration Reference and Valid Configurations

[jfchoquette]

Hello,

Thank you all for maintaining such detailed and comprehensive documentation for the srsRAN project. I would like to raise a concern about incorrect documentation for the configuration reference.

I have an existing issue for a discrepancy with the "ru_mac_address" and "du_mac_address" fields, but I have noticed another incorrectly documented field.

The "expert_execution.affinities.isolated_cpus" documentation lists the accepted format as "[1, 2, 3 , ..., N]".
However, this will fail to validate as the correct format is actually "1,2,3,...,N" (without brackets).

I do remember seeing a disclaimer about the reference not being 100% accurate due to the fact that it is manually updated, but this is not mentioned on the reference page. At the time of writing I cannot locate that disclaimer.

I just wanted to make the community aware of this discrepancy and potentially open a dialogue on how to better keep the configuration reference in sync with the code base.

[mdsahazan]

01717853529

…

On Wed, 3 Sept 2025, 3:32 am Justin Choquette, ***@***.***> wrote: Hello, Thank you all for maintaining such detailed and comprehensive documentation for the srsRAN project. I would like to raise a concern about incorrect documentation for the configuration reference <https://docs.srsran.com/projects/project/en/latest/user_manuals/source/config_ref.html> . I have an existing issue <#1334> for a discrepancy with the "ru_mac_address" and "du_mac_address" fields, but I have noticed another incorrectly documented field. The "expert_execution.affinities.isolated_cpus" documentation lists the accepted format as "[1, 2, 3 , ..., N]". However, this will fail to validate as the correct format is actually "1,2,3,...,N" (without brackets). I do remember seeing a disclaimer about the reference not being 100% accurate due to the fact that it is manually updated, but this is not mentioned on the reference page. At the time of writing I cannot locate that disclaimer. I just wanted to make the community aware of this discrepancy and potentially open a dialogue on how to better keep the configuration reference in sync with the code base. — Reply to this email directly, view it on GitHub <#1344>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BUXNJGEDKHJ2L5SSF2LN57T3QYEGXAVCNFSM6AAAAACFOSBQPCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYHAZTGMBVG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>