# The megatrend taxonomy lives in two repositories, and only one of them is this one > mathworks/MATLAB-Simulink-Challenge-Project-Hub is a catalogue rather than code: a generated HTML table of industry-backed project ideas, a filterable explorer, and a project directory per entry. Its two most important rules are stated plainly, a generative AI guideline whose breach is grounds for rejection, and an openness requirement attached to the certificate. **mathworks/MATLAB-Simulink-Challenge-Project-Hub** — This MATLAB and Simulink Challenge Project Hub contains a list of research and design project ideas. These projects will help you gain practical experience and insight into technology trends and industry directions. - Repository: https://github.com/mathworks/MATLAB-Simulink-Challenge-Project-Hub - Stars: 2,206 · Forks: 420 - Language: HTML - License: NOASSERTION - Published: 2026-09-10 · Updated: 2026-09-10 · Language: en - Canonical page: https://hysenlabs.com/projects/mathworks-matlab-simulink-challenge-project-hub ## The ten trend files are served from a different repository The categories the projects are organised by are listed as ten named technology trends: artificial intelligence, autonomous vehicles, big data, computer vision, computational finance, drones, industry four point zero, robotics, sustainability and renewable energy, and wireless communication. Every one of those ten links points somewhere other than this repository. Each is a markdown file in a separate repository, under a directory called megatrends, fetched from a blob path on its main branch. Meanwhile this repository has its own megatrends directory at the root. So the taxonomy that the whole catalogue is filed under exists in two places at once, one of them not in this repository, and nothing in the document says which is the source of truth or how they are kept in step. If you are filtering the project list by trend, you are filtering against a name that resolves somewhere else, and a reader working only from a clone has a directory that may not be the one the links use. ## The generative AI rule is a rejection criterion rather than advice One line in the participation section carries more weight than the rest of the page, and it is set in bold. It asks you to read the generative AI guidelines before starting your project, and states that submissions with unverified, misunderstood, or misused AI-generated work will not be accepted. That is three separate grounds in one sentence: work that is unverified, work that was misunderstood, and work that was misused. The bar is therefore not about whether a model was involved but about whether the result stands up, and the document attaches the consequence directly to the submission rather than to a review stage. The guidelines themselves live on the project wiki, so the rule is one click from the sentence that states it, and any participant weighing how to use a model during a MATLAB or Simulink project has to treat that page as part of the terms rather than as a suggestion. ## The catalogue is a generated table with a hand written update date The project list is not a data file you can read. It is an HTML table pasted into the readme, and the markup gives itself away: there is a comment placeholder, a body, an empty cell, and then one heading, description, impact line, expertise line, and industry partner per project. That is generated output committed into a markdown file, and the generation is not described anywhere in the repository. The filtering alternative is a separate page, a hosted explorer where you can search and filter by technology, application area, and the specific MATLAB and Simulink tools involved, which implies a structured source that the table does not show. Above the table there is a single line carrying a date, updated October 2, 2026, which is the same day as the most recent commit. One date for the whole table means you cannot tell which entries are current and which have not been revisited since the list was last regenerated. ## A 2024 challenge with a stated prize is still in the source, commented out Two blocks of the readme are wrapped in HTML comments, and both are worth reading because they show what the file used to carry. The first wraps an announcements table with two cells, one inviting you to host your own custom challenge and one inviting industry partners to co-develop a challenge project, both linking into an announcements wiki page and both with a follow-on link to the custom competitions page. The second wraps a challenge announcement from 2024, the sustainability and renewable energy challenge, describing a second edition after an inaugural one, inviting you to build on previous submissions provided you add enough personal contribution for the work to be considered novel and highlight those contributions in the documentation, and stating a prize of up to a thousand dollars. That is a useful set of submission rules sitting in a comment in a file whose current version does not mention them, and the practical effect is that the live rules for that challenge are somewhere other than here. ## Every signup link carries the project name and a numeric tracking code The first entry in the table is a worked example of the structure each project follows. It is titled as an analysis of oil and gas fatal incident reports, and the task is to turn published fatal incident reports into structured data and visualisations and then use AI to classify accidents as either human acts or process design. The impact statement ties it to making the evidence align safety remedies with their real causes, the expertise gained is listed as artificial intelligence, text analytics, and natural language processing, and an industry partner is named with its own site link. Then there are two calls to action per project, and both are links to the same sign-up page with the project title and a numeric code appended as query parameters. So the catalogue tracks which project brought you in, which is sensible for a programme, and it also means every project link in the table is unique and long enough that the structure of the page is machine generated. ## The certificate is tied to making your results open The participation section is short and its condition is easy to skim past. It asks you to make the results of your work open and accessible in order to receive a certificate and endorsements from MathWorks research leads, and then describes the mechanism: you signal intent to complete a project through the sign-up form on that project's description page, and the organisers send more information about the project and about the recognition awards. So the reward is not a prize for a good result but recognition for visible work, and openness is the entry condition rather than a bonus. There is a second line about prizes, but it points at the regular contests run by the MATLAB Central community rather than at this programme, which is worth separating from the certificate route so the two are not confused. ## The licence field is unresolved and the licence file is named license.txt The machine readable licence for this repository is unasserted, and there is a licence file at the root with a lowercase name. Nothing visible in the document resolves which terms apply or which source to trust, so the two disagree and neither is identified as authoritative. For a catalogue whose main purpose is to be read and reused, that is the wrong detail to leave open, and it sits alongside a small structural oddity worth noting: the root also contains a directory with a capitalised, space separated name for classroom challenge projects, which is the only path in the tree that will need quoting in any tooling, plus a single standalone HTML file that is the table the readme links to as the explorer. The security policy file is present at the root, which is the one piece of governance paperwork that is unambiguous. ## Conclusion This fits a student or a team that wants a scoped engineering problem with a named industry partner and a defined set of tools to practise on, rather than a project to invent. It is a list, not a framework, and there is nothing to install. Check four things. The generative AI guideline, which is linked before you start and which makes unverified or misused generated work a reason for rejection rather than a note in the documentation. Whether you are willing to make results open, since the certificate and the endorsements from research leads are tied to that. Which megatrend document you are following, because the ten trend files are served from a different repository than the one hosting the project list, so a local copy can drift. And whether the entry is current, since the table carries a written update date rather than a per-project revision, and a 2024 challenge is still present in the source, commented out. ## FAQ ### What is the MATLAB and Simulink Challenge Project Hub? A catalogue of research and design project ideas, each with a description, an impact statement, the expertise it develops, and often a named industry partner. It is a list of project briefs rather than a library or framework, and there is nothing to install. ### Can I use generative AI on a MathWorks challenge project? The project asks you to read its generative AI guidelines before starting, and states that submissions with unverified, misunderstood, or misused AI-generated work will not be accepted. The guidelines themselves are on the project wiki. ### What do I get for completing a challenge project? A certificate and endorsements from MathWorks research leads, and you signal your intent through the sign-up form on the project's description page, after which the organisers send more about the project and the recognition awards. Making your results open and accessible is the condition attached to receiving them. ### How are the challenge projects categorised? By ten technology trends, from artificial intelligence and autonomous vehicles through computational finance, drones, industry four point zero, robotics, sustainability and renewable energy, and wireless communication. Each trend links to a markdown file in a separate repository, even though this repository also has a megatrends directory. ### How do I filter or search the challenge projects? Through a hosted interactive explorer where you can search and filter by technology, application area, and the MATLAB and Simulink tools involved. The full list in the repository is a generated HTML table with a single written update date above it. ## Sources - [Issues](https://github.com/mathworks/MATLAB-Simulink-Challenge-Project-Hub/issues) - [mathworks/MATLAB-Simulink-Challenge-Project-Hub on GitHub](https://github.com/mathworks/MATLAB-Simulink-Challenge-Project-Hub) - [README](https://github.com/mathworks/MATLAB-Simulink-Challenge-Project-Hub/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/mathworks-matlab-simulink-challenge-project-hub