I'd like to extend my gratitude to @Zindi and the ambassadors from ITU (@ITU_Challenge) and Huawei (@AntonioDeDomenico) for organizing this captivating competition. Congratulations to all participants for their remarkable efforts.
With my work now submitted for code review, I'm eagerly awaiting a positive outcome. This seems like the ideal opportunity to offer a glimpse into my approach to solving the problem.
Despite my best efforts to share my solution through discussion, I've encountered a recurring "Compilation Error" every time I attempt to publish. As a result, I invite you to explore my approach here https://docs.google.com/document/d/1Qxjxs7RIro_jm9gQSOb3-6NOPYMnDUde1kgeVTohAqc/edit?usp=sharing. Enjoy the read!
Wow @JuliusFx quite something, and I think, some ingredients of your secret sauce, is the interactions. I mean
is inspirational, how did you come up with that?
It measured the difference between the actual data rate achieved during transmission and the data rate that would be expected based on the chosen MCS. The difference provides insights into the efficiency of the communication channel, including factors such as interference, noise, and signal quality where If the difference is large, it might indicate that the wireless link is not performing as expected due to various conditions in the environment.
hmmmmm, what can I say, its like you are taking me back to school ... perhaps I can say this: no wonder you are so high up on the lb ...
Haha, it was more of a trial-and-error approach rather than a stroke of genius, to be honest.. I did have a bit more time to experiment compared to you, as I joined the competition earlier. I noticed your efforts to select the best submission in the final hours of the competition, but unfortunately, the system jammed and couldn't score your submission in time. I understand how frustrating that can be.
I really enjoyed this "speed-chess" like approach, but I can also see it won't really work, not with the kind of competition we have :-) You have to really get a good grip on the data and the problem and then use some ML technique really well to make a dent in the LB.
The LB jamming in the final hour ... I had a ton of models that ran on the last day and was going to submit two and based on their public score would decide which variations to submit and then make a final selection. Now with hindsight it is impossible to know what I would have done.
Do you have any suggestions on how to fix this? What is fair? What should zindi do? One solution is to rerun the whole competition but that is not feasable - do you have any idea how to resolve this?
Sometimes I notice this behavior while submitting for other competitions too, even when the submission files are small in size. However, the issue usually gets resolved within a few minutes, and then the submission is scored. My assumption is that they might be improving their server capacities.. maybe..
Nice approach @JuliusFx. Congratulations on your win!
Thanks proff