omniomni/omni-engineering huggingface dataset:
Fairey Seafox. The Fairey Seafox was a 1930s British reconnaissance floatplane designed and built by Fairey for the Fleet Air Arm. It was designed to be catapulted from the deck of a light cruiser and served in the Second World War.  Sixty-six were built, with two finished without floats and used as landplanes.

Design and development
The Fairey Seafox was built to satisfy Air Ministry Specification S.11/32 for a two-seat spotter-reconnaissance floatplane. The first of two prototypes appeared in 1936, first flying on 27 May 1936, and the first of the 64 production aircraft were delivered in 1937. The flights were organised as 700 Naval Air Squadron of the Fleet Air Arm.

The fuselage was of all-metal monocoque construction, the wings being covered with metal on the leading edge, otherwise fabric. It was powered by a 16-cylinder 395 hp (295 kW) air-cooled Napier Rapier H engine. It cruised at 106 mph (171 km/h), and had a range of 440 mi (710 km). The Seafox handled well but it was criticised for being underpowered, engine cooling was poor and landing speeds were higher than desired.

Operational history
In 1939, a Seafox played a part in the Battle of the River Plate against the German pocket battleship , by spotting for the naval gunners. Seafoxes operated during the early part of the war from the cruisers , , , ,  and  and the armed merchant cruisers ,  and . They remained in service until 1943.

Operators

 Fleet Air Arm
 700 Naval Air Squadron
 702 Naval Air Squadron
 703 Naval Air Squadron
 713 Naval Air Squadron
 714 Naval Air Squadron
 716 Naval Air Squadron
 718 Naval Air Squadron
 754 Naval Air Squadron
 764 Naval Air Squadron
 765 Naval Air Squadron
 773 Naval Air Squadron

Specification

See also

References

Notes

Bibliography

 "For Light Reconnaissance" (PDF). Flight, 9 December 1937. pp. 570–574.
 Mondey, David. The Hamlyn Concise Guide to British Aircraft of World War II. London; New York: Aerospace Publishing Ltd., 1982. P.87. , .
 Sturtivant, Ray and Balance, Theo. The Squadrons of the Fleet Air Arm. Tonbridge, Kent, UK: Air Britain (Historians) Ltd., 1994. .
 Taylor, H.A. Fairey Aircraft since 1915. London: Putnam, 1974. .

External links

 Fairey Seafox – British Aircraft of World War II

1930s British military reconnaissance aircraft
Floatplanes
Seafox
Single-engined tractor aircraft
Biplanes
Aircraft first flown in 1936
List of military aircraft of Sweden. This is a list of Swedish military aircraft since its start.  It is not guaranteed to be up-to-date or to be accurate, or complete. Aircraft still in service noted.

Early aircraft

Early balloons of the Army and Navy

Early Navy
(The aviation corps became a separate organization in 1915.)

Early Army
(The aviation corps became a separate organization in 1915.)

Air Force (1926–40)
Created in July of 1926.

Later XX implies later redesignation.

Fighters (Jakt)

Bombers (Bomb), torpedo bombers (Torped) and ground attack (Attack)

Reconnaissance (Spaning)

Transport (Transport)

Trainers (Skol) and advanced trainers (Övning)

Experimental/prototype/projects (Prov)

Undesignated/Miscellaneous
Not used by air force

Gliders
 G = Glidflygplan "glider"
 Se = Segelflygplan, "soarer" (sailplane),
 Lg = Lastglidare, "transport glider"

Post-1940 designation system
(Aircraft still in service have a light green background.)

Main list

Helicopters (Helikopter)

Navy

Army

Common helicopter wing
Helicopters that entered after a 1998 re-organisation/merger.

All the above active helicopters that were active were merged into this service.

Unmanned aerial vehicles

See also
 Swedish Armed Forces
 Swedish Air Force
 Swedish Army
 Swedish Navy
 List of Swedish-Made Military Aircraft

References

External links

 Swedish military aircraft designations
 Swedish military aviation
 World air forces: Sweden

Sweden Military Aircraft

Aircraft
Sweden
TI-85. The TI-85 is a graphing calculator made by Texas Instruments based on the Zilog Z80 microprocessor. Designed in 1992 as TI's second graphing calculator (the first was the TI-81), it was replaced by the TI-86, which has also been discontinued.

The TI-85 was significantly more powerful than the TI-81, as it was designed as a calculator primarily for use in engineering and calculus courses. Texas Instruments had included a version of BASIC on the device to allow programming.  Each calculator came with a cable to connect calculators (simply a three-conductor cable with 2.5 mm phone connectors on each end). Another cable known as the TI-Graph Link was also sold, along with appropriate software, to connect the calculator to a personal computer. These cables made it possible to save programs and make backups.

The TI-85 calculator is known in the modern era for being used by Sal Khan from Khan Academy in his educational videos.

Assembly programs 

Enthusiasts analyzed memory backups and discovered that entries in the calculator's CUSTOM menu pointed at specific memory locations. With this knowledge, a hack was devised where a special string could be inserted into the backup at the proper location to allow the calculator to execute assembly language programs. These programs could run much faster than their BASIC counterparts and be much more efficient in terms of memory usage. This development made the TI-85 the first TI graphing calculator that could execute assembly programs.

Programs written in assembly would be stored as string expressions and accessed through the CUSTOM menu. Games such as Tetris and Boulder Dash are available, as are programs with more practical uses, such as versions of the periodic table. Total memory capacity was about 32 kilobytes, with 28226 bytes available for use.

The assembly language shell ZShell is also available for the TI-85. Probably in response to the widespread use of assembly programs, TI officially introduced assembly access in later models, such as the TI-83 and TI-86, along with expanded memory.  The TI-86 is very similar to the TI-85, sharing the same display resolution (128×64), processor, and processor speed (6 MHz).

Technical specifications
 CPU: Zilog Z80 CPU, 6 MHz
 RAM: 32 KB, (28 KB user-available)
 ROM: 128 KB non-upgradeable
 Display
 Text: 21×8 characters
 Graphics: 128×64 pixels, monochrome
 Link capability: 2.5 mm I/O port
 Power: 4×AAA, 1×CR1616 or CR1620 (for backup power)
 Programming language(s): TI-BASIC, Z80 Assembly (accessible with a hack)

See also
 Comparison of Texas Instruments graphing calculators

References

External links
 ticalc.org – The largest archive of TI programs available.
 CalcG.org - Very organized and large archive of games and programs.
 TI-85 Graphical Demo - An interesting graphical demo programmed for a TI-85.

Graphing calculators
Texas Instruments programmable calculators
Products introduced in 1992
Z80
British Rail Class 10. The British Rail Class 10 diesel locomotives are a variant of the standard Class 08 diesel-electric shunter with a Lister Blackstone diesel engine and General Electric Company plc (GEC) traction motors. The locomotives were built at the BR Works in Darlington and Doncaster over the period 1955–1962, and were withdrawn between February 1967 and June 1972.

Background
British Railways built four main variants of its standard large diesel-electric shunter. Those fitted with a Lister Blackstone diesel engine were classified D3/4 if they had GEC traction motors and D3/5 with British Thomson-Houston (BTH) traction motors. The D3/4 locomotives were later reclassified to become Class 10 under TOPS.

Technical details
The locomotives had the same  general outline, 0-6-0 wheel arrangement and outside frames as the earlier Class 11, built originally for the London, Midland and Scottish Railway after 1945, and perpetuated by British Railways as the Class 08. However, they were fitted with Lister Blackstone 6-cylinder, 4-stroke, ER6T engines and two GEC nose suspended motors.

Building and use
The first batch of thirty locomotives, originally numbered 13137–13151, (later renumbered D3137–D3151) were built at Darlington works during 1955, and allocated to motive power depots in the North Eastern Region of British Railways, notably Thornaby. Further batches were built at Darlington as follows: D3439–D3453 (1957); D3473–D3491 (1957/8); D3612–D3651 (1958); D4049–D4094 (1961/2). These were allocated to the Eastern Region of British Railways particularly in the London area. Six examples, D3497–D3502, were built at Doncaster (1957/8). The class eventually numbered 146 locomotives.

Withdrawal
As they were non-standard, compared to the 08 class they had relatively short lives and were withdrawn between February 1967 and June 1972. Twenty locomotives were sold to industrial customers.

Post BR Use

Preservation

Four examples have been preserved:
 D3452 at Bodmin and Wenford Railway
 D3489 at Spa Valley Railway
 D4067 at Great Central Railway
 D4092 at Barrow Hill Engine Shed
 A fifth example, D3476, was stored on the Colne Valley Railway, though has since been scrapped.

References

 

10
C locomotives
Standard gauge locomotives of Great Britain
Diesel–electric locomotives of Great Britain
Railway locomotives introduced in 1955
Shunting locomotives
BESM-6. BESM-6 (, short for Большая электронно-счётная машина, i.e. 'Large Electronic Calculating Machine') was a Soviet electronic computer of the BESM series.

Overview
The BESM-6 was the most well-known and influential model of the series designed at the Institute of Precision Mechanics and Computer Engineering. The design was completed in 1965. Production started in 1968 and continued for the following 19 years.

Like its BESM-3 and BESM-4 predecessors, the original BESM-6 was transistor-based (however, the version used in the 1980s as a component of the Elbrus supercomputer was built with integrated circuits). The machine's 48-bit processor ran at 10 MHz clock speed and featured two instruction pipelines, separate for the control and arithmetic units, and a data cache of sixteen 48-bit words.  The system achieved a performance of 1 MIPS.
The CDC 6600, a common Western supercomputer when the BESM-6 was released, achieved about 2 MIPS.

The system memory was word-addressable using 15-bit addresses. The maximum addressable memory space was thus 32K words (192K bytes). A virtual memory system allowed to expand this up to 128K words (768K bytes).

The BESM-6 was widely used in USSR in the 1970s for various computation and control tasks. During the 1975 Apollo-Soyuz Test Project the processing of the space mission telemetry data was accomplished by a new computer complex which was based on a BESM-6. The Apollo-Soyuz mission's data processing by Soviet scientists finished half an hour earlier than their American colleagues from NASA.

A total of 355 of these machines were built. Production ended in 1987.

As the first Soviet computer with an installed base that was large for the time, the BESM-6 gathered a dedicated developer community. Over the years several operating systems  and compilers for programming languages such as Fortran, ALGOL and Pascal were developed.

A modification of the BESM-6 based on integrated circuits, with 2-3 times higher performance than the original machine, was produced in the 1980s under the name Elbrus-1K2 as a component of the Elbrus supercomputer.

In 1992, one of the last surviving BESM-6 machines was purchased by the Science Museum in London, England.

Peripherals
The BESM-6 could send output to an АЦПУ-128 (Алфавитно-Цифровое Печатающее Устройство) printer, and read input from punched cards in the GOST 10859 character set. A Consul-254 teletype, made by Zbrojovka Brno in Czechoslovakia, could be used for interactive sessions. When CRT terminals became available, the BESM-6 could be connected to Videoton 340 terminals.

Further reading
  (NB. Has information on the BESM-6 character set.)

References

External links
 BESM-6 Nostalgia Page

Soviet computer systems
1965 establishments in Russia
Supercomputers
Audi RSQ. The Audi RSQ concept vehicle series include:

Audi RSQ (2004)

The Audi RSQ is a mid-engined concept car developed by Audi AG for use as a product placement in the 2004 sci-fi film I, Robot. It is meant to depict a technologically advanced automobile in the Chicago cityscape from the year 2035.

This sports coupé is a visionary interpretation of Audi's typical automobile design. An important challenge presented to the designers was that in order for the car to have successful advertising for Audi as product placement, despite its extreme character, the car still had to be recognised by those audience members familiar with car designs as an Audi. To accommodate this demand, the engineers implemented a current Audi front-end design which includes the trapezoidal "Audi single-frame grille," the company's trademark four overlapping rings, and the Multi Media Interface (MMI) driver-to-car control system. The RSQ also includes special features suggested by film director Alex Proyas. The car uses spheres instead of conventional wheels. Its two reverse butterfly doors are hinged to the C-pillars of the body.

Although this kind of collaboration was a first for Audi, a similar project named the Lexus 2054 was developed by Lexus for use in the 2002 film Minority Report.

Audi RSQ e-tron (2019)

The Audi RSQ e-tron is a concept car developed by Audi for use in the 2019 animated film Spies in Disguise.

According to Audi, the car was designed closely with Blue Sky Studios and features a "visionary design language and futuristic highlights including a hologram speedometer".

Marketing
As part of the Audi RSQ e-tron and Spies in Disguise movie launch, a video named 'Lunchbreak' was produced.

See also
Audi Le Mans quattro, a similar styled concept car
Audi R8, a road car influenced by the RSQ's design and the production version of the Le Mans Quattro
Audi RS Q e-tron, an off-road competition car debuted in 2021

References

External links

 Audi UK page: RSQ, RSQ e-tron

RSQ e-tron
Cars designed and produced for films
All-wheel-drive vehicles
Rolls-Royce RB.183 Tay. The Rolls-Royce RB.183 Tay is a medium-bypass turbofan engine, developed from the RB.183 Mk 555 Spey core and using a fan scaled directly from the Rolls-Royce RB.211-535E4 to produce versions with a bypass ratio of 3.1:1 or greater. The IP compressor and LP turbine were designed using technology from the RB.211 programme. The engine was first run in August 1984. The Tay 650 had a new HP turbine which incorporated new technology which had been proven with the RB.211-535E4. This engine also had a new combustor for improved durability.
The Tay family is used on a number of airliners and larger business jets, including the Gulfstream IV family, Fokker 70 and Fokker 100, with a later version being used to re-engine Boeing 727-100s.

Variants

Tay 611-8

Originally designated 610-8, all but one training engine have now been converted to 611-8 standard. The newest variant is the 611-8C, which has cast HP1 turbine blades, larger fan from the 650-15, structural by-pass duct and FADEC.

All Tay engines use a 22-blade titanium fan, a 3-stage intermediate-pressure compressor coupled to the fan shaft, a 12-stage high-pressure compressor, a 2-stage high-pressure turbine and a 3-stage low-pressure turbine.

Thrust: 13,850 lbf (62 kN)
Aircraft: Tay 611 entered service in 1987 on the Gulfstream IV/IV-SP, for which it is the exclusive powerplant.

Tay 620-15

The 620-15 is internally identical to the 611-8 and externally similar to the 650-15.

Thrust: 13,850 lbf (62 kN)
Aircraft: Fokker 70 from 1994, Fokker 100 from 1988

Tay 650-15
Thrust: 15,100 lbf (67 kN)
Aircraft: Originally designed to re-engine the BAC One-Eleven (650-14, only two made; both have since been converted to 650-15 standard.), the 650-15 entered service on the Fokker 100 in 1989.

Tay 651-54
The 651-54 is internally identical to the 650-15. The externals and gearbox suit the Boeing 727.

Thrust: 15,400 lbf (69 kN)
Aircraft: Boeing 727-100 from 1992. Conversion from three JT8D-7 to three Tay 651-54 was carried out by the now defunct Dee Howard Aircraft Maintenance Company in San Antonio, Texas, for the United Parcel Service, but all aircraft have since been withdrawn from service. Only one private 727 was converted.

Applications
 BAC 1-11
 Boeing 727-100 QF
 Fokker 70
 Fokker 100
 Gulfstream IV
 Gulfstream G350/G400/G450
 Gulfstream X-54

Engines on display
 A Tay RB.183 620-15 is on public display at the City of Norwich Aviation Museum in Horsham St Faith, Norfolk.

Specifications (Tay 620-15)

See also

References

Notes

Bibliography

FAA Type Certificate Data Sheet 
Gunston, Bill. World Encyclopedia of Aero Engines. Cambridge, England. Patrick Stephens Limited, 1989. 
Rolls-Royce Tay product page

External links

Rolls-Royce Tay

Medium-bypass turbofan engines
Tay
1980s turbofan engines
Matra BAe Dynamics. Matra BAe Dynamics was an Anglo-French 50/50 joint venture formed in August 1996 through a merger between half the missile business of France's Matra Hautes Technologies (the aerospace, defence and telecommunications division of the Matra conglomerate) and the missile activities of the UK's BAe Dynamics (a division of British Aerospace). During its 5 years of existence, it was Europe`s largest guided weapons company and the third largest in the world.

British Aerospace had previously sought to merge its missile business with that of France's Thomson-CSF (now Thales Group). The companies announced their plan to create a new combined company called Eurodynamics in 1989. However, after more than a year of monopoly investigations, the deal collapsed. The formation of Matra BAe Dynamics was followed in 1997 by the acquisition of a 30% share in LFK.

In 1999, the other half of Matra Hautes Technologies' missile business (Matra Missiles) combined with the missile systems division of the French corporation Aérospatiale to form Aérospatiale Matra Missiles following the merger between Aérospatiale and Matra Hautes Technologies. This new giant, Aérospatiale-Matra, also gained ownership of Matra's 50% share in Matra BAe Dynamics as a result of the merger.

Matra BAe Dynamics ultimately merged with Aérospatiale Matra Missiles and the missile activities of Alenia Marconi Systems to form MBDA in December 2001.

References

Aerospace companies of the United Kingdom
BAE Systems subsidiaries and divisions
Defence companies of France
Defence companies of the United Kingdom
France–United Kingdom military relations
Guided missile manufacturers
Manufacturing companies established in 1996
Matra
Multinational joint-venture companies
1996 establishments in France
British companies established in 1996
IITRAN. IITRAN is a discontinued programming language created in the mid-1960s and designed as a first language for students. The primary designer of the language, William S. Worley, also contributed to the design of PL/I, and the two languages have similar syntax.  The name derives from Illinois Institute of Technology, where it was developed.

The IITRAN language was initially implemented for IBM 7040, with a compiler made available to students in 1964. This was followed shortly by an IBM System/360 implementation in 1966, for which the language was partially redesigned by a committee led by Dr. Peter G. Lykos. In the early 1970s, a compiler was developed for the Univac 1108 platform. Programming was done using punched cards.

IITRAN was designed and developed in response to the increasing demand for a computer language which would meet the following specifications:

It should be clear, concise, and easily learned, even for those who have had no previous experience with computers or mathematics;
It should bear as close a resemblance as possible to the English language;
It should be free of awkward restrictions and limitations;
It should be consistent with mathematical and logical foundations;
It should allow processing of a great number of individual programs in a very short time;
It should serve as a computational tool for students of science and engineering;
It should process a clear, easily understood, set of diagnostic error messages.
(Bauer, p. V)

There was a Spanish language version of IITRAN at IIT as well. It utilized Spanish keywords rather than English ones. For example, the keyword read was replaced by leer.

Bibliography
IITRAN / 360: Self-Instructional Manual and Text,  Bauer, Charles R. et al.,  Addison Wesley Publishing, 1967. 
The IITRAN Programming Language, R. Dewar et al., CACM 12(10):569-575 (Oct 1969).

Educational programming languages
PL/I programming language family
Lava flow (programming). In computer programming jargon, lava flow is an anti-pattern that occurs when computer source code written under sub-optimal conditions is deployed into a production environment and subsequently expanded upon while still in a developmental state. The term derives from the natural occurrence of lava which, once cooled, solidifies into rock that is difficult to remove. Similarly, such code becomes difficult to refactor or replace due to dependencies that arise over time, necessitating the maintenance of backward compatibility with the original, incomplete design.

Causes 
Lava flow can occur due to a variety of reasons within a software development process:
 Pressure to meet deadlines leading to temporary solutions becoming permanent
 Inadequate documentation which prevents understanding of the code’s purpose
 Lack of automated tests which makes refactoring risky
 Frequent changes in the development team leading to loss of knowledge

Consequences 
Unrefined code that becomes part of the software’s infrastructure increases the complexity of the system and the codebase becomes increasingly difficult to understand and maintain. It leads to:
 The need for backward compatibility which can stifle innovation and prevent adoption of newer, more efficient solutions
 Increased technical debt that accumulates over time, resulting in higher costs of change and maintenance
 Obstacles to refactoring or improving the system due to fear of breaking dependent components

Impact on teams 
Development teams often experience the impact of lava flow when team members cycle in and out:
 Loss of knowledge about aspects of the system's code when original developers leave
 Reluctance among new developers to refactor unfamiliar code, leading to further complexity as they add rather than clean up

Mitigation strategies 
Several practices can mitigate the effects of the lava flow anti-pattern:
 Promoting good documentation practices for clear understanding of code
 Encouraging regular code reviews to catch suboptimal practices early
 Prioritizing refactoring as an integral part of the development lifecycle
 Maintaining a comprehensive suite of automated tests to reduce risk in changes

References

Anti-patterns