Return to design-outline.tex CVS log

Up to [local] / OpenXM / doc / issac2000

Annotation of OpenXM/doc/issac2000/design-outline.tex, Revision 1.7

1.7     ! takayama    1: % $OpenXM: OpenXM/doc/issac2000/design-outline.tex,v 1.6 2000/01/15 02:24:18 takayama Exp $
1.2       takayama    2:
                      3: \section{Design Outline}
                      4:
                      5: As Schefstr\"om clarified in \cite{schefstrom},
                      6: integration of tools and softwares has three dimensions:
                      7: data, control, and user interface.
                      8:
                      9: Data integration concerns with the exchange of data between different
                     10: softwares or same softwares.
                     11: OpenMath \cite{OpenMath} and MP (Multi Protocol) \cite{GKW} are,
                     12: for example, general purpose mathematical data protocols.
1.6       takayama   13: They provide standard ways to express mathematical objects.
1.2       takayama   14: For example,
                     15: \begin{verbatim}
                     16:  <OMOBJ>  <OMI> 123 </OMI> </OMOBJ>
                     17: \end{verbatim}
1.3       takayama   18: means the (OpenMath) integer $123$ in OpenMath/XML expression.
1.2       takayama   19:
                     20: Control integration concerns with the establishment and management of
1.3       takayama   21: inter-software communications.
1.6       takayama   22: Control involves, for example, a way to ask computations to other processes
1.3       takayama   23: and a method to interrupt computations on servers from a client.
1.2       takayama   24: RPC, HTTP, MPI, PVM are regarded as a general purpose control protocols or
1.3       takayama   25: infrastructures.
1.2       takayama   26: MCP (Mathematical Communication Protocol)
                     27: by Wang \cite{iamc} is such a protocol specialized to mathematics.
                     28:
                     29: Although, data and control are orthogonal to each other,
                     30: real world requires both.
1.4       ohara      31: NetSolve \cite{netsolve}, OpenMath$+$MCP, MP$+$MCP \cite{iamc},
1.6       takayama   32: and MathLink \cite{mathlink} provide both data and control integration.
1.7     ! takayama   33: Each integration method has their own features due to their
1.2       takayama   34: own design goals and design motivations.
1.6       takayama   35: OpenXM (Open message eXchange protocol for Mathematics)
                     36: is a project aiming to integrate data, control and user interfaces
1.7     ! takayama   37: with its own set of design goals.
1.2       takayama   38: To explain our design outline, we start with a list of
                     39: our motivations.
                     40: \begin{enumerate}
1.6       takayama   41: \item Noro has developed a general
1.2       takayama   42: purpose computer algebra system Risa/Asir \cite{asir}.
1.7     ! takayama   43: An interface for interactive distributed computations was introduced
1.3       takayama   44: in Risa/Asir version 950831 released in 1995.
1.2       takayama   45: The model of computation was RPC (remote procedure call)
1.7     ! takayama   46: and it had its own serialization.
1.2       takayama   47: A robust interruption method was provided by having two communication channels
1.6       takayama   48: like ftp.
1.7     ! takayama   49: As an application of this robust and the interactive distributed computation
1.5       noro       50: system, speed-up was achieved for a huge Gr\"obner basis computation
                     51: to determine all odd order replicable functions
                     52: by Noro and McKay \cite{noro-mckay}.
                     53: However, the protocol was closed in Asir and we thought that we should
1.2       takayama   54: design an open protocol.
1.6       takayama   55: \item Takayama has developed
1.2       takayama   56: a special purpose computer algebra system Kan/sm1 \cite{kan},
1.7     ! takayama   57: which is a Gr\"obner engine for the ring of differential operators $D$.
1.2       takayama   58: In order to implement algorithms in D-modules due to Oaku
                     59: (see, e.g., \cite{sst-book}),
                     60: factorizations and primary ideal decompositions were necessary.
1.3       takayama   61: Kan/sm1 does not have an implementation for these and called
1.5       noro       62: Risa/Asir as a C library or a UNIX external program.
1.2       takayama   63: This approach was not satisfactory.
                     64: Especially, we could not write a clean interface code between these
                     65: two systems.
                     66: We thought that it is necessary to provide a data and control protocol
1.5       noro       67: for Risa/Asir to work as a server of factorization and primary ideal
1.2       takayama   68: decomposition.
                     69: \item The number of mathematical softwares is increasing rapidly in the last
1.3       takayama   70: decade of the 20th century.
1.7     ! takayama   71: These are usually ``expert'' systems in one area of mathematics
1.2       takayama   72: such as ideals, groups, numbers, polytopes, and so on.
1.3       takayama   73: They have their own interfaces and data formats.
1.7     ! takayama   74: Interfaces are sometimes specialized to a specific field of mathematics
        !            75: or poor.
1.2       takayama   76: It is fine for intensive and serious users of these systems.
                     77: However, for users who want to explore a new area of mathematics with these
1.3       takayama   78: softwares or users who need these systems only occasionally,
1.4       ohara      79: a unified system will be more convenient.
1.7     ! takayama   80:
1.5       noro       81: \item  We believe that an open integrated system is a future of mathematical
1.2       takayama   82: softwares.
1.3       takayama   83: However, it might be just a dream without realizability.
1.5       noro       84: We want to build a prototype system of such an open system by using
1.2       takayama   85: existing standards, technologies and several mathematical softwares.
                     86: We want to see how far we can go with this approach.
                     87: \end{enumerate}
                     88:
                     89: Motivated with these, we started the OpenXM project with the following
                     90: fundamental architecture.
                     91: \begin{enumerate}
1.4       ohara      92: \item Communication is an exchange of messages. The messages are classified into
1.2       takayama   93: three types:
                     94: DATA, COMMAND, and others.
                     95: The messages are called OX (OpenXM) messages.
1.3       takayama   96: Mathematical data are wrapped with {\it OX messages}.
                     97: We use standards of mathematical data formats such as OpenMath and MP
                     98: and our own data format ({\it CMO --- Common Mathematical Object format})
1.2       takayama   99: as data expressions.
1.4       ohara     100: \item Servers, which provide services to other processes, are stack machines.
                    101: The stack machine is called the
                    102: {\it OX stack machine}.
                    103: Existing mathematical softwares are wrapped with this stack machine.
                    104: Minimal requirements for a target software wrapped with the OX stack machine
1.2       takayama  105: are as follows:
                    106: \begin{enumerate}
1.4       ohara     107: \item The target must have a serialized interface such as a character based
1.2       takayama  108: interface.
1.3       takayama  109: \item An output of the target must be understandable for computer programs;
1.4       ohara     110: it should follow a grammar that can be parsed with other softwares.
1.2       takayama  111: \end{enumerate}
1.7     ! takayama  112: \item Any server may have a hybrid interface;
        !           113: it may accept and execute its original command sequences.
        !           114: For example,
        !           115: if we send the following string to ox\_asir server
        !           116: {\footnotesize
        !           117: \begin{verbatim}
        !           118:       " fctr(x^10-y^10); "
        !           119: \end{verbatim}
        !           120: }
        !           121: and call the stanck machine command
        !           122: SM\_executeStringByLocalParser,
        !           123: then the server executes the asir command
        !           124: \verb+ fctr(x^10-y^10); +
        !           125: (factorize $x^10-y^10$ over ${\bf Q}$)
        !           126: and push the result on the stack.
1.2       takayama  127: \end{enumerate}
1.7     ! takayama  128: We are implementing a package, OpenXM package.
1.2       takayama  129: It is based on above fundamental architecture.
                    130: For example, the following is a command sequence to ask $1+1$ from
1.5       noro      131: the Asir client to the OX sm1 server:
1.2       takayama  132: \begin{verbatim}
                    133:   P = sm1_start();
                    134:   ox_push_cmo(P,1); ox_push_cmo(P,1);
                    135:   ox_execute_string(P,"add"); ox_pop_cmo(P);
                    136: \end{verbatim}
                    137: The current system, OpenXM on TCP/IP,
1.3       takayama  138: uses client-server model and the TCP/IP is used for interprocess
1.2       takayama  139: communications.
1.6       takayama  140: The OpenXM on MPI \cite{MPI} is currently running on Risa/Asir
1.7     ! takayama  141: as we will see in Section \ref{section:homog}.
1.3       takayama  142: However, we focus only on the system based on TCP/IP in this paper.
1.6       takayama  143:
1.2       takayama  144:
                    145:
1.1       takayama  146: