omniomni/omni-engineering huggingface dataset:
William Otis. William Smith Otis (September 20, 1813 – November 13, 1839) was an American inventor of the steam shovel. Otis received a patent for his creation on February 24, 1839.

In 1839 William Smith Otis, civil engineer of Philadelphia, Pennsylvania, was issued a US patent for the steam shovel (No. 1,089) for excavating and (removing earth). Officially the patent drawing is missing but a drawing exists which is said to be the one from the patent and this shows the crane mounted on a railroad car. A load of earth could be lifted by the bucket, raised by the crane and turned to be dumped, such as in railcars. The patent described how a steam engine of a type then in ordinary use, was installed with a power control mechanism for the crane, and a system of pulleys to move its arms and bucket. It could move about 380 cubic meters of earth a day, with its 1.1 cubic meter capacity shovel and 180° slewing wooden jib. It was first used on the Western Railroad in Massachusetts.

Otis was born on September 20, 1813, in Pelham, Massachusetts. He was a cousin of Elisha Otis of elevator fame.  At an early age, William was interested in earthworks and mechanics. At the age of 22, he had shown an uncommon mechanical ingenuity and created the first steam powered mechanical excavator.

Using materials obtained in vicinity of Canton, Massachusetts, William created the machine in 1835 which was used building railroad lines between Norwich and Worcester.  Working with the company, ”Carmichael and Fairbanks”, William Smith Otis devised an apparatus carrying out the same actions as the person with a shovel.

Otis moved to Philadelphia and enlisted the talents of engineer and inventor Joseph Harrison Jr. to help construct a prototype.  Harrison operated the company ”Garrett and Eastwick," and fabricated a pre-production model in 1836.  On June 15, 1836, William Smith Otis received the patent for the invention; however during a fire, the engineering specifications had been destroyed.

On February 24, 1839, the patent behind number 1089 officially entered validity, and called “Crane-Excavator for Excavating and Removing Earth”.

Otis died of typhoid fever on November 13, 1839, at the age of 26.

See also
Boston's Back Bay: The Story of America's Greatest Nineteenth-century  Landfill, by William A. Newman and Wilfred E. Holton, Northeastern University Press,  Boston,  published by University Press of New England, 2006. See Chapter 4, Locomotives and Steam Shovels, Pg. 79.
 Marion Steam Shovel
 Osgood Company

References

1813 births
1839 deaths
People from Pelham, Massachusetts
19th-century American inventors
Compilers: Principles, Techniques, and Tools. Compilers: Principles, Techniques, and Tools is a computer science textbook by Alfred V. Aho, Monica S. Lam, Ravi Sethi, and Jeffrey D. Ullman about compiler construction for programming languages. First published in 1986, it is widely regarded as the classic definitive compiler technology text.

It is known as the Dragon Book to generations of computer scientists as its cover depicts a knight and a dragon in battle, a metaphor for conquering complexity. This name can also refer to Aho and Ullman's older Principles of Compiler Design.

First edition
The first edition (1986) is informally called the "red dragon book" to distinguish it from the second edition  and from Aho & Ullman's 1977 Principles of Compiler Design sometimes known as the "green dragon book".
Topics covered in the first edition include:
Compiler structure
Lexical analysis (including regular expressions and finite automata)
Syntax analysis (including context-free grammars, LL parsers, bottom-up parsers, and LR parsers)
Syntax-directed translation
Type checking (including type conversions and polymorphism)
Run-time environment (including parameter passing, symbol tables and register allocation)
Code generation (including intermediate code generation)
Code optimization

Second edition
Following in the tradition of its two predecessors, the second edition (2006) features a dragon and a knight on its cover, and is informally known as the purple dragon. Monica S. Lam of Stanford University became a co-author with this edition.

The second edition includes several additional topics, including:
 Directed translation
 New data flow analyses
 Parallel machines
 Garbage collection
 New case studies

Updated second edition
In order to cover recent developments and issues, there is an updated second edition from Pearson Education India (4 July 2023), with contributions from Sorav Bansal. This revised and updated edition has new chapters on programming language semantics and undefined behaviour semantics.

See also
Structure and Interpretation of Computer Programs

References

Further reading

External links
 Book Website at Stanford with link to Errata

1986 books
2006 non-fiction books
Compiler construction
Computer science books
Engineering textbooks
Compiler theory
Semantic analysis (compilers). Semantic analysis or context sensitive analysis is a process in compiler construction, usually after parsing, to gather necessary semantic information from the source code. It usually includes type checking, or makes sure a variable is declared before use which is impossible to describe in the extended Backus–Naur form and thus not easily detected during parsing.

See also 
 Attribute grammar
 Context-sensitive language
 Semantic analysis (computer science)

References

Compiler construction
Program analysis
Al-Samoud 2. Al-Samoud (الصمود, alternately Al-Samed, which means steadfastness in Arabic) was a liquid-propellant rocket tactical ballistic missile developed by Iraq in the years between the Gulf War and the 2003 Invasion of Iraq. The Iraqi army also developed a solid-fuel rocket version known as Ababil-100.

Development 
The missile was essentially a scaled-down Scud, though parts were mostly derived from the Soviet S-75 Dvina surface-to-air missile. The first test-firing was carried out as early as 1997 and was supervised by UNSCOM. The production started in 2001, and the goal was the assembly of ten missiles each month. The Al Samoud 2 was not fully operational by 2003, but some of them had been already delivered to the Iraqi army.

Engine 
The rocket engine evolved from the S-75 Dvina design and the thrust vector controls from the Scud.
The system also included an Iraqi-designed mobile launcher similar to the Al-Nida, built for the missile Al Hussein, produced by the Iraqi company Al-Fida.

Payload 
The missile carried a 280 kilogram warhead that was half high explosives and half protective steel shell. The explosive charge weighed 140 kg, made of a mixture of 84 kg of RDX=60%, 42 kg of TNT= 30% and 14 kg of aluminium= 10%, the latter used as an energetic blast enhancer. The payload was also designed to upload different types of bomblets.

Guidance 
The guidance package was assembled by cannibalizing gyroscopes from the Chinese Silkworm cruise missile. A source is cited as claiming that there were inertial and even GPS guidance systems illegally imported from Belarus, but these allegations have not been confirmed.

Banned by the UN 

On February 13, 2003, a UN panel reported that Iraq's Al-Samoud 2 missiles, disclosed by Iraq to weapons inspectors in December, have a range of 180 km, in breach of UNSCR 1441. The limit allowed by the UN is 150 km.

Iraq agreed to destroy the Al-Samoud 2 long range missiles, and by mid-March 2003, a number had been destroyed. Although UNMOVIC ordered to stop its production, Iraq assembled some 20 missiles during the early months of 2003.

American forces found a cache of 12 Al Samoud missiles south of Baiji on July 21, 2003.

Operational history (March–April 2003) 

A number of Al-Samoud 2 missiles were fired at Kuwait during the 2003 conflict. One of them, aimed at the Coalition Headquarters at Camp Doha, was successfully intercepted by a Patriot missile on March 27. Some debris hit buildings inside the US base. The other missiles were also shot down or landed harmlessly in the desert.

A similar development, the Al-Fahd or Ababil-100, a solid propellant version of the Al-Samoud, was also used by the Iraqi army during the invasion. The Headquarters of the 2nd Brigade, US 3rd Infantry Division, were struck south of Baghdad by a missile of this kind on April 7. Three soldiers and two foreign reporters were killed in the blast.

See also 

 List of missiles

References 

Tactical ballistic missiles of Iraq
Ballistic missiles of Iraq
Short-range ballistic missiles of Iraq
Surface-to-surface missiles of Iraq
Theatre ballistic missiles
Military equipment introduced in the 2000s
Sillimanite. Sillimanite or fibrolite is an aluminosilicate mineral with the chemical formula Al2SiO5. Sillimanite is named after the American chemist Benjamin Silliman (1779–1864). It was first described in 1824 for an occurrence in Chester, Connecticut.

Occurrence
Sillimanite or fibrolite is one of three aluminosilicate polymorphs, the other two being andalusite and kyanite. A common variety of sillimanite is known as fibrolite, so named because the mineral appears like a bunch of fibres twisted together when viewed in thin section or even by the naked eye. Both the fibrous and traditional forms of sillimanite are common in metamorphosed sedimentary rocks. It is an index mineral indicating high temperature but variable pressure. Example rocks include gneiss and granulite. It occurs with andalusite, kyanite, potassium feldspar, almandine, cordierite, biotite and quartz in schist, gneiss, hornfels and also rarely in pegmatites. Dumortierite and mullite are similar mineral species found in porcelain.

Sillimanite has been found in Brandywine Springs, New Castle County, Delaware. It was named by the State Legislature in 1977 as the state mineral of Delaware by the suggestion of the Delaware Mineralogical Society.

Uses
Natural sillimanite is used in the manufacture of high alumina refractories or 55–60% alumina bricks. However, it has mostly been replaced by the other aluminosilicate polymorphs, andalusite and kyanite, for this purpose. , sillimanite was just 2% of all aluminosilicate mineral production in the western world.

Gallery

See also

List of minerals
List of minerals named after people
Asbestos cement, which is also called "fibrolite"

References

Aluminium minerals
Nesosilicates
Orthorhombic minerals
Minerals in space group 62
Industrial minerals
Symbols of Delaware
CDM. CDM may refer to:

Arts and media
 Celebrity Deathmatch, a TV series
 CD maxi, a music release format

Organizations
 College of Dental Medicine, US dental schools
 DePaul University College of Computing and Digital Media, in Chicago, Illinois, US
 Corona del Mar High School, a high school in Newport Beach, California, US

Science and technology

Computing
 Combining Diacritical Marks, for keyboards
 Common Diagnostic Model, an information technology standard of the Distributed Management Task Force
 Conceptual data model, in database design
 Content Decryption Module, used in digital rights management
 Customer data management, software and behaviors for businesses to handle customer data
 Continuous Diagnostics and Mitigation, a program of the Department of Homeland Security; see Federal Systems Integration and Management Center

Other uses in science and technology
 Cash deposit machine, in banks
 Clean Development Mechanism, a mechanism in the Kyoto Protocol for reducing emissions
 Ceramic metal-halide lamp, a light source
 Charged-device model, used in electrostatic discharge testing
 Clinical data management, in medical research
 Code division multiplexing, in radio communications
 Cold dark matter, a theory in physics
 Combustion detection module, in Saab automobiles
 Congenital dermal melanocytosis, a benign birthmark

Other uses
 Charge description master, a comprehensive price list of items billable to patients in a US hospital
 Chidambaram railway station, Cuddalore, Tamil Nadu, India (Indian Railways station code CDM)
 Construction (Design and Management)
 Construction (Design and Management) Regulations 2007, UK construction regulations
 Construction (Design and Management) Regulations 2015, UK construction regulations
 Corona del Mar, Newport Beach, a beach and community in California, US

 Clergy Discipline Measure 2003, a legal measure in the Church of England
 Central defensive midfielder, a position in association football
 Christian electronic dance music, also known as CDM

See also
 Lambda-CDM model or ΛCDM model, standard cosmological model of the universe
USS Langley. USS Langley may refer to:

Ships:
, the first aircraft carrier of the United States Navy, converted from the collier Jupiter in 1922, and scuttled in February 1942 after being disabled by the Japanese
, laid down 10 July 1942 and renamed Hammann on 1 August 1942
, a light aircraft carrier commissioned in 1943, active in World War II, and transferred to France in 1951

Others:
USS Langley, a Unix Space Server which provides proof of concept for global internet access via a nanosatellite constellation. The satellite was launched aboard the Atlas V mission designated as USA-261 on 20 May 2015.

United States Navy ship names
LBG. LBG can refer to:

 Lake Burley Griffin, an artificial lake in the centre of Canberra
 Landenberg, Pennsylvania
 Laurinburg, North Carolina
 Limbe Botanic Garden
 Linde–Buzo–Gray algorithm, an algorithm to derive a good codebook for vector quantization
 Lindesberg, a Swedish town
 Liquid biogas
 Lloyds Banking Group
 Location based game
 Locust bean gum, a galactomannan vegetable gum
 London Bridge station, in the UK National Rail code
 Louis Béland-Goyette, a Canadian soccer player
 Lyman-break galaxy
 Paris–Le Bourget Airport, IATA airport code
 The LBG, a rock band from Chennai, India
Anorthite. Anorthite (an = not, ortho = straight) is the calcium endmember of the plagioclase feldspar mineral series. The chemical formula of pure anorthite is CaAl2Si2O8. Anorthite is found in mafic igneous rocks. Anorthite is rare on the Earth but abundant on the Moon.

Mineralogy 

Anorthite is the calcium-rich endmember of the plagioclase solid solution series, the other endmember being albite (NaAlSi3O8).  Anorthite also refers to plagioclase compositions with more than 90 molecular percent of the anorthite endmember. The composition of plagioclases is often expressed as a molar percentage of An%, or (for a specific quantity) Ann, where n = Ca/(Ca + Na) × 100. This equation predominantly works in a terrestrial context; exotic locales and in particular Lunar rocks may need to account for other cations, such as Fe2+, to explain differences between optically and structurally derived An% data observed in Lunar anorthites.

At standard pressure, pure (An100) anorthite melts at .

Occurrence
Anorthite is a rare compositional variety of plagioclase. It occurs in mafic igneous rock. It also occurs in metamorphic rocks of granulite facies, in metamorphosed carbonate rocks, and corundum deposits.  Its type localities are Monte Somma and Valle di Fassa, Italy. It was first described in 1823.  It is more rare in surficial rocks than it normally would be due to its high weathering potential in the Goldich dissolution series.

It also makes up much of the lunar highlands; the Genesis Rock, collected during the 1971 Apollo 15 mission, is made of anorthosite, a rock composed largely of anorthite. Anorthite was discovered in samples from comet Wild 2, and the mineral is an important constituent of Ca-Al-rich inclusions in rare varieties of chondritic meteorites.

See also 
List of minerals
Lunar highlands
Lunar regolith

References 

Tectosilicates
Calcium minerals
Feldspar
Triclinic minerals
Gemstones
Minerals in space group 2
LCARS. In the Star Trek fictional universe, LCARS (; an acronym for Library Computer Access/Retrieval System) is a computer operating system.  Within Star Trek chronology, the term was first used in the Star Trek: The Next Generation series.

Production
The LCARS graphical user interface was designed by scenic art supervisor and technical consultant Michael Okuda. The original design concept was influenced by a request from Gene Roddenberry that the instrument panels not have a great deal of activity on them. This minimalized look was designed to give a sense that the technology was much more advanced than in the original Star Trek.

On Star Trek: The Next Generation, many of the buttons were labeled with the initials of members of the production crew and were referred to as "Okudagrams."

PADD

The LCARS interface is often seen used on a PADD (Personal Access Display Device), a hand-held computer.

At , similarly sized modern tablet computers such as the Nexus 7, Amazon Fire, BlackBerry PlayBook, and iPad Mini have been compared with the PADD.  Several mobile apps were created  which offered an LCARS-style interface.

Legal
CBS Television Studios claims to hold the copyright on LCARS. Google was sent a DMCA letter to remove the Android app called Tricorder since its use of the LCARS interface was un-licensed. The application was later re-uploaded under a different title, but it was removed again.

References

External links

Fictional software
Operating systems
Star Trek terminology
Java APIs for Integrated Networks. Java APIs for Integrated Networks (JAIN) is an activity within the Java Community Process, developing APIs for the creation of telephony (voice and data) services. Originally, JAIN stood for Java APIs for Intelligent Network. The name was later changed to Java APIs for Integrated Networks to reflect the widening scope of the project. The JAIN activity consists of a number of "Expert Groups", each developing a single API specification.

Trend
JAIN is part of a general trend to open up service creation in the telephony network so that, by analogy with the Internet, openness should result in a growing number of participants creating services, in turn creating more demand and better, more targeted services.

Goal
A goal of the JAIN APIs is to abstract the underlying network, so that services can be developed independent of network technology, be it traditional PSTN or Next Generation Network.

API
The JAIN effort has produced around 20 APIs, in various stages of standardization, ranging from Java APIs for specific network protocols, such as SIP and TCAP, to more abstract APIs such as for call control and charging, and even including a non-Java effort for describing telephony services in XML.

Parlay X
There is overlap between JAIN and Parlay/OSA because both address similar problem spaces. However, as originally conceived, JAIN focused on APIs that would make it easier for network operators to develop their own services within the framework of Intelligent Network (IN) protocols. As a consequence, the first JAIN APIs focused on methods for building and interpreting SS7 messages and it was only later that JAIN turned its attention to higher-level methods for call control. Meanwhile, at about the same time JAIN was getting off the ground, work on Parlay began with a focus on APIs to enable development of network services by non-operator third parties.

Standardized APIs
From around 2001 to 2003, there was an effort to harmonize the not yet standardized JAIN APIs for call control with the comparable and by then standardized Parlay APIs. A number of difficulties were encountered, but perhaps the most serious was not technical but procedural. The Java Community Process requires that a reference implementation be built for every standardized Java API. Parlay does not have this requirement. Not surprisingly, given the effort that would have been needed to build a reference implementation of JAIN call control, the standards community decided, implicitly if not explicitly, that the Parlay call control APIs were adequate and work on JAIN call control faded off. Nonetheless, the work on JAIN call control did have an important impact on Parlay since it helped to drive the definition of an agreed-upon mapping of Parlay to the Java language.

See also
 NGIN
 Parlay Group

External links
 The JAIN APIs.
 JAIN-SIP.
 JAIN-SIP (new site).

Books 
 
 
 

Integrated Networks
Telecommunications standards
Computer standards
Brad Cox. Brad J. Cox (May 2, 1944 – January 2, 2021) was an American computer scientist who was known mostly for creating the Objective-C programming language with his business partner Tom Love and for his work in software engineering (specifically software reuse) and software componentry.

Biography
Cox received his Bachelor of Science Degree in Organic Chemistry and Mathematics from Furman University,
and his Ph.D. from the Department of Mathematical Biology at the University of Chicago.
Among his first known software projects, he wrote a PDP-8 program for simulating clusters of neurons.

He worked at the National Institutes of Health and Woods Hole Oceanographic Institute before moving into the software profession.

Although Cox invented his own programming language, Objective-C, which he used in his early career, he stated in an interview for the Masterminds of Programming book that he wasn't interested in programming languages but rather in software components, and he regarded languages as mere tools for building and combining parts of software.

Cox was also an entrepreneur, having founded the Stepstone company together with Tom Love, established to release the first Objective-C implementation. Stepstone folded in 1994 and in April 1995, NeXT acquired the Objective-C trademark and rights from Stepstone. At the same time, Stepstone licensed back from NeXT the right to continue selling their Objective-C based products. As Apple Computer acquired NeXT a year later, they now hold the rights to Objective-C. Stepstone appears to have gone out of business in the early 2000s.

Awards

 Online course "Taming the Electronic Frontier" won a Paul Allen Distance Education Award ($25,000) in 1998.

Notes

Books

External links
Belaboring the Obvious His personal blog
VirtualSchool.edu (archived 2017) A website for hosting his miscellaneous works

1944 births
2021 deaths
Furman University alumni
Programming language designers
American software engineers
University of Chicago alumni
LCFG. LCFG stands for "Local ConFiGuration system". Developed at the University of Edinburgh beginning around 1993, it is "a system for automatically installing and managing the configuration of large numbers of computer systems. It is particularly suitable for sites with very diverse and rapidly changing configurations".

System architecture

Source:

 The configuration of the entire site is described in a set of source files, held on a central server. Note that one source file does not (necessarily) correspond to one machine; a source file typically describes one aspect of the overall configuration, such as "parameters specific to student machines", or "parameters specific to Scientific Linux machines". An individual parameter may be affected by more than one source file.
 The source files are compiled into individual profiles. One profile corresponds to one machine, and the profile contains all the configuration parameters necessary to recreate the configuration of the target machine. The profiles are published on a web server.
 When a profile changes, the corresponding client is sent a simple UDP notification. The client retrieves the profile using HTTP, and caches the parameters in a DBM file. Clients normally poll periodically for new configurations in case the notification has been missed.
 Clients periodically send a simple UDP acknowledgement to the server. These are collated to generate a web page showing status information for all the clients.
 Component scripts on the client are responsible for reading the configuration parameters and taking the appropriate actions necessary to implement the configuration; usually this involves generating configuration files from the parameters in the profile.  Components are notified when a new configuration is received which involves a change to some parameter of that component. The component regenerates any necessary configuration files, and notifies any associated daemons.

See also

 Computer-aided maintenance
 Quattor
 Comparison of open source configuration management software

References

External links

Configuration management