Hi all,
I have developed a basic LTE scenario as part of my effort to become proficient with the ns3 framework. In this scenario, I established a setup consisting of 20 User Equipment (UE) nodes and a single evolved NodeB (eNB) node. Additionally, I created two distinct applications to simulate different scenarios. To manage the scheduling behavior, I employed the following code snippet: `Ptr lteHelper = CreateObject(); lteHelper1->SetSchedulerType("ns3::CqaFfMacScheduler");` I also utilized the Flow Monitor tool to monitor the progress of data flows during the simulation. After running the simulation, I recorded pertinent information regarding throughput and fairness for the various flows. I then repeated the process, this time using the PfScheduler. In a subsequent step, I introduced a function to dynamically alter the scheduler type during the simulation. Through the use of Log statements, it became evident that the scheduler type was indeed changing as intended within the `lteHelper` instance. Curiously, despite the apparent change in the scheduler type to PfScheduler, the observed results continued to correspond to those produced by the CqaFfMacScheduler. In another attempt to modify the simulation behavior, I added attributes (Alpha, Beta, and Gama) to the Cqa Scheduler. I also created a function to change the values of these attributes to specific values. However, similar to the scheduler type change, although I could see the attribute values changing using Log statements, the final outcomes with respect to throughput and fairness persisted as if the default attribute values were still in effect. The situation has left me quite perplexed, as the simulation appears to be disregarding the changes I've introduced to the scheduler type and attributes, despite indications from Log statements that these changes are indeed being made. I would greatly appreciate any assistance or insights that can help me better comprehend and resolve this issue.
Best regards,
