omniomni/omni-engineering huggingface dataset:
National Aerospace Laboratory of Japan. The National Aerospace Laboratory of Japan (NAL), was established in July 1955.  Originally known as the National Aeronautical Laboratory, it assumed its present name with the addition of the Aerospace Division in 1963. Since its establishment, it has pursued research on aircraft, rockets, and other aeronautical transportation systems, as well as peripheral technology. NAL was involved in the development of the autonomous ALFLEX aircraft and the cancelled HOPE-X spaceplane.

NAL has also endeavored to develop and enhance large-scale test facilities and make them available for use by related organizations, with the aim of improving test technology in these facilities.

The NAL began using computers to process data since the 1960s. It began working to develop supercomputer and numerical simulation technologies in order to execute full-scale numeric simulations. The NAL, in collaboration with Fujitsu, developed the Numerical Wind Tunnel parallel supercomputer system, which went into operation in 1993. From 1993 to 1995, it was the most power supercomputer in the world, and was one of the top 3 in the world until 1997. It remained in use for 9 years after it began operations.

On October 1, 2003, NAL, which had focused on research and development of next-generation aviation, merged with the Institute of Space and Astronautical Science (ISAS), and the National Space Development Agency (NASDA) of Japan into one Independent Administrative Institution: the Japan Aerospace Exploration Agency (JAXA).

References

1955 establishments in Japan
JAXA
Aeronautics organizations
Aviation research institutes
Aerospace research institutes
ArcSDE. ArcSDE (SDE for Spatial Database Engine) is a server-software sub-system (produced and marketed by Esri) that aims to enable the usage of Relational Database Management Systems for spatial data. The spatial data may then be used as part of a geodatabase.

History 
Geographic Technologies Incorporated (GTI) in Australia originally designed the database software, named Spatial DataBase Engine (SDBE). Development shifted to Salamanca Software Pvt Ltd., which developed the first production version. SDBE originally used the InterBase DBMS. The president of Esri, Jack Dangermond, announced SDE at the GIS'95 conference in Vancouver, British Columbia, and Esri purchased Salamanca Software in 1996. Esri rebranded the software as "ArcSDE" to follow the naming convention of other products.

ArcSDE grew to meet the need of users of geographic data for robust multi-user editing, storage and access of extremely large geospatial databases. ArcSDE supports the Esri geodatabase implementation.

The product began as stand-alone software: Esri integrated it into ArcGIS version 9.2.

In 2013 ESRI announced plans to deprecate the ArcSDE command line tools and the ArcSDE application server following the forthcoming release of ArcGIS 10.2.

ArcSDE 10.1 and 10.2 

 with the release of 10.1, Esri sells ArcSDE as a component of ArcGIS Server - part of the ArcGIS family of software products which integrates geographic-information query, mapping, spatial analysis, and editing within a multi-user enterprise DBMS environment.

Functionality 
ArcSDE enables organizations to move from a traditional approach — managing separate collections of geographic data files — to an integrated environment in which one can manage spatial data as a continuous database: accessible to the entire organization simultaneously and easily publishable on the Web. It stores spatial data using the Geodatabase data model and structure.

ArcSDE as an application server facilitates storing and managing spatial data (raster, vector, and survey)
in a DBMS and makes the data available to many applications. ArcSDE allows one to manage spatial data in any of four commercial databases (IBM Db2, Informix, Microsoft SQL Server and Oracle). Starting with the 9.3 release, Esri added support for the open-source PostgreSQL database.

ArcSDE serves data for the advanced ArcGIS Desktop products (ArcView, ArcEditor and ArcInfo); the ArcGIS development products (ArcGIS Engine and ArcGIS Server), ArcView 3.x as well as ArcIMS. It is a key component in managing a multi-user Esri-based GIS.

While traditional RDBMS software keeps track of the tables and records contained in the database, ArcSDE pushes the relational model higher so that client software can manage geographic data - which comprise several tables - seamlessly. The user need have no awareness of nor dealings with the particulars of the RDBMS. The GIS environment routes all connections to the database through the ArcSDE middleware, which manages the storing and retrieval of data.

References

External links

 Esri webpage

Esri software
Relational database management systems
Capacitance multiplier. A capacitance multiplier is designed to make a capacitor function like a much larger capacitor. This can be achieved in at least two ways.
 An active circuit, using a device such as a transistor or operational amplifier
 A passive circuit, using autotransformers. These are typically used for calibration standards. The General Radio / IET labs 1417 is one such example.

Capacitor multipliers make low-frequency filters and long-duration timing circuits possible that would be impractical with actual capacitors.  Another application is in DC power supplies where very low ripple voltage (under load) is of paramount importance, such as in class-A amplifiers.

Transistor-based 

Here the capacitance of capacitor C1 is multiplied by approximately the transistor's current gain (β).

Without Q, R2 would be the load on the capacitor. With Q in place, the loading imposed upon C1 is simply the load current reduced by a factor of (β + 1). Consequently, C1 appears multiplied by a factor of (β + 1) when viewed by the load.

Another way is to look at this circuit as an emitter follower with capacitor C1 holding voltage at base constant with load of input impedance of Q1: R2 multiplied by (1 + β), so the output current is stabilized much more against power line voltage noise.

Operational amplifier based 

Here, the capacitance of capacitor C1 is multiplied by the ratio of resistances: C = C1 * R1 / R2 at the Vi node.

The synthesized capacitance also brings a series resistance approximately equal to R2, and a leakage current appears across the capacitance because of the input offsets of OP. These problems can be avoided by a circuit with two op amps. In this circuit the input to OP1 can be a.c.-coupled if necessary, and the capacitance can be made variable by making the ratio of R1  to R2 variable. C = C1 * (1 + (R2 / R1)).

In the circuits described above the capacitance is grounded, but floating capacitance multipliers are possible.

A negative capacitance multiplier can be created with a negative impedance converter.

Autotransformer based 
These permit the synthesis of accurate values of large capacitance (e.g., 1 F) by multiplying the capacitance of a high-precision lower value capacitor by the use of two transformers. Its function acts as a reference standard, not as a general-purpose circuit element. The resulting device is a four-terminal element and cannot be used at dc.

References

 IET Labs 1417 FOUR-TERMINAL CAPACITANCE STANDARD

Electricity
Electronic circuits
HFT. HFT may refer to:

Businesses and organisations 
 Harbor Freight Tools, an American retailer
 Hft, a British disability charity

Science and technology 
 High-flow therapy, a method of delivering respiratory gases
 Hardware Fault Tolerance in IEC 61508
 Himalayan Frontal Thrust, a geologic fault

Transport 
 Hammerfest Airport, Norway (by IATA code)
 Hoh Fuk Tong stop, Hong Kong (by MTR station code)
 Human Friendly Transmission, a motorcycle transmission

Other uses 
 High-frequency trading, type of algorithmic trading
 Hunter Field Target, a target shooting sport
Enstrophy. In fluid dynamics, the enstrophy  can be interpreted as another type of potential density; or, more concretely, the quantity directly related to the kinetic energy in the flow model that corresponds to dissipation effects in the fluid. It is particularly useful in the study of turbulent flows, and is often identified in the study of thrusters as well as in combustion theory and meteorology.

Given a domain  and a once-weakly differentiable vector field  which represents a fluid flow, such as a solution to the Navier-Stokes equations, its enstrophy is given by:where . This quantity is the same as the squared seminorm of the solution in the Sobolev space .

Incompressible flow 
In the case that the flow is incompressible, or equivalently that , the enstrophy can be described as the integral of the square of the vorticity :

or, in terms of the flow velocity:

In the context of the incompressible Navier-Stokes equations, enstrophy appears in the following useful result:

The quantity in parentheses on the left is the kinetic energy in the flow, so the result says that energy declines proportional to the kinematic viscosity  times the enstrophy.

See also 

 Atmospheric circulation
 Turbulence

References

Further reading 
 
 
 

Continuum mechanics
Fluid dynamics
Turbulence
Graphplan. Graphplan is an algorithm for automated planning developed by Avrim Blum and Merrick Furst in 1995. Graphplan takes as input a planning problem expressed in STRIPS and produces, if one is possible, a sequence of operations for reaching a goal state. 

The name graphplan is due to the use of a novel planning graph, to reduce the amount of search needed to find the solution from straightforward exploration of the state space graph.

In the state space graph:
 the nodes are possible states,
 and the edges indicate reachability through a certain action.

On the contrary, in Graphplan's planning graph:
 the nodes are actions and atomic facts, arranged into alternate levels, 
 and the edges are of two kinds: 
 from an atomic fact to the actions for which it is a condition, 
 from an action to the atomic facts it makes true or false.
The first level contains true atomic facts identifying the initial state. 

Lists of incompatible facts that cannot be true at the same time and incompatible actions that cannot be executed together are also maintained.

The algorithm then iteratively extends the planning graph, proving that there are no solutions of length l-1 before looking for plans of length l by backward chaining: supposing the goals are true, Graphplan looks for the actions and previous states from which the goals can be reached, pruning as many of them as possible thanks to incompatibility information.

A closely related approach to planning is the Planning as Satisfiability (Satplan). Both reduce the automated planning problem to search for plans of different fixed horizon lengths.

References

A. Blum and M. Furst (1997). Fast planning through planning graph analysis. Artificial intelligence. 90:281-300.

External links

Avrim Blum's Graphplan home page
PLPLAN: A Java GraphPlan Implementation
NPlanner: A .NET GraphPlan Implementation 
Emplan and JavaGP: C++ and Java implementations of Graphplan
MIT OpenCourseWare lecture on GraphPlan and making planning graphs

Automated planning and scheduling
Search algorithms
Plating efficiency. Plating efficiency ("PE") is a measure of the number of colonies originating from single cells. It is a very sensitive test and is often used for determining the nutritional requirements of cells, testing serum lots, measuring the effects of growth factors, and for toxicity testing.

Plating Efficiency is the number of cells that grow into colonies per 100 cells inoculated. That is, it is the proportion of cells that attach and grow to the number of cells originally plated, expressed as a percentage. PE can be determined by the following formulae:

or

The first method is more accurate.

Cell growth in culture generally undergoes a decline after plating, and graphically, PE is the global minimum (lowest point) of the growth curve at day one, after which growth rises again. The decrease in viable cells after plating is due to "anchorage-dependence"--cells must attach to the bottom of the culture dish.

Plating Efficiency is one of the parameters typically used to define  growth properties of cells in culture. Other common parameters are doubling time ("DT") (which is an average of generation time ("GT")), and saturation density ("SD").

References
Mather, J.P., and P.E. Roberts, 1998. Introduction to Cell and Tissue Culture: Theory and Technique. Plenum Press. New York City and London.

Plant reproduction
Pafawag. Pafawag (Państwowa Fabryka Wagonów) (English: National Rail Carriage Factory) is a Polish locomotive manufacturer based in Wrocław. The company became part of Adtranz in 1997 as Adtranz Pafawag, and in 2001 part of Bombardier Transportation.  .

History
The factory opened in 1833 as Linke-Hofmann-Werke, Breslau, and became one of the major production centres for rolling stock in Europe.

By the end of the Second World War most of the factory had been destroyed, and after the War the city of Breslau became part of Poland.

In 1953 the company was renamed Pafawag.

In 1953 the company produced the EP-02, the first Polish electric locomotive manufactured after World War II.

In the late 1980s to mid 1990s the company experienced increasing economic problems due to lack of orders causing loss of production and lower employment.

In 1997 ABB DaimlerBenz Transportation (ADtranz) acquired a majority share in the company. The Adtranz group (DaimlerChrysler Rail Systems after 1999) was bought by Bombardier Transportation in 2001;  the Wroclaw plant was merged with another Bombardier owned plant based in Łódź to form Bombardier Transportation Polska Sp. z o.o. The plant manufactures the bodyshells of Bombardier locomotives as well as other sub-components for the Bombardier Transportation group.

In 2015 Bombardier contracted Panattoni Europe to construct an additional  manufacturing hall, initially to be used for the construction of Deutsche Bahn's ICx trains.

Products

The main products:
 locomotives,
 bodies,
 frames,
 running gear for locomotives.

Pafawag was the producer of first Polish modern "fast locomotive" EP09 .

Pafawag types

Adtranz-Pafawag types

See also
Linke-Hofmann

References

External links 

  History of Linke-Hofmann-Werke (in German)

 
Locomotive manufacturers of Poland
Rail vehicle manufacturers of Poland
Companies based in Wrocław
Manufacturing companies established in 1833
1833 establishments in Poland
Handle-o-Meter. The Handle-o-Meter is a testing machine developed by Johnson & Johnson and now manufactured by Thwing-Albert that measures the "handle" of sheeted materials: a combination of its surface friction and flexibility. Originally, it was used to test the durability and flexibility of toilet paper and paper towels. It is also used to measure the stiffness of packaging film.

The test sample is placed over an adjustable slot. The resistance encountered by the penetrator blade as it is moved into the slot by a pivoting arm is measured by the machine.

Details
The data collected when such nonwovens, tissues, toweling, film and textiles are tested has been shown to correlate well with the actual performance of these specific material's performance as a finished product.

Materials are placed over a slot that extends across the instrument platform, and then the tester hits test. A beam then protrudes through the slot and a strain gauge measures the force that the material exerts on the beam. Stiff materials offer greater resistance to the movement of the beam. Machine direction and transverse stiffness are measured separately.

There are three different test modes which can be applied to the material: single, double, and quadruple. The average is automatically calculated for double or quadruple tests.

Restrictions on measuring the friction between the platform and the material limit the instrument's accuracy.

Features
Adjustable slot openings
Interchangeable beams
Auto-ranging
2 x 40 LCD display
Statistical Analysis
RS-232 Output and Serial Port
Industry Standards:
ASTM D2923, D6828-02
TAPPI T498
INDA IST 90.3

References

External links
Manufacturer's datasheet

Textiles
Machines
Quality control
Toilet paper
Microsoft RPC. Microsoft RPC (Microsoft Remote Procedure Call) is a modified version of DCE/RPC. Additions include partial support for UCS-2 (but not Unicode) strings, implicit handles, and complex calculations in the variable-length string and structure paradigms already present in DCE/RPC.

Example 
The DCE 1.0 reference implementation only allows such constructs as , or possibly . MSRPC allows much more complex constructs such as  and even , a common expression in DCOM IDL files.

Use 
MSRPC was used by Microsoft to seamlessly create a client/server model in Windows NT, with very little effort. For example, the Windows Server domains protocols are entirely MSRPC based, as is Microsoft's DNS administrative tool. Microsoft Exchange Server 5.5's administrative front-ends are all MSRPC client/server applications, and its MAPI was made more secure by "proxying" MAPI over a set of simple MSRPC functions that enable encryption at the MSRPC layer without involving the MAPI protocol.

History 
MSRPC is derived from the Distributed Computing Environment 1.2 reference implementation from the Open Software Foundation, but has been copyrighted by Microsoft. DCE/RPC was originally commissioned by the Open Software Foundation, an industry consortium to set vendor- and technology-neutral open standards for computing infrastructure. None of the Unix vendors (now represented by the Open Group), wanted to use the complex DCE or such components as DCE/RPC at the time. 

Microsoft's Component Object Model is based heavily on MSRPC, adding interfaces and inheritance. The marshalling semantics of DCE/RPC are used to serialize method calls and results between processes with separate address spaces, albeit COM did not initially allow network calls between different machines.

With Distributed Component Object Model (DCOM), COM was extended to software components distributed across several networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure.

References

External links
MSRPC at MSDN
, a chapter on MSRPC from a technical article by Jean-Baptiste Marchand.

Network protocols
Remote procedure call
Microsoft application programming interfaces
DCEThreads. DCEThreads is an implementation of POSIX Draft 4 threads. DCE Stands for "Distributed Computing Environment"  DCEThreads allowed users to create multiple avenues of execution in a single process. It is based on pthreads interface.

History
DCE/RPC was under development, but the POSIX committee had not finalised POSIX threads at the time. The Open Group had to make a decision about which to use, and the final POSIX threads were different from their selection.

POSIX Draft 4 threads were limited to begin with (the final standard fixed these). Microsoft adopted DCE/RPC wholesale in Windows NT as MSRPC and also in DCOM. Most of the stability and reliability problems that programmers associate with DCOM services - especially memory leaks, exception handling problems and thread cancellation stability issues - can be traced back to the use of POSIX Draft 4 threads.

DCE/RPC is sufficiently complex that the issue of updating it to solve and modernise the POSIX Draft 4 threading problem requires highly skilled and highly specific programming knowledge. Consequently, despite its capacities, the reference implementation of DCE/RPC has been held up due to a lack of information and resources.

The key difference between POSIX Draft 4 threads and the final POSIX threads specification, aside from a number of functions being interruptible where others are not, is thread cancellation. DCE/RPC utilises thread cancellation to propagate signals across the "Remote" of RPC, such that for example a client application terminating a thread results in its corresponding thread on the server also being terminated in the same way. The final POSIX specification does not include such sophisticated cancellation methodology, and, given the difficulties that the Unix vendors had in correctly implementing the POSIX threads specification, it was removed.

Recent developments
Linux, since the introduction of NPTL and the Linux 2.6 kernel, has proper support for thread cancellation.

Current use
DCEThreads now only realistically exists as an emulation layer.

References

POSIX
Tin(II) hydroxide. Tin(II) hydroxide, Sn(OH)2, also known as stannous hydroxide, is an inorganic compound tin(II). The only related material for which definitive information is available is the oxy hydroxide Sn6O4(OH)4, but other related materials are claimed.  They are all white solids that are insoluble in water.

Preparation and structure
Crystals of Sn6O4(OH)4 has been characterized by X-ray diffraction.  This cluster is obtained from solution of basic solutions of tin(II).  The compound consists of an octahedron of Sn centers, each face of which is capped by an oxide or a hydroxide.  The structure is reminiscent of the Mo6S8 subunit of the Chevrel phases.. The structure of pure Sn(OH)2 is not known.

Sn(OH)2 has been claimed to arise from the reaction of (CH3)3SnOH with SnCl2 in an aprotic solvent:
2 Me3SnOH + SnCl2 → Sn(OH)2 + 2 Me3SnCl
No crystallographic characterization is available on this material.

Reactions
Stannous hydroxide is easily oxidized to stannic oxide (SnO2) by air.

References

Hydroxides
Tin(II) compounds
Reducing agents
Lead(II) hydroxide. Lead(II) hydroxide, (), is a hydroxide of lead, with lead in oxidation state +2.

Preparation
When a hydroxide is added to a solution of a lead(II) salt, a hydrated lead oxide  (with x < 1) is obtained. Careful hydrolysis of lead(II) acetate solution yields a crystalline product with a formula  or . This material is a cluster compound, consisting of an octahedron of Pb centers, each face of which is capped by an oxide or a hydroxide. The structure is reminiscent of the  subunit of the Chevrel phases.
The following formula can also prepare it:
Pb(NO₃)₂ + NaOH = NaNO₃ + Pb(OH)₂

Reactions
In aqueous solution, lead(II) hydroxide is a somewhat weak base, forming lead(II) ion, , under weakly acidic conditions. This cation hydrolyzes and, under progressively increasing alkaline conditions, it becomes somewhat weak acid, and it forms , (aqueous), , and other species, including several polynuclear species, e.g., , , .
Upon heating to decomposition temperatures, it forms lead oxide (PbO) in the yellow form, litharge.

History
The name lead hydrate has sometimes been used in the past but it is unclear whether this refers to  or . In 1964 it was believed that such a simple compound did not exist, as lead basic carbonate () or lead(II) oxide (PbO) was encountered where lead hydroxide was expected. This has been a subject of considerable confusion in the past. However, subsequent research has demonstrated that lead(II) hydroxide does indeed exist as one of a series of lead hydroxides.

References

External links
 Case Studies in Environmental Medicine - Lead Toxicity
 ToxFAQs: Lead
 National Pollutant Inventory - Lead and Lead Compounds Fact Sheet

Hydroxides
Lead(II) compounds