Tracking categories

Flight chamber

A Flight Chamber serves as a bridge between the world of aviation research and adrenaline-packed recreation. Historically rooted in aerodynamic testing, wind tunnels were conceived to study the complex interactions between airflow and objects. However, as technology advanced and human curiosity grew bolder, the concept of utilizing these tunnels for human interaction was realized, leading to the creation of the flight chamber. This specialized segment of a wind tunnel is meticulously designed to simulate the exhilarating conditions of freefall.

View More

Turning vanes

In the heart of aerodynamic testing lies the challenge of managing airflow. Turning vanes in wind tunnels are our solution, often referred to as "corner vanes." Their primary function is to direct the airflow seamlessly, especially around potential disruption zones, like corners. Wind tunnels play a pivotal role in industries such as aerospace and automotive design, acting as bridges between concept and real-world functionality. Testing in this environment ensures that designs, like those of prototype aircraft or automobiles, interact optimally with flowing air.

View More
Jump to navigation Jump to search

This page lists tracking categories which are automatically populated by the MediaWiki software. Their names can be changed by altering the relevant system messages in the MediaWiki namespace.

Tracking category Message name Category inclusion criteria
Pages with broken file linksbroken-file-categoryThe page contains a broken file link (a link to embed a file when the file does not exist).
Pages using duplicate arguments in template callsduplicate-args-categoryThe page contains template calls that use duplicates of arguments, such as {{foo|bar=1|bar=2}} or {{foo|bar|1=baz}}.
Pages where expansion depth is exceededexpansion-depth-exceeded-categoryThe page exceeds the maximum expansion depth.
Pages with too many expensive parser function callsexpensive-parserfunction-categoryThe page uses too many expensive parser functions (like #ifexist). See Manual:$wgExpensiveParserFunctionLimit.
Hidden categorieshidden-category-categoryThe category contains __HIDDENCAT__ in its page content, which prevents it from showing up in the category links box on pages by default.
Indexed pagesindex-categoryThe page has a __INDEX__ on it (and is in a namespace where that flag is allowed), and hence is indexed by robots where it normally wouldn't be.
Pages where node count is exceedednode-count-exceeded-categoryThe page exceeds the maximum node count.
Noindexed pagesnoindex-categoryThe page is not indexed by robots because it has the magic word __NOINDEX__ on it and is in a namespace where that flag is allowed.
Pages with non-numeric formatnum argumentsnonnumeric-formatnumThe page contains a non-numeric argument to the formatnum parser function.
Pages containing omitted template argumentspost-expand-template-argument-categoryThe page is bigger than $wgMaxArticleSize after expanding a template argument (something in triple braces, like {{{Foo}}}).
Pages where template include size is exceededpost-expand-template-inclusion-categoryThe page size is bigger than $wgMaxArticleSize after expanding all the templates, so some templates were not expanded.
Pages with ignored display titlesrestricted-displaytitle-ignoredThe page has an ignored {{DISPLAYTITLE}} because it is not equivalent to the page's actual title.
Pages which use = as a templatetemplate-equals-categoryThe page contains {{=}} but on this wiki that does not expand to =. This usage is deprecated; a future MediaWiki version will implement {{=}} as a parser function.
Pages with template loopstemplate-loop-categoryThe page contains a template loop, ie. a template which calls itself recursively.
Pages where the unstrip depth limit is exceededunstrip-depth-categoryThe page exceeds the unstrip depth limit.
Pages where the unstrip size limit is exceededunstrip-size-categoryThe page exceeds the unstrip size limit.