omniomni/omni-engineering huggingface dataset:
Francis Mond Professor of Aeronautical Engineering. The Francis Mond Professor of Aeronautical Engineering is a professorship in the University of Cambridge. It was established in 1919 as a result of a benefaction from Emile Mond, in memory of his son Francis who had been educated at Peterhouse and was killed in action on 15 May 1918 whilst serving with the RAF on the Western Front.

Incumbents of the Francis Mond Professorship of Aeronautical Engineering

Bennett Melvill Jones, 1919–1952
William Austyn Mair, 1952–1983
Michael Gaster, 1986–1995
Bill Dawes, 1996–current

See also
List of Professorships at the University of Cambridge

References

Aeronautical Engineering, Mond, Francis
School of Technology, University of Cambridge
Aeronautical Engineering, Mond, Francis, Cambridge
1919 establishments in England
Worshipful Company of Engineers. The Worshipful Company of Engineers is one of the livery companies of the City of London. The company was founded and became a livery company in 1983 and was incorporated by royal charter in 2004. The company is for chartered engineers of EC(UK) professional institutions or fellows of the Royal Academy of Engineering. It works to promote and develop all aspects of the science, art, and practice of engineering.

The Engineers' Company ranks ninety-fourth in the order of precedence for livery companies. Its motto is Certare Ingenio, Latin for Use Skills to the Best of One's Abilities. Its church is St Vedast-alias-Foster.

Masters 
Since the formation of the Company in 1983:

References

External links
 The Engineers' Company

Engineering societies based in the United Kingdom
Engineers
1983 establishments in England
Am486. The Am486 is a 80486-class family of computer processors that was produced by AMD in the 1990s. Intel beat AMD to market by nearly four years, but AMD priced its 40 MHz 486 at or below Intel's price for a 33 MHz chip, offering about 20% better performance for the same price.

While competing 486 chips, such as those from Cyrix, benchmarked lower than the equivalent Intel chip, AMD's 486 matched Intel's performance on a clock-for-clock basis.

While the Am386 was primarily used by small computer manufacturers, the Am486DX, DX2, and SX2 chips gained acceptance among larger computer manufacturers, especially Acer and Compaq, in the 1994 time frame.

AMD's higher clocked 486 chips provided superior integer performance to many of the early Pentium chips, especially the 60 and 66 MHz launch products. While equivalent Intel 80486DX4 chips were priced high and required a minor socket modification, AMD priced low. Intel's DX4 chips initially had twice the cache of the AMD chips, giving them a slight performance edge, but AMD's DX4-100 usually cost less than Intel's DX2-66.

The enhanced Am486 series supported new features like extended power-saving modes and an 8 KiB Write-Back L1-Cache, later versions even got an upgrade to 16 KiB Write-Back L1-Cache.

The 133 MHz AMD Am5x86 was a higher clocked enhanced Am486.

One derivative of the Am486 family is the core used in the AMD Élan SC4xx family of microcontrollers marketed by AMD.

Features

Am486 models

WT = Write-Through cache strategy, WB = Write-Back cache strategy

References

External links 

 AMD: Enhanced Am486 Microprocessors
 AMD: 30 Years of Pursuing the Leader. Part 2
 cpu-collection.de AMD Am486 processor images and descriptions

Am486
X86 microarchitectures
Computer-related introductions in 1992
Bus contention. Bus contention is an undesirable state in computer design where more than one device on a bus attempts to place values on it at the same time.  

Bus contention is the kind of telecommunication contention  that occurs when all communicating devices communicate directly with each other through a single shared channel, and contrasted with "network contention" that occurs when communicating devices communicate indirectly with each other, through point-to-point connections through routers or bridges.

Bus contention can lead to erroneous operation, excess power consumption, and, in unusual cases, permanent damage to the hardware—such as burning out a MOSFET.

Description
Most bus architectures requires devices sharing a bus to follow an arbitration protocol carefully designed to make the likelihood of contention negligible. However, when devices on the bus have logic errors, manufacturing defects, or are driven beyond their design speeds, arbitration may break down and contention may result. Contention may also arise on systems which have a programmable memory mapping when illegal values are written to the registers controlling the mapping.
Most small-scale computer systems are carefully designed to avoid bus contention on the system bus. They use a single device, called bus arbiter, that controls which device is allowed to drive the bus at each instant, so bus contention never happens in normal operation. The standard solution to bus contention between memory devices, such as EEPROM and SRAM, is the three-state bus with a bus arbiter.

Some networks, such as Token Ring, are also designed to avoid bus contention, so bus contention never happens in normal operation.

Most networks are designed with hardware robust enough to tolerate occasional bus contention on the network. CAN bus, ALOHAnet, Ethernet, etc., all experience occasional bus contention in normal operation, but use some protocol (such as Multiple Access with Collision Avoidance, carrier-sense multiple access with collision detection, or automatic repeat request) to minimize the times that contention occurs, and to re-send data that was corrupted in a packet collision.

See also 
 Network on a chip
 Parallel communication
 Serial communication

References 

Computer buses
SRP. SRP may refer to:

Science and technology
 Scaling and root planing, in dentistry
 Signal recognition particle, in cell biology
 Soluble reactive phosphorus, in soil sciences
 Spreading resistance profiling, for measuring semiconductor resistivity

Computing
 Secure Remote Password protocol, for authentication
 Server Routing Protocol, for BlackBerry
 Spatial Reuse Protocol, a Cisco networking protocol
 Stream Reservation Protocol, Ethernet enhancement
 Session Request Protocol, of USB On-The-Go
 Stack Resource Policy, a resource allocation policy
 SCSI RDMA Protocol, for transferring commands and data
 Synchronous reactive programming, a programming paradigm for reactive systems
 Single-responsibility principle, a programming principle (the S in SOLID)

Military
 Ship-submarine recycling program, a US Navy program
 Soldier Readiness Processing, a US Army program

Organizations
 Salt River Project, a utilities provider in Arizona, US
 Society for Radiological Protection, UK
 Sdruženie rasovo prenasledovaných (Association of Racially Persecuted People), which helped Holocaust survivors in Slovakia
 SRP Records, founded by Carl Sturken and Evan Rogers

Politics
 Sam Rainsy Party, the main opposition party in Cambodia
 Self-Defense of the Republic of Poland, a political party
 Socialist Labour Party of Croatia (Socijalistička radnička partija Hrvatske)
 Socialist Reich Party (Sozialistische Reichspartei), West Germany, banned in 1952

Other uses
 Suggested retail price
 Stord Airport, Sørstokken (IATA airport code), Norway
 Sports Racing Prototype, a car classification
 Shelf-ready packaging, for a product
 Service release premium, payment received by a lender on the sale of a closed mortgage loan
 South Road Properties, Cebu City, Philippines
 Serbian language (ISO 639-3 and ISO 639-2 code: srp)
 Standard Response Protocol
Sakigake. , known before launch as MS-T5, was Japan's first interplanetary spacecraft and the first deep space probe to be launched by any country other than the US or the Soviet Union. It aimed to demonstrate the performance of the new launch vehicle, test its ability to escape from Earth gravity, and observe the interplanetary medium and magnetic field. Sakigake was also supposed to act as a frame of reference for data received from probes that flew closer to Halley's Comet.  Early measurements would be used to improve the mission of the Suisei probe launched several months later.

Sakigake was developed by the Institute of Space and Astronautical Science for the National Space Development Agency (both of which are now part of the Japanese Aerospace Exploration Agency, or JAXA). It became a part of the Halley Armada together with Suisei, the Soviet Vega probes, the ESA Giotto and the NASA International Cometary Explorer, to explore Halley's Comet during its 1986 sojourn through the inner Solar System.

Design
Unlike its twin Suisei, it carried no imaging instruments in its instrument payload.

Launch
Sakigake was launched January 7, 1985, from Kagoshima Space Center by M-3SII launch vehicle on M-3SII-1 mission.

Halley encounter
It carried out a flyby of Halley's Comet on March 11, 1986, at a distance of 6.99 million km.

Giacobini-Zinner encounter
There were plans for the spacecraft to go on to an encounter with 21P/Giacobini-Zinner in 1998, but the flyby had to be abandoned because of a lack of propellant.

End of mission
Telemetry contact was lost on November 15, 1995, though a beacon signal continued to be received until January 7, 1999.

References

External links

 Sakigake
 Sakigake Mission Profile by NASA's Solar System Exploration
 Halley's Comet Flyby
 Sakigake Mission Comet Halley Data Archive at the NASA Planetary Data System, Small Bodies Node

Japanese space probes
Missions to Halley's Comet
Satellites orbiting the Sun
1985 in spaceflight
Derelict space probes
Spacecraft launched in 1985
Japanese inventions
Ten15. Ten15 is an algebraically specified abstract machine. It was developed by Foster, Currie et al. at the Royal Signals and Radar Establishment at Malvern, Worcestershire, during the 1980s. It arose from earlier work on the Flex machine, which was a capability computer implemented via microcode. Ten15 was intended to offer an intermediate language common to all implementations of the Flex architecture for portability purposes. It had the side effect of making the benefits of that work available on modern processors lacking a microcode facility.

Ten15 served as an intermediate language for compilers, but with several unique features, some of which have still to see the light of day in everyday systems. Firstly, it was strongly typed, yet wide enough in application to support most languages — C being an exception, chiefly because C deliberately treats an array similar to a pointer to the first element of that array. This ultimately led to Ten15's development into TDF, which in turn formed the basis for ANDF. Secondly, it offered a persistent, write-only filestore mechanism, allowing arbitrary data structures to be written and retrieved without conversion into an external representation.

Historical note 
Why 'Ten15'? Nic Peeling reports that during early discussions of the concepts of Ten15, it was agreed that this was important and should have a name - but what? Ian Currie looked up at the clock and said 'Why not call it 10:15?'

See also 
 Virtual machine
 TenDRA Compiler

References 

 

Computer languages
History of computing in the United Kingdom
Malvern, Worcestershire
Science and technology in Worcestershire
Theory of computation
Flex machine. The Flex Computer System was developed by Michael Foster and Ian Currie of Royal Signals and Radar Establishment (RSRE) in Malvern, England, during the late 1970s and 1980s. It used a tagged storage scheme to implement a capability architecture, and was designed for the safe and efficient implementation of strongly typed procedures.

The hardware was custom and microprogrammable, with an operating system, (modular) compiler, editor, garbage collector and filing system all written in ALGOL 68RS. 

There were (at least) two incarnations of Flex, implemented using hardware with writable microcode. The first was supplied by Logica to an RSRE design, and the second used an ICL PERQ.  The microcode alone was responsible for storage allocation, deallocation and garbage collection. This immediately precluded a whole class of errors arising from the misuse (deliberate or accidental) of pointers.

A notable feature of Flex was the tagged, write-once filestore. This allowed arbitrary code and data structures to be written and retrieved transparently, without recourse to external encodings. Data could thus be passed safely from program to program.

In a similar way, remote capabilities allowed data and procedures on other machines to be accessed over a network connection, again without the application program being involved in external encodings of data, parameters or result values.

The whole scheme allowed abstract data types to be safely implemented, as data items and the procedures permitted to access them could be bound together, and the resulting capability passed freely around. The capability would grant access to the procedures, but could not be used in any way to obtain access to the data.

Another notable feature of Flex was the notion of shaky pointers, more recently often called weak references, which points to blocks of memory that could be freed at the next garbage collection.  This is used for example for cached disc blocks or a list of spare procedure work-spaces.

COMFLEX, a packet switching network capable of transmitting data at magnetic-disc speed, was developed alongside Flex. It made feasible the use of remote file-stores, remote capabilities, and remote procedure calls.

See also 
 Royal Radar Establishment Automatic Computer
 Ten15
 PS-algol

References

Further reading

 Martin C. Atkins:  An Introduction to Ten15 - A personal retrospective. (includes a section about RSRE's Flex)

Computers designed in the United Kingdom
Capability systems
Malvern, Worcestershire
Mainframe computers
Science and technology in Worcestershire
Flex. Flex or FLEX may refer to:

Computing
 Apache Flex, formerly Adobe Flex, technologies for developing rich internet applications
 Flex (language), developed by Alan Kay
 FLEX (operating system), a single-tasking operating system for the Motorola 6800
 FlexOS, an operating system developed by Digital Research
 FLEX (protocol), a communication protocol for pagers
 Flex, a family of automatic test equipment produced by Teradyne
 FLEx, a piece of software used in language documentation
 Flex (lexical analyser generator), a lexical analyser generator and a free software alternative to lex
 Flex machine, a computer developed by RSRE in the 1980s
 CSS Flexible Box Layout, commonly known as Flexbox, a CSS 3 web layout model

Science and technology
 Bending, also known as flexure, as used in mechanics
 Flexion, in anatomy, a position made possible by the joint angle decreasing
 Femtosecond Lenticule EXtraction, a form of refractive eye surgery
 Flex circuit, a flexible printed circuit used in electronic assemblies
 FLEX mission, a future satellite launch mission by the European Space Agency
 Flex temp, a reduced takeoff thrust setting which trades excess performance for reduced engine wear
 Flex-fuel, a flexible-fuel vehicle
 Inflection point, of a curve in geometry
 Power cord, or flex, a flexible electrical cable

Music
 Flex (singer), Félix Danilo Gómez (born 1974), Panamanian singer
 Funkmaster Flex (born 1968),  American DJ and music producer
 Flex (album), Lene Lovich's 1979 second album
 Flex (EP) a 2003 EP by Pitch Black
 "Flex" (Dizzee Rascal song), 2007
 "Flex" (Mad Cobra song), 1992
 "Flex" (Polo G song), 2020
 "Flex (Ooh, Ooh, Ooh)", a 2015 song by Rich Homie Quan
 "Flex", a 2021 song by TFN
 Flex, a break in the recitation tone before the mediation in Gregorian chant
A "flex" in a "flex bar", a technique used in battle rap

Organizations
 Flex Ltd., a software compant, previously known as Flextronics
 Flex (club), a nightclub in Vienna, Austria
 Flex (company) (NASDAQ symbol: FLEX), a contract electronics maker based in Singapore
 Flex FM, a London-based radio station
 Flex-Elektrowerkzeuge, a German producer of power tools
 Flex Linhas Aéreas, a Brazilian regional airline

People
 Flex Alexander, Mark Alexander Knox (b. 1970), an American actor and comedian
 Flex Wheeler (born 1965), American bodybuilder
 Walter Flex (1887–1917), German author

Other uses
 Amazon Flex, a platform for gig workers performing deliveries for Amazon
 Flex (comics), a fictional superhero
 Flex (film), a commercial/short film by English director Chris Cunningham
 Flex (magazine), an American bodybuilding magazine
 Flex (TV program), a 2021 Philippine variety show
 Fleet Landing Exercises, a series of landing exercises conducted by the Fleet Marine Force, a combined-United States Navy/Marine landing force
 Flex Your Rights, a civil-liberties non-profit based in Washington DC, US
 Ford Flex, a crossover SUV produced from 2009-2019
 Future Leaders Exchange, an American student exchange program for high school students from the former Soviet Union

See also
 Bend (disambiguation)
 Flexible (disambiguation)
Architecture Neutral Distribution Format. The Architecture Neutral Distribution Format (ANDF) in computing is a technology allowing common "shrink wrapped" binary application programs to be distributed for use on conformant Unix systems, translated to run on different underlying hardware platforms.  ANDF was defined by the Open Software Foundation and was expected to be a "truly revolutionary technology that will significantly advance the cause of portability and open systems", but it was never widely adopted.

As with other OSF offerings, ANDF was specified through an open selection process.  OSF issued a Request for Technology for architecture-neutral software distribution technologies in April, 1989.  Fifteen proposals were received, based on a variety of technical approaches, including obscured source code, compiler intermediate languages, and annotated executable code.

The technology of ANDF, chosen after an evaluation of competing approaches and implementations, was Ten15 Distribution Format, later renamed TenDRA Distribution Format, developed by the UK Defence Research Agency.

Adoption

ANDF was intended to benefit both software developers and users.  Software developers could release a single binary for all platforms, and software users would have freedom to procure multiple vendors' hardware competitively. Programming language designers and implementors were also interested because standard installers would mean that only a single language front end would need to be developed.

OSF released several development 'snapshots' of ANDF, but it was never released commercially by OSF or any of its members.  Various reasons have been proposed for this: for example, that having multiple installation systems would complicate software support.

After OSF stopped working on ANDF, development continued at other organizations.

See also
 TenDRA Compiler
 UNCOL
 Java bytecode
 Common Language Runtime
 LLVM
 Compilation
 Software portability
 WebAssembly
 SafeTSA
 Oberon slim binaries

References

Bibliography
 Stavros Macrakis, "The Structure of ANDF: Principles and Examples", Open Software Foundation, RI-ANDF-RP1-1, January, 1992.
 Stavros Macrakis, "Protecting Source Code with ANDF", Open Software Foundation, November, 1992.
 Open Systems Foundation. "OSF Architecture-Neutral Distribution Format Rationale", June 1991.
 Open Systems Foundation. "A Brief Introduction to ANDF", January 1993.  Available at Google Groups

Abstract machines
Cross-compilers
Executable file formats
Computer-related introductions in 1991
Shim (computing). In computer programming, a shim is a library that transparently intercepts API calls and changes the arguments passed, handles the operation itself or redirects the operation elsewhere. Shims can be used to support an old API in a newer environment, or a new API in an older environment. Shims can also be used for running programs on different software platforms than they were developed for.

Shims for older APIs typically come about when the behavior of an API changes, thereby causing compatibility issues for older applications which still rely on the older functionality; in such cases, the older API can still be supported by a thin compatibility layer on top of the newer code. Shims for newer APIs are defined as: "a library that brings a new API to an older environment, using only the means of that environment."

Examples 
 Web polyfills implement newer web standards using older standards and JavaScript, if the newer standard is not available in a given web browser.
 Support of AppleTalk on Macintosh computers, during the brief period in which Apple Computer supported the Open Transport networking system. Thousands of Mac programs were based on the AppleTalk protocol; to support these programs, AppleTalk was re-implemented as an OpenTransport "stack", and then re-implemented as an API shim on top of this new library.
 The Microsoft Windows Application Compatibility Toolkit (ACT) uses the term to mean backward compatible libraries. Shims simulate the behavior of older versions of Windows for legacy applications that rely on incorrect or deprecated functionality, or correct the way in which poorly written applications call unchanged APIs, for example to fix least-privileged user account (LUA) bugs.
 bind.so is a shim library for Linux that allows any application, regardless of permissions, to bind to a listening socket or specify outgoing IP address. It uses the LD_PRELOAD mechanism, which allows shims and other libraries to be loaded into any program.
 In the type tunnel pattern, a generic interface layer uses a family of shims to translate a heterogeneous set of types to a single primitive type used by an underlying API.

See also 
 Adapter pattern
 Application virtualization
 Driver wrapper
 Glide wrapper
 Glue code
 Stub (computer science)
 Thunk (compatibility mapping)
 Windows on Windows (WoW)
 Wrapper function
 Wrapper library

References

External links 
 Microsoft Dev-Center - Windows 8 Client and Server 2012 application Compatibility
 Microsoft TechNet - Understanding Shims

Application programming interfaces
Compatibility layers