omniomni/omni-engineering huggingface dataset:
Security Technical Implementation Guide. A Security Technical Implementation Guide or STIG is a configuration standard consisting of cybersecurity requirements for a specific product. The use of STIGs enables a methodology for securing protocols within networks, servers, computers, and logical designs to enhance overall security. These guides, when implemented, enhance security for software, hardware, physical and logical architectures to further reduce vulnerabilities.

Examples where STIGs would be of benefit is in the configuration of a desktop computer or an enterprise server. Most operating systems are not inherently secure, which leaves them open to criminals such as identity thieves and computer hackers. A STIG describes how to minimize network-based attacks and prevent system access when the attacker is interfacing with the system, either physically at the machine or over a network. STIGs also describe maintenance processes such as software updates and vulnerability patching.

Advanced STIGs might cover the design of a corporate network, covering configurations of routers, databases, firewalls, domain name servers and switches.


See also
CIA triad
Information Assurance
Security Content Automation Protocol

References

External links
NIST Security Configuration Checklists Repository
Security Technical Implementation Guides and Supporting Documents in the Public Area
Online STIG search

Configuration management
Security compliance
Laser converting. For industrial processes, Laser converting or laser digital converting is a production technology that enables device manufacturers to produce features that otherwise would be problematic or even impossible to die-cut, without tooling.

In contrast to traditional mechanical converting, laser digital converting utilizes the features of lasers and advanced software technology to convert parts in extremely high accuracy. In production environment, the laser digital converting is the economics of scale when the production run is short, as there is virtually no 'up-front' cost associated with machine tools making and storage. Also, the turnaround time is minimal as it only involves software interpretation on the imported engineering diagram of the part.

See also
Laser cutting
List of laser articles

Industrial processes
Laser applications
FUDI. FUDI (Fast Universal Digital Interface) is a networking protocol used by the Pure Data patching language invented by Miller Puckette. It is a string-based protocol in which messages are separated by semicolons. Messages are made up of tokens separated by whitespaces, and numerical tokens are represented as strings.

Format 

FUDI is a packet-oriented protocol.

Each message consists of one or more atoms, separated by one or more whitespace characters, and it's terminated by a semicolon character.

An atom is a sequence of one or more characters; whitespaces inside atoms can be escaped by the backslash (ascii 92) character (see Examples below).

A whitespace is either a space (ascii 32), a tab (ascii 9) or a newline (ascii 10).

A semicolon (ascii 59) is mandatory to terminate (and send) a message.
A newline is just treated as whitespace and not needed for message termination.

Implementations

pdsend / pdreceive 

Those command-line tools are distributed with the software Pure Data. They are meant to be used with their counterparts, the classes [netsend] / [netreceive] of Pd.

[netsend] / [netreceive] 

Those classes can be used to transport Pd-messages over a TCP or UDP socket. Both are part of Pd-vanilla.

[netserver] / [netclient] 

Those are part of maxlib and allow bidirectional connections of multiple clients with one server.

Example messages 

 test/blah 123.453 my-slider 12;

 hello this is a message;

 this message continues
 in the following
 line;

 you; can; send; multiple messages; in a line;

 this\ is\ one\ whole\ atom;

 this_atom_contains_a\
 newline_character_in_it;

References

External links 
 https://archive.today/20100704034430/http://wiki.puredata.info/en/FUDI

Network protocols
Constantine Dafermos. Constantine Michael Dafermos (Greek: Κωνσταντίνος Δαφέρμος; born May 26, 1941, Athens) is a Greek-American applied mathematician. He received a Diploma in Civil
Engineering from the National Technical University of Athens (1964) and a Ph.D. in Mechanics from Johns Hopkins University under the direction of Jerald Ericksen (1967). He has been an Assistant Professor at Cornell University (1968-1971) and an Associate Professor (1971-1975) and Professor (1975-) in the Division of Applied Mathematics at Brown University. Since 1984, he has been the Alumni-Alumnae University Professor at Brown.

In recent years, his research has focused on nonlinear hyperbolic systems of conservation laws whose solutions spontaneously develop singularities propagating as shock waves. In particular, he is studying the interplay between thermodynamics and analysis in the theory of these systems and he is analyzing the fundamental role of entropy as a stabilizing agent.

In 2012 he became a fellow of the American Mathematical Society. 
In 2016 he was elected to the National Academy of Sciences.

Awards

Honorary Doctorate, University of Athens, 1987.
Honorary Doctorate, National Technical University (Greece), 1991.
Honorary Doctorate, University of Crete, 2001.
SIAM W.T. and Idalia Reid Prize, 2000.
ISIMM prize, 2014
Norbert Wiener Prize in Applied Mathematics, 2016

Affiliations

Fellow American Academy of Arts and Sciences, 2001-.
Correspondent Member, Academy of Athens, 1988-.
Honorary Professor, Academia Sinica, China, 2004-.
Member, Board of Governors, Weizmann Institute of Science (Israel), 1995-.

Notes

Sources
Brown University, The Division of Applied Mathematics (http://www.dam.brown.edu/)

20th-century Greek mathematicians
National Technical University of Athens alumni
Brown University faculty
Fellows of the Society for Industrial and Applied Mathematics
Fellows of the American Mathematical Society
Members of the United States National Academy of Sciences
Living people
1941 births
Scientists from Athens
Johns Hopkins University alumni
Cornell University faculty
Greek emigrants to the United States
Logical disk. A logical disk, logical volume or virtual disk (VD or vdisk for short) is a virtual device that provides an area of usable storage capacity on one or more physical disk drive(s) in a computer system. The disk is described as logical or virtual because it does not actually exist as a single physical entity in its own right. The goal of the logical disk is to provide computer software with what seems a contiguous storage area, sparing them the burden of dealing with the intricacies of storing files on multiple physical units. Most modern operating systems provide some form of logical volume management.

Levels 
Logical disks can be defined at various levels in the storage infrastructure.

Operating system 
An operating system may define volumes or logical disks and assign each to one physical disk, more than one physical disk or part of the storage area of a physical disk. For example, Windows NT can create several partitions on a hard disk drive, each of which a separate volume with its own file system. Each floppy disk drive, optical disc drive or USB flash drive in Windows NT becomes one volume. Windows NT can also create partitions that span multiple hard disks drives. Each volume is identified with a drive letter.

Storage area network 
Storage area networks (SANs) consolidate inhomogeneous storage devices. As such logical disks or vdisks allow computer programs to access files stored on a SAN.

Storage subsystem 
A hardware-level redundant array of independent disks (RAID) exposes itself to the operating system as one logical disk while the array itself consists of several disks. The operating system either does not know that the hardware with which it is interfacing is a RAID, or knows but still does not concern itself with intricate details of storage. In case of the latter, specialized management, maintenance and diagnostics software dedicated to that specific RAID may run on the operating system.

Motivation
When IBM first released the magnetic disk drive in the 1956 IBM 305, a single disk drive would be directly attached to each system, managed as a single entity. As the development of drives continued, it became apparent that reliability was a problem and systems using RAID technology evolved, so that more than one physical disk is used to produce a single logical disk.

Many modern business information technology environments use a SAN. Here, many storage devices are connected to many host server devices in a network. A single RAID array may provide some capacity to one server, and some capacity to another. Therefore, logical disks are used to partition the available capacity and provide the amount of storage needed by each host from a common pool of logical disks. The  IBM SAN Volume Controller uses the term "vdisk" to refer to these logical disks.

Today, the rationale for the logical disk approach starts to be questioned and solutions that offer more flexibility and better abstraction are increasingly needed.

See also
 Storage virtualization

References

Computer data storage
Storage virtualization
Kapustinskii equation. The Kapustinskii equation calculates the lattice energy UL for an ionic crystal, which is experimentally difficult to determine. It is named after Anatoli Fedorovich Kapustinskii who published the formula in 1956.

{|
|-
|where ||K = 1.20200 J·m·mol−1
|- 
| ||d = 3.45 m
|- 
| ||ν is the number of ions in the empirical formula,
|-
| || z+ and z− are the numbers of elementary charge on the cation and anion, respectively, and
|-
| || r+ and r− are the radii of the cation and anion, respectively, in meters.
|}

The calculated lattice energy gives a good estimation for the Born–Landé equation; the real value differs in most cases by less than 5%.  

Furthermore, one is able to determine the ionic radii (or more properly, the thermochemical radius) using the Kapustinskii equation when the lattice energy is known. This is useful for rather complex ions like sulfate (SO) or phosphate (PO).

Derivation from the Born–Landé equation

Kapustinskii originally proposed the following simpler form, which he faulted as "associated with antiquated concepts of the character of repulsion forces". 

Here, K' = 1.079 J·m·mol−1. This form of the Kapustinskii equation may be derived as an approximation of the Born–Landé equation, below. 

Kapustinskii replaced r0, the measured distance between ions, with the sum of the corresponding ionic radii. In addition, the Born exponent, n, was assumed to have a mean value of 9. Finally, Kapustinskii noted that the Madelung constant, M, was approximately 0.88 times the number of ions in the empirical formula. The derivation of the later form of the Kapustinskii equation followed similar logic, starting from the quantum chemical treatment in which the final term is  where d is as defined above. Replacing r0 as before yields the full Kapustinskii equation.

See also
 Born–Haber cycle

References

Literature
 
 A. F. Kapustinskii; Zhur. Fiz. Khim. Nr. 5, 1943, pp. 59 ff.

Chemical bonding
Crystallography
Eponymous equations of physics
Soviet inventions
Operation Surgeon. Operation Surgeon was a British post-Second World War programme to exploit German aeronautics and deny German technical skills to the Soviet Union.

A list of 1,500 German scientists and technicians was created, with the goal of forcibly removing them from Germany ("whether they like it or not") to lessen the risk of their falling into enemy hands. It was feared that if they remained in Germany, they could enable the Soviet Union to "achieve a long range bomber force superior to any other in the world".

At the operation's inception, many of the scientists had already offered their services to British Commonwealth countries, Sweden, Switzerland, Brazil and South America, and regarded working for the Soviet Union as a last resort, should they be prevented from working in Germany and unable to find employment elsewhere in the west.

Of the scientists relocated from 1946-1947, 100 chose to work for the UK.

British records of the operation were made public in 2006.

See also
 T-Force
 Similar (but separate) attempts to remove German technical information and personnel after the war were:
 Operation Paperclip  - US removal of German rocketry experts and materials.
 TICOM (cryptography)
 Operation Alsos (nuclear weapons)
 Operation Osoaviakhim - a secret Soviet operation under which more than 2,500 former Nazi German specialists were transported from former Nazi Germany to the Soviet Union

References

Further reading
 Matthew Uttley "Operation 'Surgeon' and Britain's post-war exploitation of Nazi German aeronautics", Intelligence and National Security, Volume 17, Number 2, June 2002, pp. 1-26(26) Publisher: Routledge, part of the Taylor & Francis Group
 John Gimbel, Science Technology and Reparations: Exploitation and Plunder in Postwar Germany Stanford University Press, 1990 
 Matthias Judt;  Burghard Ciesla, Technology Transfer Out of Germany After 1945 Harwood Academic Publishers, 1996. 
 John Gimbel U.S. Policy and German Scientists: The Early Cold War, Political Science Quarterly, Vol. 101, No. 3 (1986), pp. 433–451

External links
 Employment of German scientists and technicians: denial policy UK National archives releases March 2006.
 Dark side of the Moon BBC article.

 
Surgeon
Surgeon
Soviet Union–United Kingdom relations
LeanCMMI. LeanCMMI is an approach to software engineering process improvement that integrates agile computing methods with process design and deployment for organization's wishing to improve software engineering capability and achieve a maturity level two or three rating based upon the Software Engineering Institute's Capability Maturity Model Integration (CMMI).

Developed by Broadsword, LeanCMMI is based on Lean Engineering and the same concepts that spawned Extreme Programming (XP), Scrum, and Crystal, and traces its roots back to Edward Demings' "Theory of Profound Knowledge." Based upon the principle of "Just Enough Not Too Much," LeanCMMI maps the software process improvement journey across three major releases, each with seven iterations based on three "dimensions" of software process improvement each with equal weight and with equal importance to the success of the program.

Three Dimensions of Process Deployment 

Dimension 1: Design - Design and build the process along with all of its artifacts

Virtual teams develop a set of common, standard process deliverables that meet the requirements of their process area

Dimension 2: Communicate - Determine who received what message when

Virtual teams develop a strategy for communicating their work including identifying what message is delivered to each stakeholder group

Dimension 3: Educate - Determine who receives what CMMI training CMMI audit, at what level, at which time

Virtual teams develop training strategy and materials including identifying what level or training is delivered to each stakeholder group

Acceptance Test 

LeanCMMI uses a series of CMMI SCAMPI B and C Appraisals to be performed at the end of each Release in order to validate the contents of the Release and identify any gaps in the processes as it relates to the CMMI model.  This additive approach reduces risk and helps to ensure that a successful SCAMPI A Appraisal can be performed at the conclusion of the program.

Virtual Enduring Teams 

LeanCMMI requires an enduring virtual organization approach that levels the effort across all stakeholders with a five percent re-direct effort estimated for the duration of the program.  Organized into virtual teams called Special Interest Groups, or SIGs, these teams are Encapsulated Process Objects that own responsibility for the process, its data, maintenance, training, and communications.  An enduring virtual Software Engineering Process Group, or SEPG, serves as the Process Owner, and provides oversight, direction, and authority for the program.

Membership in the SIGs and SEPG is by opt-in and can rotate but the organizations endure as owners of the process.  This approach is designed to speed cultural adoption of the process by including as many practitioners as possible in the design and deployment phase.

References 

Software development process
Saxonia. Saxonia may refer to:

 Latin for Saxony
 Saxonia (locomotive), first locomotive built in Germany in 1838
 British Rail Class 40 diesel locomotive D229, built by English Electric at Newton-le-Willows, Lancashire
 , more than one passenger ship of the Cunard Line
 The Saxonia Guest House in Somerset, England, featured on the show The Hotel Inspector

See also 
 Saxon (disambiguation)
 Saxony (disambiguation)
ECIS. ECIS may refer to:

European Committee for Interoperable Systems
European Conference on Information Systems
European Council of International Schools
Electric cell-substrate impedance sensing
Eindhoven Centre for Innovation Studies, a research centre based at the School of Innovation Sciences at Eindhoven University of Technology
Evaluación de la Calidad en Interpretación Simultánea, a research group on simultaneous interpreting, based at the University of Granada
Cloud Chamber for the Trees and Sky. Cloud Chamber for the Trees and Sky is a site specific outdoor artwork by Chris Drury. It was commissioned by North Carolina Museum of Art in 2003 made possible by the Robert F. Phifer Bequest and located in the 146 acre museum park adjacent to the museum known as the Ann and Jim Goodnight Museum Park at state capital Raleigh. The artwork is situated in woodland with other large sculptures and is accessed along a woodland path.

The chamber itself is a round building built of stone, wood, and turf approximately 12 feet in diameter (3.66 metres) with a single door to admit the viewer. It is light-tight when its door is closed, except for one small, round opening in its roof which allows the building to act as a camera obscura. Images of the sun, clouds, and trees are projected onto the smooth white walls of the interior of the chamber. Classed as a public artwork, there is no admission charge to the park.

See also
 Camera obscura
 Environmental sculpture

References

External links
 Chris Drury website

Outdoor sculptures in North Carolina
Camera obscuras
Buildings and structures in Raleigh, North Carolina
Numbered highways in New York. The New York State Department of Transportation (NYSDOT) is responsible for the establishment and classification of a state highway network which includes Interstate Highways, U.S. Highways, and state routes. U.S. and Interstate Highways are classified as state routes in New York; however, a letter ("U" or "I", respectively) is suffixed to the number of the route. As a result, there is apparent duplication between U.S. Routes, Interstate Highways and state routes.

The New York state highway system is supplemented by the state's county route system, which comprises a series of highways numbered and maintained by the individual county highway departments. While neighboring New Jersey employs a statewide numbering system, no such system exists in New York. Instead, each county numbers its highways independently of other counties. As a result, county routes typically change numbers when they cross county lines.

In some cases, the state highway and county highway systems overlap. More specifically, some portions of U.S. Routes and state routes in New York are signed as U.S. Routes or state routes but are maintained by the county that the route lies within. These county-maintained segments also carry a county route designation that may or may not be posted alongside the U.S. or state designation, depending on the signing practices of the county. Some state routes, such as New York State Route 148 in Niagara County, are entirely county-maintained.

History

Lists of routes

Thruway

Highways maintained by the New York State Thruway Authority lack any signed numbers apart from Interstate Highway designations. While the vast majority of the Thruway system is part of the Interstate Highway System, some sections, such as the Berkshire Connector between Interstate 87 and Interstate 90, are unsigned reference routes. There are no standard NYSDOT reference markers on any of the highways; instead, the Thruway Authority posts their own mileposts, which (aside from the mainline) bear special Thruway codes.

See also

Transportation in New York
List of New York State Bicycle Routes

External links
New York State Department of Transportation

Numbered Highways
SS William A. Graham. SS William A. Graham (MC hull number 160) was a Liberty ship built by the North Carolina Shipbuilding Company of Wilmington, North Carolina, and launched on 26 July 1942. One of over 2,700 cargo ships produced during an emergency shipbuilding program,  William A. Graham was named for William Alexander Graham, a 19th-century governor of North Carolina and a U.S. Secretary of the Navy.

Constructed in eight weeks, the 441-foot steamship was operated by J. H. Winchester & Company. of New York. On her maiden voyage carrying Lend-Lease supplies to Karachi, William A. Graham narrowly evaded a wolf pack of German submarines off Cape Town in October 1942.  The ship had a second close encounter with the enemy in June 1944, when German bombers attacked the harbor at Anzio where William A. Graham lay at anchor with six other merchantmen.

A record of William A. Grahams maiden voyage is preserved in the diary of the ship’s first assistant engineer, Everett S. Ransom.   Copies of the diary have been donated to nearly 30 libraries and museums around the United States, including the Lower Cape Fear Historical Society, the North Carolina Collection at UNC-Chapel Hill, and the Nimitz Library of the United States Naval Academy.

After the war, William A. Graham carried cargo under different operators until being mothballed in 1952 in a reserve fleet in Mobile, Alabama. In 1972, the ship was purchased for scrap and dismantled by the Union Minerals and Alloys Corporation.

See also
 List of Liberty ships (S–Z)

References
Notes

Bibliography
 Ransom, Everett S. (2005) To Karachi and Back on the William A. Graham: The Wartime Writings of a Merchant Mariner, 1942-43. LCCN 2004094916
 North Carolina Shipbuilding Company (1946). Five Years of North Carolina Shipbuilding
 Lane, Frederic C. Ships for Victory: A History of Shipbuilding under the U.S. Maritime Commission in World War II. 

1942 ships
Liberty ships
Ships built in Wilmington, North Carolina
Kitware. 

Kitware, Inc. is a technology company headquartered in Clifton Park, New York. The company is involved in the research and development of open-source software in the fields of computer vision, medical imaging, visualization, 3D data publishing, and technical software development.

History
The company was founded in 1998 by Will Schroeder, Ken Martin, Lisa Avila, Charles Law and Bill Hoffman to support the Visualization Toolkit (VTK). VTK was initially created in 1993 by Schroeder, Martin and Bill Lorensen as companion software to “The Visualization Toolkit: An Object-Oriented Approach to 3D Graphics," originally published by Prentice-Hall.  As VTK was released open source, a user community developed around the software and the founders of Kitware took this opportunity to start the business. Later, the company expanded its focus and offerings to include development in other areas such as biomedical imaging, large data visualization, quality software process, informatics, and data management.

The company has four additional offices: Carrboro, North Carolina; Minneapolis, Minnesota; Santa Fe, New Mexico; Arlington, Virginia; and Kitware SAS, the European office, in Lyon, France.

Kitware contributes to many popular open-source projects, such as VTK and CMake.

References

Companies based in New York (state)
Data and information visualization software