Hi Vuk,
The main question is - will this change help you get a working LTE code faster? If not, I strongly encourager you postpone this polishing to some later time and focus on your LTE target.
Unlike academia, in the real world the only thing which matters is "working code now". A perfect code which didn't exist yet is equivalent to no code at all. That's one of the reasons why "Release early, release often" works so well.
Sent from my Android device.
--
Regards,
Alexander Chemeris
CEO, Fairwaves LLC
http://fairwaves.ru
--
You received this message because you are subscribed to the Google Groups "ALOE" group.
To post to this group, send email to flex...@googlegroups.com.
To unsubscribe from this group, send email to flexnets+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Alexander,
Thanks for getting back to us on this. We appreciate you feedback.
We're developing LTE, which is our primer focus, while improving ALOE. We analyzed our framework and decided to recreate it for many reasons. ALOE++ will simply waveform design and deployment. It is necessary not (only) for optimization reasons, which is one important point of the ALOE concept, but rather for community building and encouraging external contributions. In any case, we'll have to postpone the development of most part of ALOE++ to some later stage as you suggest.
Thanks again for your feedback. Hope to hear from you soon again.