Your answer gets reviewed by the program mentors and they decide if the answer fulfills the requirements specified in the question. However, for your work to be perceived as the content worth publishing and endorsing through Typhoon HIL/HIL Academy web pages and marketing channels, it really needs to stand out. For that reason we would like you to get a clear understanding of the review process in the context of publishing. Also we are providing a list of quality examples of authored content so that you can get a feel for what it takes to get published.
Review processAuthor submits the files for review | Mandatory files: Schematic Editor (.tse), HIL SCADA (.cus), written content draft (template will be supplied to you depending on the type, i.e. application note, white paper, etc.) Optional files: Model Settings (.runx), TyphoonTest scripts (.py), libraries (.tlib, wlib), Package Manager (.tpkg) ( 3rd party software files required to run the example (if any). Some of the optional files may be specified mandatory depending on the requirements. Endorsement credits: Personal/organization/project information that will be featured in published content and marketing channels. |
General review | Typhoon HIL reviews the model for functionality according to requirements stated in the question. This includes how the model performs in real-time so testing it on a HIL device will be done. Besides functionality tests, the originality and novelty of application will be reviewed relative to what is already published. |
| Schematic Editor | If the model is accepted after the general review, Typhoon HIL may request the author to make changes primarily in accordance with best practices of creating model in Schematic Editor. |
| HIL SCADA | If the model is accepted after general review, Typhoon HIL may request the author to make changes primarily in accordance with best practices of HIL SCADA design. |
| TyphoonTest script | Writing an automated test for your application is not essential for the publishing process, unless required. However, if you want to put test automation on your verified skills list, or the application emphasis is on automated testing, then an automated test must be included. |
| Written content | Written content will be reviewed both for domain-specific accuracy and quality of technical writing style. |
| Package Manager | If you decide to publish your work as a package it needs to be able to install successfully and all actions of package manipulation must be functional. |
Here are some representative content examples:
Welding inverter
IEEE 34 node islanding with implemented Artificial Neural Network (ANN)
Distance protection relay with false tripping prevention
Electric vehicle charging according to standard IEC62196 – mode 3
Dynamic voltage restorer
Heart model
Quadcopter drone
Hybrid train
Feel free to also browse all the application notes and try out some packages on HIL Marketplace to get a better feel for the expectations.
