TACO 1.0 is linked or mirrored on JoeF’s archives, kPower’s site, and official FAA AWES content.
People who ignore acronyms are just not the same folks for whom they are useful. If always spelled out, why bother using them? Consult JoeF’s AWE archives for comprehensive disambiguation.
Providing AWE links cannot be preemptively optimized, as the ignorance of AWE facts varies from person to person. Requested links are therefore provided as convenient to the sharer (may take a day or two, even a reminder).
Sorry this thread became the acronym-complaint place.
Acronyms are also used to speed communication in an informed community. Wubbo would not have been allowed to be astronaut if he did not master the acronyms required.
A rule not allowing acronyms unless defined would exclude free expression, like Pierre using “IMHO” on this Forum.
This is not that community. We are here to learn and share, not to try to search for obscure acronyms. That only frustrates.
IMHO is a common acronym used outside of a very small community. You can edit the wiki, add the terms you like, and maybe use a script to edit your posts to put them in a footnote every time you use an acronym. So it does limit your speech, but you can work around that by doing a little work as a courtesy to your reader, where now you do too little, IMHO.
We have discussed this for longer already than it would have taken you to write out the acronyms you use.
It would take long time to redefine all AWES acronyms in common use by the serious AWE community, not just the first few. These terms have all been defined in our academic literature and the Old Forum.
We are also talking about the time required to forever enforce a no-aconyms-unless-defined rule.
If someone uses an acronym like “AWESCO”, at least most of us understand, and do not bother arguing the user should spell it out.
By “redefine” here, I mean “define twice” not “change the definition”. Let my TACO 1.0 acronym glossary stand as the current best effort. Anyone who wants can mine the literature for more.
AWESCO is the TUDelft-led program to train PhDs in AWE. If I knew who you are, Windy Skies, it would help me judge your request that I do further work for you.
It takes work to express oneself clearly. If you want to be understood and people to read your text, I recommend not pushing that effort onto the readers.
Thanks, but I am resigned to not be understood by all, just as anyone who does not understand English cannot understand you here. I do not ask you to explain English.
I have been independently developing an airborne HAWT for the last several years now, and had been thinking about doing that for a long time before that, but could not think of solutions to some problems I saw.
I am interested in learning more about engineering, physics, and math so that I can more effectively develop my product. Study of obscure acronyms has no place in this.
I have lurked the old forum since early on, and have always been frustrated with your lack of communication skills. At the same time, I did get some ideas from it, mostly from @JoeFaust linking content, and it has helped keep up my interest in the subject.
You can use as many acronyms as you want. I just recommend using as few as possible.
It’s not a problem as long as others aren’t bothered by posts in their threads which can’t be understood.
