Machine translation software

The Spanish language edition of USP 23-NF 18 was published in 1995 as a DOS-based electronic product. In 1998, the product was converted to a Windows-based electronic product. Work on the translation of USP-NF text began in 1993 with the exploration of machine translation software suitable for use in the translation of the characteristic text of the USP-NF. The software selected was ENG-SPAN-AM from the Pan American Health Organization. This was fortified by a microdictionary and software macros specific to the compendia. Since the initial release in 1995, the USP has released Supplements for the Spanish language edition concurrent with the release of the English language Supplements. The database continues to be kept abreast of revisions to the USP and NF, but it was not marketed after 1998. 

For modifications on site, the software supplier should have access to a test configuration which is identical to the real system in all relevant aspects (including installed machine, translator, testing tools, plant simulator, etc.) to ensure the validity of the modifications. 

Although much easier to assemble, a software program written in a high-level language requires more time for the computer to execute, since all the instructions must be translated into machine code before the computer can understand them. Even a simple statement like start in a high-level language requires several machine-code moves to execute. 

The acquisition software sets up the right hardware parameters to begin an acquisition and controls the data flow during the acquisition. It can be controlled in two different ways, the routine way and the research based way with full access to all hardware based parameters. The routine way of starting an experiment requires the existence of a high level method, which is mainly a software module that translates high level, easily understandable parameters into low level, machine readable parameters. 

Accidents related to software or system logic design often result from incompleteness and unhandled cases in the functional design of the controller. This incompleteness can be considered a requirements or functional design problem. Some requirements completeness criteria were identified in Safeware and specified using a state machine model. Here those criteria plus additional design criteria are translated into functional design principles for the components of the control loop. 

The ultimate result of Computer Integrated Injection Molding (CUM) in software packages is to translate the results of computer simulation of the molding of a specific part into machine settings for specific microprocessor-controlled machines (Fig. 2-16). CUM automates the entry of a large number of set points (Figs. 2-2 and 2-13) in microprocessor-controlled machines and maximizes their efficiency, on the basis of extensive development by Ernest C. Bernhardt (Plastics Computer Inc., Montclair, NJ 07042, USA), a world leader on this subject (110, 111). 

Nehme and Lundqvist [6] describe a framework combining software tools for application verification and hardware platforms for execution and real-time monitoring. The tool translates safety critical VHDL code into a formal representation in a form of finite state machine (FSM) model. Formal techniques can then be applied on FSM representation to verify properties such as liveness and deadlock and to validate that the timing constraints of the original system are met. Three aspects of the tool implementation are discussed transformation of source code into an intermediate representation, verification of real-time properties, and some tool-related implementation issues. 

Since we have the GENSAL language (see Figure 2) for description of Markush structures , and software for translation of them into machine internal representations, we are able to derive search representations automatically. Great... 

---