omniomni/omni-engineering huggingface dataset:
Defense Switched Network. The Defense Switched Network (DSN) is a primary information transfer network for the Defense Information Systems Network (DISN) of the United States Department of Defense.  The DSN provides the worldwide non-secure voice, secure voice, data, facsimile, and video teleconferencing services for DOD Command and Control (C2) elements, their supporting activities engaged in logistics, personnel, engineering, and intelligence, as well as other federal agencies.

In 1982, the DSN was designated by the Office of the Secretary of Defense (OSD) and the Joint Chiefs of Staff (JCS) as the provider of long-distance communications service for the DOD.  The DSN is designated as a primary system of communication during peacetime, periods of crisis, preattack, non-nuclear, and post-attack phases of war.  The network assures nonblocking service for users with "flash" and "flash override" precedence capabilities. Key users include the National Command Authorities, Commanders of the Combatant Commands, and subordinate component commanders. DSN replaced the older Autovon system.

The DSN consists of four subsystems:
Switching,
Transmission,
Timing and Synchronization, and
Network Administration and Management.
The DSN Switching Subsystem consists of multifunction, stand-alone tandem, end office, and remote switching units.  Using the transmission, timing, and control elements of the DISN, they interconnect all military locations worldwide and provide end-to-end long-distance common user and dedicated voice, secure voice, data, and video services worldwide.

In addition to nonsecure voice, data, and video services, the DSN will provide transmission, switching, and support services for Secure Telephone Units, Third Generation (STU-IIIs, now obsolete), the Secure Terminal Equipment (STE), the Defense Red Switch Network (DRSN), the dial-up alternative routing for the Unclassified  but Sensitive Internet Protocol (IP) Router Network (NIPRNet), and the Secret IP Router Network (SIPRNet). The DSN can also provide access to the Government Emergency Telephone System (GETS).

Area codes
Eight area codes are used to cover certain geographical areas for regular voice communications:
311 for AFRICOM
312 for the Continental United States (NORTHCOM) and Puerto Rico
313 for the Caribbean
314 for EUCOM
315 for INDOPACOM
317 for Alaska
318 for CENTCOM
319 for Canada (Canadian Switched Network (CSN))

Other area codes are assigned to functional areas:
20x for interface with the United Kingdom's Defence Fixed Telecommunications Service (DFTS)
606 for interface with NATO's Core Network (NCN)
7xx for interface with Australia's Defence Voice Network (DVN)
715 for interface with New Zealand's Defence Telephone Network (DTelN)

References

External links
 Defense Information Systems Agency (DISA)
 DISA Media Resources Page
 A brief history of the DSN US Government Defense Information Systems Agency
 DSN Movie US Government Defense Information Systems Agency
 DSN Movie Transcript US Government Defense Information Systems Agency

United States Department of Defense agencies
Military communications of the United States
PostScript Printer Description. PostScript Printer Description (PPD) files are created by vendors to describe the entire set of features and capabilities available for their PostScript printers.

A PPD also contains the PostScript code (commands) used to invoke features for the print job. As such, PPDs function as drivers for all PostScript printers, by providing a unified interface for the printer's capabilities and features. For example, a generic PPD file for all models of HP Color LaserJet contains:
*% =================================
*% Basic Device Capabilities
*% =================================
*LanguageLevel: "2"
*ColorDevice: True
*DefaultColorSpace: CMYK
*TTRasterizer: Type42
*FileSystem: False
*Throughput: "10"
which specifies that the printer understands PostScript Level 2, is a color device, and so forth. The PPD can describe allowable paper sizes, memory configurations, the minimum font set for the printer, and even specify a tree-based user interface for printer-specific configuration.

A PPD is also often called PostScript Page Description instead of Printer Description, this is because PostScript has the concept of Page Devices where the PostScript page description configuration is read from or saved as a PPD file.

CUPS 
CUPS uses PPD drivers for all of its PostScript printers, and has even extended the concept to allow for PostScript printing to non-PostScript printing devices, by directing output through a CUPS filter. Such a file is no longer a standard PPD, but rather a "CUPS-PPD".
CUPS clients usually read the current PPD file from the server every time a new print job is created. It is located in /usr/share/ppd/ or /usr/share/cups/model/.
/usr/share/ppd
├── cupsfilters
│   ├── Fuji_Xerox-DocuPrint_CM305_df-PDF.ppd
│   ├── Generic-PDF_Printer-PDF.ppd
│   ├── HP-Color_LaserJet_CM3530_MFP-PDF.ppd
│   ├── pxlcolor.ppd
│   ├── pxlmono.ppd
│   └── Ricoh-PDF_Printer-PDF.ppd
├── cups-pdf
│   ├── CUPS-PDF_noopt.ppd
│   └── CUPS-PDF_opt.ppd
└── custom

Windows 
Microsoft Windows also uses PPD files but converts these to a binary .BPD file format before using them. These, both PPD and BPD, are normally stored in %WINDIR%\system32\spool\drivers\w32x86\3 on an x86 system, or %WINDIR%\System32\spool\drivers\x64\3 on a 64 bit system.

Updating a PPD file requires four steps:
 stop the spooling service;
 edit the existing PPD file in place or replace it by an updated version;
 remove the old BPD file;
 restart the spooling service.
This will automatically generate a new BPD from the updated PPD.

MIME type 
The MIME type for the CUPS variant of PPD is application/vnd.cups-ppd.

References

External links 
 Adobe PostScript Language Specifications
 Adobe Tech Note 5003: PostScript Printer Description (PPD) File Format Specification, hosted on MIT
 Adobe Tech Note 5645: Update to PPD Specification Version 4.3, hosted on MIT

Computer file formats
PostScript
Defensive design. Defensive design is the practice of planning for contingencies in the design stage of a project or undertaking. Essentially, it is the practice of anticipating all possible ways that an end-user could misuse a device, and designing the device so as to make such misuse impossible, or to minimize the negative consequences. For example, if it is important that a plug is inserted into a socket in a particular orientation, the socket and plug should be designed so that it is physically impossible to insert the plug incorrectly. Power sockets are often keyed in such a manner, to prevent the transposition of live and neutral. They are also recessed in the wall in a way that makes it impossible to touch connectors once they become live.

Defensive design in software engineering is called defensive programming. Murphy's law is a well-known statement of the need for defensive design, and also of its ultimate limitations.

Applications

Computer software 

Implementation decisions and software design approaches can make software safer and catch user errors.
Code that implements this is termed a sanity check.

 Data entry screens can "sanitize" inputs, e.g. numeric fields contain only digits, signs and a single decimal point if appropriate.

 Inputs can be checked for legitimate values, e.g. for counts of workplace injuries (or number of people injured) the number can be 0 but can't be negative and must be a whole number; for number of hours worked in one week the amount for any specified employee can be 0, can be fractional, but can't be negative and can't be greater than 168, nor more than 24 times the number of days they were in attendance.

 A word processor requested to load a saved document should scan it to ensure it is in good form and not corrupted. If it is corrupted, the program should say so, then either accept the partial document that was valid, or refuse the entire document. In either case it should remain running and not quit.

Electronics 

Many electrical connectors apply this principle by being asymmetric.
Alternatively, USB-C plugs are mechanically but not electrically symmetric, but achieve an illusion of symmetry resulting from how devices respond to the cable, and hence can be plugged in either of two ways. Accompanying circuitry makes the plugs and cables behave as though they are symmetric.

See also
 Defensible space theory
 Fail-safe
 Idiot-proof
 Inherent safety
 Poka-yoke
 Usability testing

References 

Design
Datapoint's Advanced Systems Language. DASL (Datapoint's Advanced Systems Language) was a programming language and compiler proprietary to Datapoint.  Primarily influenced by Pascal with some C touches, it was created in the early 1980s by Gene Hughes.

The compiler output was assembly language, which was typically processed through a peep-hole optimizer before the assembler and linker.

Reflecting its name, DASL was used for systems programming, mainly by the vendor itself.

References

External links & References
The Dasl Document

Systems programming languages
List of weapons of military aircraft of Germany during World War II. During World War II, the Luftwaffe (German air force) equipped their aircraft with the most modern weaponry available until resources grew scarce later in the war.

Machine guns
(Maschinengewehr)
 MG 15
 MG 17
 MG 81 & 81Z
 MG 131

Autocannon 
(Maschinenkanone and related types)

 MG FF and FF/M [1]
 MG 151, /15 or /20 [1]
 MK 101
 MK 103
 MK 108

[1] The official designation for MG FF and MG 151 was Maschinengewehr but they are cannon.

Heavy aircraft cannon
(Bordkanone)
 BK 3.7
 BK 5
 BK 7.5 (based on Rheinmetall's 7.5 cm Pak 40 with self-contained twelve-round magazine)

Rockets and Missiles
 Kramer Rk 344, air-to-air missile (liquid-fuel, rocket-powered)
 Henschel Hs 293, guided anti-ship, boost-glide missile
 R4M rocket
 Werfer-Granate 21 heavy-calibre air-to-air unguided rocket

Bombs

High explosive 
"Sprengcylindrisch"' (high-explosive)

 SC 50
 SC 250
 SC 500
 SC 1000 "Hermann"
 SC 1200
 SC 1800 "Satan"
 SC 2000
 SC 2500 "Max"
 SC 500J
 SB 1000
 SB 1800
 SB 2500

Anti-personnel 
"Splitterbomben-Dickwandig"' (Shrapnel)
 SD 1
 SD 1 FRZ
 SD 2
 SD 4 HL
 SD 4/HL RS
 SD 9/HL
 SD 10 A
 SD 10 FRZ
 SD 10 C
 SD 15
 SBe 50
 SD 50
 SD 70
 SBe 250
 SD 250
 SD 500
 SD 1400 "Esau"
 SD 1700 "Sigismund"
 SD 500A
 SD 500E

Armour-piercing 
 SC 10
 SC 10 DW
"Panzersprengbombe-Cylindrisch" (Armor-piercing bombs)
 PC 500* 'Pauline'
PC 500 RS
 PC 1000* 'Pol'
PC 1000 RS
 PC 1400 'Fritz' (starting point for the Fritz X gravity precision-guided munition)
 PC 1600
PC 1800 RS 'Panther'
PD 500
PD 1000

Cluster bombs 
 AB 23
 AB 250-2
AB 250-3
 AB 500-1
 AB 500-1B
 AB 500-3A
 AB 70-D1
 BDC 10

Prototype only
 the Düsenkanone 88 rotary-magazine heavy calibre cannon, meant to largely be recoilless
 Henschel Hs 298, air-to-air missile (rocket-powered)
Mauser MG 213
MK 112
 MK 115
MK 214A cannon
 SG 116 (Link is to german wikipedia page)
 Ruhrstahl X-4
 Jagdfaust

See also
 List of weapons of World War II Japanese aircraft
 Schräge Musik

References

External links

War weapons
DFS 194. The DFS 194 was a rocket-powered aircraft designed by Alexander Lippisch at the Deutsche Forschungsanstalt für Segelflug (DFS - "German Institute for Sailplane Flight").

Design and development
The DFS 194 was based on the Alexander Lippisch Delta series of tailless designs. As originally conceived, it would have been a tailless aircraft similar to his DFS 40, powered by a conventional piston engine driving a pusher propeller. The airframe was completed in this configuration in March 1938.

Lippisch's designs had attracted the attention of the Reichsluftfahrtministerium (RLM - Reich Aviation Ministry) who believed that tailless aircraft were the best basis for a rocket-powered fighter. On January 2, 1939, Lippisch and his team were transferred to the Messerschmitt company to begin work on such an aircraft, under what was known as Project X. The DFS-194 was modified to accept a Walter R I-203 rocket engine designed by Hellmuth Walter, and by October, the aircraft was undergoing engine tests at Peenemünde.

These were followed by glide tests in early 1940 leading to the first powered flight in August with Heini Dittmar at the controls. The flight went well, the DFS 194 reaching , bettering the speed of the earlier (20 July 1939), Walter rocket powered Heinkel He 176.

The aircraft proved to have excellent flying characteristics and proved safe to fly at nearly twice the anticipated speed. These results paved the way for the next stage of the project, which now received priority status from the RLM. The Messerschmitt Me 163, a considerably refined design along the same basic lines, flew the following year.

Specifications

Source:

See also

References

1940s German experimental aircraft
Rocket-powered aircraft
Tailless aircraft
DFS 194
Aircraft first flown in 1940
Louis Lumière. Louis Jean Lumière (; 5 October 1864 – 6 June 1948) was a French engineer and industrialist who played a key role in the development of photography and cinema.

Early life and education
Lumière was one of four children of Claude-Antoine Lumière, a photographer and painter, and his wife Jeanne-Joséphine (née Costille). At the Martinière Technical School he gained highest marks in his class.

Career
At age 17, Lumière invented a new process for film development using a dry plate. This process was significantly successful for the family business, permitting the opening of a new factory with an eventual production of 15 million plates per year. Thomas Edison's Kinetoscope inspired his and his brother's subsequent work on the cinematograph.

Louis Lumière is most often associated with the name of his brother, Auguste Lumière, under the name of the Lumière brothers. This comparison is a little excessive with regard to the invention of the cinematograph, since in reality, Auguste failed in his attempt to manufacture the first machine, and passed it to his brother who made the invention succeed. On the other hand, Louis was the director of all the first animated photographic views of the Lumière Society, which Auguste sometimes attended only as an amateur actor (Le Repas de bébé, La Pêche aux poissons rouges, Démolition d'un mur, etc.). But the contract signed between the two brothers provided that they be systematically associated, both morally and financially, in all their work and discoveries.

References

External links 

 Louis Lumière at IMDb

Auguste and Louis Lumière
1864 births
1948 deaths
French silent film directors
Auguste Lumière. Auguste Marie Louis Nicolas Lumière (; 19 October 1862 – 10 April 1954) was a French engineer, industrialist, biologist, and illusionist. In 1894 and 1895, he and his brother Louis invented an animated photographic camera and projection device, the cinematograph, which met with worldwide success.

Life
Lumière was born in Besançon. He attended the Martinière Technical School and worked as a manager at the photographic company of his father, Claude-Antoine Lumière. He was invited to attend a demonstration of the Kinetoscope invented by Thomas Edison, which inspired his and his brother's work on the cinematograph. The brothers screened their first film using this device in December 1895, and following the success of this initial venture opened a number of cinemas worldwide. However, Auguste was skeptical of the potential of the device, remarking "My invention can be exploited... as a scientific curiosity, but apart from that it has no commercial value whatsoever".

After his work on the cinematograph Lumière began focusing on the biomedical field, becoming a pioneer in the use of X-rays to examine fractures. He also contributed to innovations in military aircraft, producing a catalytic heater to allow cold-weather engine starts. He died in Lyon, aged 91.

References

External links 

 

1862 births
1954 deaths
19th-century French inventors
Auguste and Louis Lumière
Pioneers of photography
French silent film directors
Value transfer system. A value transfer system refers to any system, mechanism, or network of people that receives money for the purpose of making the funds or an equivalent value payable to a third party in another geographic location, whether or not in the same form.

The average size of the payment is an indicator of the system's use.  Specialised large-value transfer system have developed because of the large size and critical timing of some payments market participants require services and mechanisms that meet their need for reliability, security, accuracy and timeliness.

A value transfer system may fall into one or more of these groups:
Retail value transfer systems:
Traditional retail value transfer systems, e.g. Bank transfer, Wire transfer, Post offices transfer service or specialist companies such as Western Union
Internet-only value transfer systems, e.g. Electronic money such as PayPal, eGold, Liberty Reserve
Cryptocurrencies: Bitcoin, Litecoin, Ethereum, etc.
Institutional formal value transfer systems, e.g. SWIFT (International), domestic real-time gross settlement (RTGS) systems such as LVTS (Canada), Fedwire (USA), CHAPS (UK)
Informal value transfer systems, e.g. hawala

See also

Digital currency
Electronic funds transfer
Correspondent account
Payment system

References

External links
1996 paper: The Effect of Internet Value Transfer 

Financial economics
Payment systems
Mikoyan-Gurevich I-270. The Mikoyan-Gurevich I-270 (Design Ж ("Zh") under Mikoyan-Gurevich's in-house designation sequence, USAF/DoD designation: Type 11) was a response to a Soviet Air Forces requirement in 1945 for a rocket-powered interceptor aircraft for the point-defence role. In concept and basic configuration, it was related to the early Korolyov RP-318 rocket-powered aircraft which was developed in 1936 and first flew February 20, 1940, and the more recent Bereznyak-Isayev BI-1 Soviet design. Only two prototypes were built, both of which were destroyed in crashes, leading to the cancellation of the project.

Flights

In the early stages of World War II (1942), a complete prototype BI-1 (also known as The Devil's Broomstick), made its first several flights. The I-270 shared the BI-1's simple, tapered fuselage, bubble canopy, wing design, and dual-chambered bipropellant rocket motor. On the other hand, it was considerably larger than the BI-1 and featured short, reinforced wings (from the RP-218) and a raised T-tail which aircraft such as the Tupolev ANT-8 proved, offered better landing control than the BI-1's more traditional fighter layout. While there seems little doubt that the BI-1 influenced the design of the I-270, the latter appears far from a direct descendant of the former, and much closer to being a Soviet version of the Me 263, sharing very similar fuselage, canopy and landing gear layouts, while adding a conventional stabilizer surface atop the vertical tail, absent on the German design.

The Soviet tradition of rocketry, starting from the early work of Konstantin Tsiolkovsky and carried through by men like Sergei Korolev, made rocket fighters a reality.  The RD-2M engine, designed by Leonid Dushkin was the dual-combustion chamber version of the engine used for the 1941 BI-1 rocket plane. That in turn had followed from a tradition dating back to Sergey Korolev's work on project "06" in the early 1930s and the RP-318 rocket plane designed in 1936.

The first gliding trials commenced in December 1946, with the first prototype towed into the air behind a Tupolev Tu-2, ballast-loaded in place of an engine. The second prototype began powered tests early in 1947, but was damaged beyond repair making a hard landing. Shortly afterwards, the first prototype was also destroyed in a landing accident. By this stage, turbojet technology was at a far more advanced stage than it had been at the outset of the project, and surface-to-air missiles had replaced the need for point-defence interceptors. Under these circumstances, the Air Force decided to cancel the project.

Operators

Soviet Air Forces

Specifications (I-270)

See also

References

I-270
1940s Soviet fighter aircraft
Rocket-powered aircraft
Abandoned military aircraft projects of the Soviet Union
Aircraft first flown in 1946
T-tail aircraft
Aircraft with retractable tricycle landing gear
Edinburgh Multiple Access System. The Edinburgh Multi-Access System (EMAS) was a mainframe computer operating system at the University of Edinburgh. The system went online in 1971.

EMAS was a powerful and efficient general purpose multi-user system which coped with many of the computing needs of the University of Edinburgh and the University of Kent (the only other site outside Edinburgh to adopt the operating system).

History
Originally running on the ICL System 4/75 mainframe (based on the design of the IBM 360) it was later reimplemented  on the ICL 2900 series of mainframes (as EMAS 2900 or EMAS-2) where it ran in service until the mid-1980s. Near the end of its life, the refactored version was back-ported (as EMAS-3) to the Amdahl 470 mainframe clone, and thence to the IBM System/370-XA architecture (the latter with help from the University of Kent, although they never actually ran EMAS-3). The National Advanced System (NAS) VL80 IBM mainframe clone followed later.  The final EMAS system (the Edinburgh VL80) was decommissioned in July 1992.

The University of Kent system went live in December 1979, and ran on the least powerful machine in the ICL 2900 range - an ICL 2960, with 2 MB of memory, executing about 290k instructions per second. Despite this, it reliably supported around 30 users. This number increased in 1983 with the addition of an additional 2 MB of memory and a second Order Code Processor (OCP) (what is normally known as a CPU) running with symmetric multiprocessing. This system was decommissioned in August 1986.

Features
EMAS was written entirely in the Edinburgh IMP programming language, with only a small number of critical functions using embedded assembler within IMP sources. It had several features that were advanced for the time, including dynamic linking, multi-level storage, an efficient scheduler, a separate user-space kernel ('director'), a user-level shell ('basic command interpreter'), a comprehensive archiving system and a memory-mapped file architecture.

Such features led EMAS supporters to claim that their system was superior to Unix for the first 20 years of the latter's existence.

Legacy
The Edinburgh Computer History Project is attempting to salvage some of the lessons learned from the EMAS project and has the complete source code of EMAS online for public browsing.

See also
Atlas Autocode

References

History of computing in the United Kingdom
Time-sharing operating systems
1970s software
University of Edinburgh School of Informatics
Yokosuka MXY8. The Yokosuka MXY8 Akigusa (秋草, "Autumn grass") was a training glider built in parallel with the Mitsubishi J8M rocket-powered interceptor aircraft.

Design and development
The J8M was to have simply been a licence-built Messerschmitt Me 163 Komet, but, due to difficulties in obtaining technical materials from Germany, it eventually had to be designed almost from scratch. The MXY8 was designed in parallel with the J8M to validate the design and then to provide pilot training during the development of the actual interceptor. The Army designation for the type was Ku-13.

The MXY8 was built entirely of wood and fitted with ballast tanks that would be filled with water to simulate the weight and, therefore, flight characteristics of a fully equipped J8M. Some 50-60 of these gliders were eventually built.

A more advanced trainer, the MXY9, equipped with a primitive jet engine was planned but was never produced.

Many sources apply the designation MXY8 to the Yokosuka MXY7 Ohka kamikaze weapon.

Specifications

See also

References

Bibliography

External links

1940s Japanese military trainer aircraft
1940s military gliders
MXY8
Mid-wing aircraft
Tailless aircraft
Aircraft with skid landing gear
Glider aircraft