omniomni/omni-engineering huggingface dataset:
LSI. LSI may refer to:

Science and technology 

 Large-scale integration, integrated circuits with tens of thousands of transistors
 Latent semantic indexing, a technique in natural language processing
 LSI-11, an early large-scale integration computer processor that implemented the DEC PDP-11 instruction set
 Langelier saturation index, a measure for water's tendency to form scale
 Linear shift-invariant systems, the discrete equivalent of linear time-invariant systems

Organizations 

 LSI Corporation, a technology company founded in 1981 as LSI Logic Corporation
 Lynch Syndrome International, non-profit organisation supporting those affected by Lynch Syndrome
 Labour and Socialist International, a multinational federation of left wing political parties and trade unions active between 1923 and 1940
 Socialist Movement for Integration (Lëvizja Socialiste për Integrim), a political party in Albania
 Lear Siegler Incorporated, a technology company active from 1961 to 2002
 Lingkaran Survei Indonesia, a survey company in Indonesia

Transportation 

 Lake Superior and Ishpeming Railroad, a railroad service in Michigan, United States
 Sumburgh Airport (IATA airport code) in Shetland, Scotland

Music 

 "LSI (Love Sex Intelligence)", a single by The Shamen
 Long-string instrument, a musical instrument

Other uses 

 Landing ship, infantry, a type of troopship or post World War II a landing craft
 La Salle Institute, a college preparatory school
 Linguistic Survey of India, a survey of the languages of British India directed by G.A. Grierson
 Logical Sensory Introvert, a socionics type
 Lighting & Sound International, a trade magazine
Wait state. A wait state is a delay experienced by a computer processor when accessing external memory or another device that is slow to respond.

Computer microprocessors generally run much faster than the computer's other subsystems, which hold the data the CPU reads and writes.  Even memory, the fastest of these, cannot supply data as fast as the CPU could process it.  In an example from 2011, typical PC processors like the Intel Core 2 and the AMD Athlon 64 X2 run with a clock of several GHz, which means that one clock cycle is less than 1 nanosecond (typically about 0.3 ns to 0.5 ns on modern desktop CPUs), while main memory has a latency of about 15–30 ns. Some second-level CPU caches run slower than the processor core.

When the processor needs to access external memory, it starts placing the address of the requested information on the address bus. It then must wait for the answer, that may come back tens if not hundreds of cycles later. Each of the cycles spent waiting is called a wait state.

Wait states are a pure waste of a processor's performance. Modern designs try to eliminate or hide them using a variety of techniques: CPU caches, instruction pipelines, instruction prefetch, branch prediction, simultaneous multithreading and others. No single technique is 100% successful, but together can significantly reduce the problem.

Energy conservation
Wait states can be used to reduce the energy consumption of a processor, by allowing the main processor clock to either slow down or temporarily pause during the wait state if the CPU has no other work to do. Rather than spinning uselessly in a tight loop waiting for data, sporadically reducing the clock speed in this manner helps to keep the processor core cool and to extend battery life in portable computing devices.

Alternative meaning on IBM mainframes
On IBM mainframes, the term wait state is used with a different meaning. A wait state refers to a CPU being halted, possibly due to some kind of serious error condition (such as an unrecoverable error during operating system to IPL). A wait state is indicated by bit 14 of the PSW being set to 1, with other bits of the PSW providing a wait state code giving a reason for the wait.  In z/Architecture mode, the wait state code is found in bits 116-127.

See also
 Bubble (computing)
 
 Consistency model
 Cache miss
 Page fault
 Multithreading (computer architecture)
 Zero wait state

References 

Central processing unit
IBM mainframe technology
Adaptive Communication Environment. The Adaptive Communication Environment (ACE) is an open source software framework used for network programming. It provides a set of object-oriented C++ classes designed to help address the inherent complexities and challenges in network programming by preventing common errors.

History
ACE was initially developed by Douglas C. Schmidt during his graduate work at the University of California, Irvine. Development followed him to the Washington University in St. Louis, where he was employed. ACE is open-source software released by WU's Distributed Object Computer (DOC) group. Its development continued in the Institute for Software Integrated Systems (ISIS) at Vanderbilt University.

Features
ACE provides a standardized usage for operating system/machine specific features. It provides common data types and methods to access the powerful but complex features of modern operating systems. These include: inter-process communication, thread management, efficient memory management, etc. 

It was designed to be portable and provide a common framework. The same code will work on most Unixes, Windows, VxWorks, QNX, OpenVMS, etc., with minimal changes. Due to this cross-platform support, it has been widely used in the development of communication software. Some of the successful projects that have used ACE includes: Motorola Iridium satellites, Boeing Wedgetail's Australian airborne early warning & control (AEW&C) system, and others.

ACE used software design patterns.

See also
 Communication software
 Component-integrated ACE ORB
 Cross-platform support middleware
 TAO (software)

References

External links

Restful API Information
Distributed object computer (DOC) Group website
Institute for Software Integrated Systems (ISIS) website 
ACE Doxygen reference
ACE github code repository

C++ libraries
Cross-platform software
Application programming interfaces
Volvo P1900. The Volvo Sport (also known as P1900) is a Swedish fiberglass-bodied roadster of which sixty-eight units were built, first 19 by Glasspar Company in California, between 1956 and 1957 by Volvo Cars.

Assar Gabrielsson, Volvo's president and founder, got the idea for the car when he saw a Chevrolet Corvette in the United States and wanted to make something similar. He asked Bill Tritt of Glasspar, an American boatbuilder in Santa Ana, California, to design and tool a fibreglass/reinforced polyester body, which was later produced in Sweden. Glasspar was a pioneer in building fiberglass auto bodies from 1951 to 1957.

Erik Quistgaard was appointed as development team leader.
The car was built on a tubular-steel chassis and used the Volvo PV444's 1414 cc engine producing . The engines (B14A and B16B ) were fitted with twin SU carburetors, driving through a three-speed manual gearbox. Many other parts were taken also from the Volvo PV444.

Demand was low, and the build quality was not up to Volvo standards. Gunnar Engellau, who replaced Gabrielsson as president in 1956, took one for a drive on a holiday weekend and was dissatisfied enough that on returning to his office the following week cancelled the remaining production. "I thought it would fall apart!" is the legendary quote. The Volvo chassis design was far too flexible to accommodate a fiberglass body, and that Volvo resisted recommendations by Glasspar to alter the frame to address their concerns.

The total "Volvo Sport" production was sixty-eight cars, plus four or five prototypes. Forty-four were built in 1956, mostly for the Swedish market, and most still survive. The bulk of 1957's production went to the U.S. and elsewhere, and fewer of these are still in existence.

The development of the P1900 led to the tuning of the B-16 engine however, which was later put into the PV 444 series, making this car powerful enough to enter the US market.

Gallery

References

External links
 Czap, Nick (February 18, 2010).  "Unrequited Longing for the 67th Volvo".  The New York Times.  Accessed February 24, 2010.

P1900
Sports cars
Rear-wheel-drive vehicles
Cars introduced in 1956
Roadsters
A6. A6, A 6 or A-6 can refer to:

Arts and entertainment
A6, a mutated flu virus in the short story "Night Surf" by Stephen King
A-6, a renamed version of the US Security Group in the 1997 comic book movie Spawn

Electronics and software
A6 record, a type of DNS record
Apple A6, a System-on-a-chip ARM processor
Hanlin eReader A6, an ebook reader
Samsung Galaxy A6, a smartphone by Samsung

Military
A6, the designation for air force headquarters staff concerned with signals, communications, or information technology
In the United Kingdom, the A6 Air CIS (Computers & Information Systems) branch, also known as JFACHQ, UK Joint Force Air Component Headquarters
A 6, a Swedish artillery regiment
Grumman A-6 Intruder, a twin-engine, mid-wing all-weather US Navy medium attack aircraft manufactured by Grumman, in service from 1962 to 1997

Science and technology

Biology
British NVC community A6 (Ceratophyllum submersum community), a British Isles plants community
Noradrenergic cell group A6
Subfamily A6, a subfamily of Rhodopsin-like receptors
Xenopus A6 kidney epithelial cells in cell culture

Transportation

Civil aviation transport
A6, the IATA code for Air Alps Aviation
United Arab Emirates aircraft registration code

Civilian aircraft
Focke-Wulf A6, a 1930s civilian aircraft from the German Focke-Wulf company

Automobiles
Arrows A6, a British racing car
Audi A6, a German executive car
Changhe A6, a Chinese compact sedan
JAC Refine A6, a Chinese mid-size sedan concept
Maserati A6, an Italian sports coupe series

Roads and routes
A6 road, in several countries
Route A6 (WMATA), a bus route operated by the Washington Metropolitan Area Transit Authority\

Watercraft
A-6, formerly , a Plunger-class submarine of the United States Navy
 , a British A-class submarine of the Royal Navy

Other
Prussian A 6, a 1913 German railbus
A6, an aggregate series (A1 to A12) German rocket design in World War II, never implemented
LNER Class A6, a class of 4-6-2T locomotives

Other uses
A6 (classification), an amputee sport classification
A-6 tool steel, an air-hardening SAE grade of tool steel
A6, an ISO 216 international standard paper size (105×148 mm)
A6, or A (musical note) above soprano C, the highest note written or acknowledged as musical in classical music
ASICS, a footwear company whose name and logo resemble A6

A06
A.06, a track title on Linkin Park Underground Linkin Park fan club compilation
A06 (band), a Massachusetts-based rock band associated with multi-instrumentalist Casey Crescenzo
ATC code A06 Laxatives, a subgroup of the Anatomical Therapeutic Chemical Classification System
HMNZS Monowai (A06), a 1975 Royal New Zealand Navy hydrographic survey vessel
Réti Opening code in the Encyclopaedia of Chess Openings
Engines of Creation. Engines of Creation: The Coming Era of Nanotechnology is a 1986 molecular nanotechnology book written by K. Eric Drexler with a foreword by Marvin Minsky. An updated version was released in 2007.   The book has been translated into Japanese, French, Spanish, Italian, Russian, and Chinese.

Synopsis
The book features nanotechnology, which Richard Feynman had discussed in his 1959 speech "There's Plenty of Room at the Bottom."  Drexler imagines a world where the entire Library of Congress can fit on a chip the size of a sugar cube and where universal assemblers, tiny machines that can build objects atom by atom, will be used for everything from medicinal robots that help clear capillaries to environmental scrubbers that clear pollutants from the air.  In the book, Drexler proposes the gray goo scenario—one prediction of what might happen if molecular nanotechnology were used to build uncontrollable self-replicating machines.

Topics also include hypertext as developed by Project Xanadu and life extension. Drexler takes a Malthusian view of exponential growth within limits to growth. He also promotes space advocacy, arguing that, because the universe is essentially infinite, life can escape the limits to growth defined by Earth.  Drexler supports a form of the Fermi paradox, arguing that as there is no evidence of alien civilizations, "Thus for now, and perhaps forever, we can make plans for our future without concern for limits imposed by other civilizations."

Nanosystems (1992)
Drexler's 1992 book, Nanosystems: molecular machinery, manufacturing, and computation is a technical treatment of similar material. Nanosystems addresses chemical, thermodynamic, and other constraints on nanotechnology and manufacturing.

Engines of Creation 2.0 (2007)
An updated version of the book, Engines of Creation 2.0, which includes more recent papers and publications, was published as a free ebook on February 8, 2007.

Reception
The book and the theories it presents have been the subject of some controversy. Scientists such as Nobel Laureate Richard Smalley and renowned chemist George M. Whitesides have been particularly critical. Smalley has engaged in open debate with Drexler, attacking the views presented for what he considered both the dubious nature of the science behind them, and the misleading effect on the public's view of nanotechnology.

See also
The Limits to Growth, 1972 report
 Planetary boundaries

References

External links
Full text of version 1.0 (1986) 
Full text in Italian: MOTORI DI CREAZIONE - L'era prossima della nanotecnologia
Full text in Chinese: 创造的发动机
Drexler's personal website and digital archive
Biography of K. Eric Drexler 
"Engines of Creation – Nanotechnology Will Save Us" Synopsis by Dan Geddes

1986 non-fiction books
1986 in the environment
Nanotechnology books
Futurology books
SIGCOMM. SIGCOMM is the Association for Computing Machinery's Special Interest Group on Data Communications, which specializes in the field of communication and computer networks. It is also the name of an annual 'flagship' conference, organized by SIGCOMM, which is considered to be the leading conference in data communications and networking in the world. Known to have an extremely low acceptance rate (~10%), many of the landmark works in Networking and Communications have been published through it.

Of late, a number of workshops related to networking are also co-located with the SIGCOMM conference. These include Workshop on Challenged Networks (CHANTS), Internet Network Management (INM), Large Scale Attack Defense (LSAD) and Mining Network Data (MineNet).

SIGCOMM also produces a quarterly magazine, Computer Communication Review, with both peer-reviewed and editorial (non-peer reviewed) content, and a bi-monthly refereed journal IEEE/ACM Transactions on Networking, co-sponsored with IEEE.

SIGCOMM hands out the following awards on an annual basis
 The SIGCOMM Award, for outstanding lifetime technical achievement in the fields of data and computer communications 
 The Rising Star Award, for a young research under the age of 35 who has made outstanding contributions during this early part of their career.
 The Test of Time Award recognizes papers published 10 to 12 years in the past in a SIGCOMM sponsored or co-sponsored venue whose contents still represent a vibrant, useful contribution. 
 Best Paper Award and the Best Student Paper Award at that year's conference.
 The SIGCOMM Doctoral Dissertation Award recognizes excellent thesis research by doctoral candidates in the field of computer networking and data communication.
 The SIGCOMM Networking Systems Award recognizes the development of a networking system that has had a significant impact on the world of computer networking.

References

Association for Computing Machinery Special Interest Groups
Binary File Descriptor library. The Binary File Descriptor library (BFD) is the GNU Project's main mechanism for the portable manipulation of object files in a variety of formats. , it supports approximately 50 file formats and 25 instruction set architectures.

History
When David Henkel-Wallace of Cygnus Support proposed developing the library as a way to open up new business opportunities for the company, Richard Stallman said that it would be difficult; David's response was that it wasn't such a "Big Fucking Deal". Abbreviated to "BFD", this became the library name. "Binary File Descriptor" was invented later as a backronym for "BFD".

Design 

BFD works by presenting a common abstract view of object files. An object file has a "header" with descriptive info; a variable number of "sections" that each has a name, some attributes, and a block of data; a symbol table; relocation entries; and so forth.

Internally, BFD translates the data from the abstract view into the details of the  bit/byte layout required by the target processor and file format. Its key services include handling byte order differences, such as between a little-endian host and big-endian target, correct conversion between 32-bit and 64-bit data, and details of address arithmetic specified by relocation entries.

BFD library can be logically divided into two parts. The front-end and the back-end. The front-end gives a common interface independent of underlying object file view. Users will be interacting with the object files with this interface. Even if the layout of the object files are not known to the user, the user would still be able to use the interface. This hiding of the detail is done with the help of the back-end. The back-end implements how the front-end interface interacts with the object files layout. Whenever a new object files type is introduced the back-end needs to register the type and implement it if it needs to be supported by the BFD application.

Although BFD was originally designed to be a generic library usable by a wide variety of tools, the frequent need to tinker with the API to accommodate new systems' capabilities has tended to limit its use; BFD's main clients are the GNU Assembler (GAS), GNU Linker (GLD), and other GNU Binary Utilities ("binutils") tools, and the GNU Debugger (GDB). As a result, BFD is not distributed separately, but is always included with releases of binutils and GDB. Nevertheless, BFD is a critical component in the use of GNU tools for embedded systems development.

The BFD library can be used to read the structured data out of a core dump.

BFD library usage
Eg: Print object file size using bfd library APIs.

#include "bfd.h"
#include <stdio.h>

int main()
{
  bfd* abfd = bfd_openr("a.o",NULL); 
  printf("%llu\n", bfd_get_size(abfd));
  return 0;
}

Build command:
gcc main.c -lbfd -o output
./output # prints the size

References

External links
 Binutils page, with access to current BFD sources
 objdump implementation, uses many BFD apis

C (programming language) libraries
Executable file formats
Free computer libraries
GNU Project software
Fuzzball router. Fuzzball routers were the first modern routers on the Internet. They were DEC PDP-11 computers (usually LSI-11 personal workstations) loaded with the Fuzzball software written by David L. Mills (of the University of Delaware). The name "Fuzzball" was the colloquialism for Mills's routing software. The software evolved from the Distributed Computer Network (DCN) that started at the University of Maryland in 1973. It acquired the nickname sometime after it was rewritten in 1977.

Six Fuzzball routers provided the routing backbone of the first 56 kbit/s NSFNET, allowing the testing of many of the Internet's first protocols. It allowed the development of the first TCP/IP routing protocols, and the Network Time Protocol. They were the first routers to implement key refinements to TCP/IP such as variable-length subnet masks.

See also

 Interface Message Processor

References

External links
 The Fuzzball, with photographs
 Fuzzball source code, last update in 1992, 16 megabytes

American inventions
Hardware routers
History of telecommunications
Engine turning. Engine turning is a form of ornamental turning. The finishing technique may use lathes or engines to produce a pattern. Aluminium is often the metal chosen to decorate. The technique has been used in various industries, including aircraft and document verification.

Description 
Engine turning is a form of ornamental turning. The technique geometrically applies a single-point cutting tool to produce a decorative metal surface finish pattern.

Traditionally, engine turning referred to Guilloché engraving. In the 20th century, it also came to refer to the different process of  (also known as spotting, jewelling, perlage), which is a fine geometric pattern of overlapping circles abraded onto the surface.

Equipment 
Guilloché engine turning may be done with various machines, including rose engines, straight-line engines, brocade engines, and ornamental turning lathes. Perlage uses an abrasive rotating disk or dowel.

Material 
Aluminium is often the metal chosen to decorate with jewelling, but any appropriate surface can be finely machined to produce intricate repetitive patterns that offer reflective interest and fine detail.

Uses

Aircraft

-style engine turning was used on the sheet metal panels of the engine cowling (nose) of Charles Lindbergh's aircraft, the Spirit of St. Louis.

The sheet metal parts of the World War I Fokker Eindecker fighters aircraft series, especially around the engine cowl and associated sheet metal, are noted for having a "dragged" form of engine turning entirely covering them. The tool creating the "swirls" was repeatedly moved along a short, irregular path each time while pressed against the metal, to create the intricate appearance that was characteristic of the aircraft's sheet-metal parts. It is partly surmised to have been a mechanical method to "clad" a duralumin-alloy sheet-metal panel with a layer of pure aluminum, for corrosion protection.

Automobiles

In the 1920s and 1930s, automobile parts such as valve covers, which are right on top of the engine, were also decorated with perlage engine turning. Similarly, dashboards or the instrument panel of the same were often perlaged. Customizers also would similarly decorate their vehicles with perlage engine-turned panels.

Documents
Engravings produced by engine turning are often incorporated into the design of bank notes, and other high-value documents, to make counterfeiting difficult. The resulting graphics are called guillochés.

Firearms

Perlage engine turning is also used on various firearm components to prevent corrosion by holding traces of oil and lubricants on the surface, in turn to a polished surface resulting in a smooth operation.

Watchmaking 
Guilloché and perlage are traditional techniques used in have been used in the watch-making.

See also
 Guilloché
 
 Rose engine lathe

References

External links

 Engine turning on YouTube by The Unemployed Prop Guy

Visual motifs
Corrosion prevention