Skip to content

GitLab

Commit 4195ee41 authored by Jean Meurice's avatar Jean Meurice Committed by Evgeny Kusmenko
Browse files

Software simulator

parent 97374b5a
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 15 additions and 5207 deletions
.gitlab-ci.yml
View file @ 4195ee41
......@@ -28,8 +28,6 @@ masterJobLinux:
- mvn package sonar:sonar -s settings.xml
only:
- master
tags:
- se
artifacts:
paths:
- install/rmi-model-server.jar
......@@ -61,8 +59,6 @@ BranchJobLinux:
- mvn -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn -B clean install --settings settings.xml
except:
- master
tags:
- se
masterJobDocker:
image: docker:dind
......
README.md
View file @ 4195ee41
......@@ -3,7 +3,7 @@
# RMIModelServer
The RMIModelServer is used to remotely allocate a series of [_HardwareEmulators_](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/hardware_emulator), which can load different autopilots generated with [_EMAM2CPP_](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Cpp).
The RMIModelServer is used to remotely allocate a series of [_SoftwareSimulators_](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/hardware_emulator), which can load different softwares generated with [_EMAM2CPP_](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Cpp).
## Requirements
......@@ -25,20 +25,17 @@ __NOTE:__ _MontiSim_ is the directory, in which MontiSim-belonging projects shou
To just compile the `jar`, use
mvn clean install -s settings.xml
To compile and copy the server to the local `install` folder, use the `scripts/compile_install` scripts.
__NOTE:__ New versions of the _HardwareEmulator_ must be copied into the `install` folder. This folder is used in a maven test to verify RMIModelServer/HardwareEmulator integration.
This will export the resulting jar in the `install` folder
## Running the RMI server
The `install` folder contains a sample setup for running the RMIModelServer.
The RMIModelServer jar must be in the same directory as the [HardwareEmulator](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/hardware_emulator) library it will use (_HardwareEmulator.lib_ or _HardwareEmulator.so_ for Windows or Linux).
The `run` script starts an instance of the RMIModelServer. It uses the `config` script to provide a way of changing the port or the autopilot folder used. The port defaults to 10101, and can be changed to start multiple RMIModelServers.
The `install` folder contains an exemplary setup to start the server.
The `run` script starts an instance of the RMIModelServer. It uses the `config` script to provide a way of changing the port or the softwares folder used. The port defaults to 10101, and can be changed to start multiple RMIModelServers.
The autopilot folder is a folder path (absolute or relative to the RMIModelServer) in which the RMI server will look for autopilot programs.
The softwares folder is a folder path (absolute or relative to the RMIModelServer) in which the RMI server will look for programs to run inside a SoftwareSimulator.
These programs are the EmbeddedMontiArc models compiled with EMAM2CPP (or a project using EMAM2CPP such as [EMAM-showcase](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/EMAM-showcase) or [EMAStudio](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/utilities/EMAStudioBuilder)).
The `autopilots` folder in the `install` folder contains the sample autopilot from `EMAM-Showcase`.
The `softwares` folder in the `install` folder contains the sample autopilot from `EMAM-Showcase`.
## Docker
......@@ -63,49 +60,3 @@ Or, for example with port 5000:
```
$ docker run --name=rmi-server -p 5000:10101 --rm rmi-server
```
# Dev Documentation
## Emulator configuration
The [emulator_configuration](docs/emulator_configuration.pdf) document shows the configuration possibilities for the autopilot emulators.
## HardwareEmulator JNI interface
The interface of between the RMIModelServer and the HardwareEmulator works with _Java Native Interface (JNI)_. In case of an update
of the interface (file: [src/main/java/simulator/integration/HardwareEmulatorInterface.java](src/main/java/simulator/integration/HardwareEmulatorInterface.java)),
the corresponding C header has to be generated.
Currently, this happens in the [hardware_emulator](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/hardware_emulator) project under the `jni` folder,
where the HardwareEmulatorInterface.java has to be copied. `generate.bat` shows how to update the interface on Windows.
The java file has to be adapted to compile without its dependencies, since the JNI header will only
be generated from compilable java files. Since the actual header file only depends on the `native` functions from the java file, the other dependencies can
be safely deleted. The resulting header file then has to be renamed `emulator_server.h` and placed in the `hardware_emulator/src/emulator` source folder.
The corresponding implementations of the C interface have to be updated in `hardware_emulator/src/emulator/emulator_server.cpp`.
A better approach would be a script in the RMIModelServer project generating the header and copying it to the *hardware_emulator* project.
## New autopilot EMA port types
To communicate with the ports from the autopilot, an _AutopilotAdapter_ encapsulates the EMA model. For new port data types,
the *EMAM2CPP* generator and the *hardware_emulator* have to be updated to handle the new data type.
In the EMAM2CPP project, the `de.monticore.lang.monticar.generator.cpp.viewmodel.AutopilotAdapterDataModel` class is responsible to create the _AutopilotAdapter_.
In its `addInput` and `addOutput` functions, the new function definition and declarations for the data type have to be defined.
In the *hardware_emulator* projects, three places require updates for new data types.
1. The `hardware_emulator/src/emulator/function_values.h / .cpp` files need to updated with the new data type (`enum class VALUE_TYPE`), buffer entry (`struct FunctionValue`) and type name (`FunctionValue::get_type()`).
2. The `call_input()` and `call_output()` functions from the `HardwareEmulator` structure (`hardware_emulator/src/emulator/hardware_emulator.h`) must be updated. They need to know how to pass the arguments to the emulated autopilots.
3. The `Java_simulator_integration_HardwareEmulatorInterface_add_1one_1input()` and `Java_simulator_integration_HardwareEmulatorInterface_query_1outputs()` functions need to know how to pass and read port data to and from Java. (`hardware_emulator/src/emulator/emulator_server.h`)
## Unsupported autopilot functionalities.
The emulator used in this RMIModelServer only implements features encountered in previous autopilots.
New autopilots might trigger new unsupported features:
* Unsupported system calls (enable `debug=unsupported_syscalls` flag for the autopilot emulator). These are operating system functions for which no current emulation is implemented. These have to be added and registered in the `hardware_emulator/src/os_linux/linux_calls.h / .cpp` files for Linux and in the `hardware_emulator/src/os_windows/windows_calls.h / .cpp` files for Windows.
* Unsupported instruction time value. The time table (currently `hardware_emulator/src/timetable/skylake.txt`) describing the number of CPU cycles for every instruction is manually filled. It currently only contains entries (!=0) for encountered instructions. It can be filled with elements from the `hardware_emulator/docs/instruction_time.txt` file (which contains entries from the instruction_tables.pdf file).
To make sure the autopilot emulation is correct, allocate an autopilot emulator with the `test_real` flag. When loading an autopilot with the same OS as the RMIModelServer, the emulator will compare the outputs of the emulated autopilot with the outputs of the actual autopilot program.
docker/Dockerfile
View file @ 4195ee41
......@@ -17,7 +17,6 @@ RUN apt-get update && \
COPY rmi-model-server.jar ./rmi-model-server.jar
COPY ./autopilots/ ./autopilots/
COPY ./softwares/ ./softwares/
CMD exec bash -c "source ~/.bashrc && java -jar rmi-model-server.jar -Djava.rmi.server.hostname=localhost port=10101 autopilots_folder=autopilots no-zookeeper \
no_time os=windows"
CMD exec bash -c "source ~/.bashrc && java -jar -Djava.rmi.server.hostname=localhost rmi-model-server.jar port=10101 softwares_folder=softwares no-zookeeper"
docker/build.sh
View file @ 4195ee41
......@@ -8,6 +8,6 @@
cp ../install/rmi-model-server.jar ./
cp -r ../install/autopilots ./autopilots
cp -r ../install/softwares ./softwares
docker build -t rmi-server .
docs/latex/emulator_configuration.aux deleted 100644 → 0
View file @ 97374b5a
\relax
\newlabel{emuconfig}{{}{1}}
\newlabel{tab:emuconfig}{{}{1}}
\newlabel{tab:managerconfig}{{}{1}}
\newlabel{tab:managerqueries}{{}{1}}
\newlabel{tab:emuqueries}{{}{1}}
docs/latex/emulator_configuration.fdb_latexmk deleted 100644 → 0
View file @ 97374b5a
# Fdb version 3
["pdflatex"] 1568890713 "b:/montisim-setup/repos/RMIModelServer/docs/latex/emulator_configuration.tex" "b:/montisim-setup/repos/RMIModelServer/docs/latex/emulator_configuration.pdf" "emulator_configuration" 1568890713
"C:/Program Files/MiKTeX 2.9/fonts/tfm/public/cm/cmbx10.tfm" 1136768653 1328 c834bbb027764024c09d3d2bf908b5f0 ""
"C:/Program Files/MiKTeX 2.9/fonts/tfm/public/cm/cmitt10.tfm" 1136768653 768 2297ad2ac26f37e67f756dad27c77d68 ""
"C:/Program Files/MiKTeX 2.9/fonts/tfm/public/cm/cmti10.tfm" 1136768653 1480 aa8e34af0eb6a2941b776984cf1dfdc4 ""
"C:/Program Files/MiKTeX 2.9/fonts/tfm/public/cm/cmtt10.tfm" 1136768653 768 1321e9409b4137d6fb428ac9dc956269 ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmbx10.pfb" 1247596666 34811 78b52f49e893bcba91bd7581cdc144c0 ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmitt10.pfb" 1247596666 26057 4749ebe351ca6b60601cf0ab49d1bf5d ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmmi10.pfb" 1247596667 36299 5f9df58c2139e7edcf37c8fca4bd384d ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmmi7.pfb" 1247596667 36281 c355509802a035cadc5f15869451dcee ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr10.pfb" 1247596667 35752 024fb6c41858982481f6968b5fc26508 ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmsy10.pfb" 1247596667 32569 5e5ddc8df908dea60932f3c484a54c0d ""
"C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmtt10.pfb" 1247596667 31099 342ef5a582aacbd3346f3cf4579679fa ""
"C:/Users/Jean/AppData/Local/MiKTeX/2.9/miktex/data/le/pdftex/pdflatex.fmt" 1562925836 4235381 0468f7ea654e25346755a1cc34bf5b43 ""
"C:/Users/Jean/AppData/Local/MiKTeX/2.9/pdftex/config/pdftex.map" 1562925912 80453 73224248f0a73acd005b5611945eaaa6 ""
"b:/montisim-setup/repos/RMIModelServer/docs/latex/emulator_configuration.aux" 1568890713 9 a94a2480d3289e625eea47cd1b285758 ""
"b:/montisim-setup/repos/RMIModelServer/docs/latex/emulator_configuration.tex" 1568890711 8550 c3bfea48587967d0f21fa2e13e69064c ""
"emulator_configuration.aux" 0 -1 0 "pdflatex"
"emulator_configuration.tex" 1568890711 8550 c3bfea48587967d0f21fa2e13e69064c ""
(generated)
"emulator_configuration.aux"
"emulator_configuration.pdf"
"b:/montisim-setup/repos/RMIModelServer/docs/latex/emulator_configuration.log"
"emulator_configuration.log"
"b:/montisim-setup/repos/RMIModelServer/docs/latex/emulator_configuration.pdf"
docs/latex/emulator_configuration.fls deleted 100644 → 0
View file @ 97374b5a
PWD b:\montisim-setup\repos\RMIModelServer\docs\latex
INPUT C:\Users\Jean\AppData\Local\MiKTeX\2.9\miktex\data\le\pdftex\pdflatex.fmt
INPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.tex
OUTPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.log
INPUT C:\Program Files\MiKTeX 2.9\fonts\tfm\public\cm\cmtt10.tfm
INPUT C:\Program Files\MiKTeX 2.9\fonts\tfm\public\cm\cmitt10.tfm
INPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.aux
INPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.aux
OUTPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.aux
INPUT C:\Program Files\MiKTeX 2.9\fonts\tfm\public\cm\cmbx10.tfm
INPUT C:\Program Files\MiKTeX 2.9\fonts\tfm\public\cm\cmti10.tfm
OUTPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.pdf
INPUT C:\Users\Jean\AppData\Local\MiKTeX\2.9\pdftex\config\pdftex.map
INPUT b:\montisim-setup\repos\RMIModelServer\docs\latex\emulator_configuration.aux
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmbx10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmbx10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmitt10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmitt10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmmi10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmmi10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmmi7.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmmi7.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmr10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmr10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmsy10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmsy10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmtt10.pfb
INPUT C:\Program Files\MiKTeX 2.9\fonts\type1\public\amsfonts\cm\cmtt10.pfb
docs/latex/emulator_configuration.log deleted 100644 → 0
View file @ 97374b5a
This diff is collapsed.
docs/latex/emulator_configuration.tex deleted 100644 → 0
View file @ 97374b5a
% (c) https://github.com/MontiCore/monticore
%
% The license generally applicable for this project
% can be found under https://github.com/MontiCore/monticore.
\usepackage{graphicx}
%\usepackage{ngerman}
\usepackage[utf8x]{inputenc}
\usepackage{fancyvrb}
\usepackage{courier}
\usepackage{amsmath}
\usepackage{amssymb}
\usepackage{helvet}
\usepackage{pbox}
\usepackage{xcolor}
\usepackage{pdfpages}
\usepackage[strict]{changepage}
\usepackage{calc}
\usepackage{enumitem}
\usepackage{array}
\usepackage{tabularx}
\usepackage{tabu}
\usepackage{multirow}
\usepackage{tikz}
\usetikzlibrary{tikzmark}
\usetikzlibrary{calc}
\usetikzlibrary{decorations.pathreplacing}
\usetikzlibrary{datavisualization}
\usepackage[htt]{hyphenat}
\usepackage{float}
\newfloat{example}{tbh}{exa}[chapter]
\floatname{example}{Example}
\usepackage{siunitx}
\usepackage{pgfplots}
%\usepackage{hyperref}
%\usepackage{url}
\pgfplotsset{compat=newest} % Allows to place the legend below plot
\usepgfplotslibrary{units} % Allows to enter the units nicely
%\the\textwidth = 426.79pt
%\the\arrayrulewidth = 0.4pt
\pdfoptionpdfminorversion=6
% \definecolor{se_dark_blue}{RGB}{0,103,166} % powerpoint
\definecolor{se_dark_blue}{RGB}{0,96,178} % website
% \definecolor{se_light_blue}{RGB}{119,158,201} % powerpoint
\definecolor{se_light_blue}{RGB}{129,160,225} % website
\graphicspath{{src/pic/}}
%%\newcommand{\tc}[1]{\Large{\fontfamily{ph v}\selectfont{#1}}}
\newcommand{\tc}[1]{\normalsize{#1}}
\newcommand{\tm}[1]{\scriptsize{#1}}
\newcommand{\ttt}[1]{\scriptsize{\texttt{#1}}}
\newcommand{\tsf}[1]{\scriptsize{\textsf{#1}}}
\newcommand{\tit}[1]{\scriptsize{\textit{#1}}}
%% setup listings
\usepackage{listings}
\lstset{
language=C++,
frame=none,
basicstyle=\small\ttfamily,
}
\lstset{
language=Java,
frame=none,
basicstyle=\small\ttfamily,
}
\lstdefinestyle{MontiArcStyle}{
numbers=left,
numberstyle=\tiny,
numbersep=5pt,
xleftmargin=11pt,
xrightmargin=4pt,
frame=single,
aboveskip=0pt,
belowskip=-6pt,
sensitive=true,
float=!t,
breaklines=false,
captionpos=b,
tabsize=2,
showstringspaces=false,
basicstyle=\small\ttfamily,
morecomment=[l]{//},
morecomment=[s][\itshape]{/**}{*/}
}
%% defines the listings laguage named 'MontiArc' derived from the language 'Java'
%% adding the below listed keywords. See
%% ftp://ftp.tex.ac.uk/tex-archive/macros/latex/contrib/listings/listings.pdf
%% for listings documentation
\lstdefinelanguage{MontiArc}[]{Java}{
morekeywords={component, port, in, out, inv, package, import, connect, autoconnect}
}
% Seite einrichten
\setlength{\voffset}{-1in}
\setlength{\hoffset}{-1in}
\setlength{\topmargin}{2.5cm}
\setlength{\headheight}{0cm}
\setlength{\headsep}{0cm}
\setlength{\oddsidemargin}{3,3cm} % innen ein wenig mehr Rand für die Klebebindung
\setlength{\evensidemargin}{2,7cm} % dafür außen ein wenig weniger
\setlength{\textwidth}{15cm}
\setlength{\textheight}{23,5cm}
\setlength{\parindent}{0cm}
\newcommand{\emptyLine}{{\LARGE ~\\}}
\begin{document}
\setcounter{page}{1}
\pagenumbering{arabic}
\section{Configuration}
\label{emuconfig}
The HardwareEmulator and the EmulatorManager support a simple fail-safe way of configuring them and making queries to them. A message is made of a String where each line (separated by a newline character) is a name followed by optional parameters.
The syntax is whitespace insensitive and as follows:
\begin{verbatim}
name = param1, param2, param...
or
name
\end{verbatim}
Whitespace is optional, and the only separating characters are the equal sign ($=$), the comma (,) and the newline character (\texttt{\textbackslash n}).
\subsection{Configuration}
The current settings supported when allocating an emulator are shown in Table~\ref{tab:emuconfig}.
\begin{table}[!htb]
\begin{tabularx}{\textwidth}{ | X |}
\hline
\texttt{autopilot=name} \\
Name of the autopilot program file, without extension.\\ \hline
\texttt{os=name} \\
Name of the operating system used. Currently \texttt{linux} or \texttt{windows}. This implies the extension of the autopilot file searched. If the os command is not given, the Emulator will search for any autopilot with the given name in the search folder. \\ \hline
\texttt{debug=flag1,flag2,\dots} \\
Enable the debugging outputs for the specified flags, where the flags are any of \texttt{mem}, \texttt{regs}, \texttt{reg\_update}, \texttt{syscalls}, \texttt{unsupported\_syscalls}, \texttt{code} or \texttt{call}. \\\hline
\texttt{cpu\_frequency=value} \\
The CPU frequency in Hertz used to evaluate the computation time. \\\hline
\texttt{memory\_frequency=value} \\
The RAM frequency in Hertz used to evaluate the computation time. \\\hline
\texttt{cache\_name=size,read\_ticks,write\_ticks} \\
Where \texttt{name} is \texttt{IL1}, \texttt{DL1}, \texttt{L2} or \texttt{L3}.
This setting enables and sets the parameters of the named cache layer. Set \texttt{size} to 0 to disable this cache level. The ticks refer to the CPU ticks.\\\hline
\texttt{no\_time} \\
Disables the delaying of the autopilot in the simulation. \\\hline
\texttt{test\_real} \\
If the RMIModelServer and the autopilot are of the same operating system type, this flag makes the emulator load the autopilot directly as a library (not emulated) and uses its outputs to validate those of the emulated instance. \\
\texttt{export} \\
Enables the \texttt{HardwareEmulator} to export the deviation from the planned trajectory and the evaluated execution time of the autopilot. Data is currently exported for the first 60 seconds of the simulation. The output files are \texttt{autopilot\_dist.txt} and \texttt{autopilot\_time.txt}.
\\\hline
\end{tabularx}
\caption{HardwareEmulator Configuration}
\label{tab:emuconfig}
\end{table}
The \texttt{EmulatorManager} itself also supports a config string on initialization. Table~\ref{tab:managerconfig} shows the supported config.
\begin{table}[!htb]
\begin{tabularx}{\textwidth}{ | X |}
\hline
\texttt{autopilots\_folder=folder} \\
Sets the folder in which to look for autopilot programs.\\ \hline
\end{tabularx}
\caption{EmulatorManager Configuration}
\label{tab:managerconfig}
\end{table}
\subsection{Queries}
The query system uses the same presented syntax, but also sends a response for every query, using the same syntax.
Queries supported by the \texttt{EmulatorManager} are shown in Table~\ref{tab:managerqueries}.
\begin{table}[!htb]
\begin{tabularx}{\textwidth}{ >{\em}l | X |}
\cline{2-2}
Query & \texttt{get\_error\_msg} \\
Response & \texttt{error\_msg=msg} \\
& Returns the last error message that occurred while allocating an autopilot emulator. \\ \cline{2-2}
Query & \texttt{get\_available\_autopilots} \\
Response & \texttt{available\_autopilots=autopilot1, autopilot2, \dots} \\
& Returns the list of autopilot files available in the autopilot folder. \\ \cline{2-2}
Query & \texttt{get\_available\_threads} \\
Response & \texttt{available\_threads=thread\_count} \\
& Returns the number of concurrent threads the machine running the RMIModelServer supports.\\ \cline{2-2}
Query & \texttt{get\_autopilots\_folder} \\
Response & \texttt{autopilots\_folder=folder} \\
& Returns the current autopilots folder.\\ \cline{2-2}
\end{tabularx}
\caption{EmulatorManager queries.}
\label{tab:managerqueries}
\end{table}
Queries supported by querying a specific emulator are shown in Table~\ref{tab:emuqueries}.
\begin{table}[!htb]
\begin{tabularx}{\textwidth}{ >{\em}l | X |}
\cline{2-2}
Query & \texttt{get\_avg\_runtime} \\
Response & \texttt{avg\_runtime=time} \\
& Returns the mean average time of autopilot execution.\\ \cline{2-2}
Query & \texttt{is\_computing} \\
Response & \texttt{computing=1 or 0} \\
& Returns 1 if the computer is considered to be computing in simulation time.\\ \cline{2-2}
Query & \texttt{get\_computer\_time} \\
Response & \texttt{computer\_time=time} \\
& Returns the time counter of the computer, in microseconds.\\ \cline{2-2}
\end{tabularx}
\caption{HardwareEmulator queries.}
\label{tab:emuqueries}
\end{table}
\end{document}
docs/latex/make.bat deleted 100644 → 0
View file @ 97374b5a
@REM
@REM (c) https://github.com/MontiCore/monticore
@REM
@REM The license generally applicable for this project
@REM can be found under https://github.com/MontiCore/monticore.
@REM
@echo off
set GENDIR=target\
set MAINNAME=emulator_configuration
set MAINTEX=%MAINNAME%.tex
set TARGET=%GENDIR%%MAINNAME%.pdf
mkdir %GENDIR%
@echo ------------initial pdf-latex run
pdflatex -output-directory=%GENDIR% %MAINTEX%
@echo ------------Make index
IF EXIST "%GENDIR%%MAINNAME%.idx" makeindex %GENDIR%%MAINNAME%.idx
@echo ------------2nd pdf-latex run
pdflatex -output-directory=%GENDIR% %MAINTEX%
@echo ------------3rd pdf-latex run
pdflatex -output-directory=%GENDIR% %MAINTEX%
install/config.bat
View file @ 4195ee41
......@@ -7,7 +7,7 @@
@REM Please replace this with the path to the Autopilot(s)
set AUTOPILOT_FOLDER=autopilots
set SOFTWARES_FOLDER=softwares
@REM Change the port if you need to
set PORT=10101
install/config.sh
View file @ 4195ee41
......@@ -8,7 +8,7 @@
# Please replace this with the path to the Autopilot(s)
AUTOPILOT_FOLDER=autopilots
SOFTWARES_FOLDER=softwares
# Change the port if you need to
PORT=10101
install/run.bat
View file @ 4195ee41
......@@ -9,7 +9,7 @@
@echo off
call config.bat
echo Starting RMIModelServer on port %PORT% with Autopilot folder: %AUTOPILOT_FOLDER%
echo Starting RMIModelServer on port %PORT% with with softwares folder: %SOFTWARES_FOLDER%
@REM java "-Djava.rmi.server.codebase=file:rmi-model-server.jar" "-Djava.rmi.server.hostname=localhost" -cp rmi-model-server.jar rwth.rmi.model.server.RMIServer %PORT% %AUTOPILOT_FOLDER% --no-zookeeper %*
java -jar rmi-model-server.jar port=%PORT% autopilots_folder=%AUTOPILOT_FOLDER% no-zookeeper default_config %*
java -jar rmi-model-server.jar port=%PORT% softwares_folder=%SOFTWARES_FOLDER% no-zookeeper
pause
install/run.sh
View file @ 4195ee41
......@@ -9,6 +9,5 @@
source ./config.sh
echo "Starting RMIModelServer on port $PORT with Autopilot folder: $AUTOPILOT_FOLDER"
# java "-Djava.rmi.server.codebase=file:rmi-model-server.jar" "-Djava.rmi.server.hostname=localhost" -cp rmi-model-server.jar rwth.rmi.model.server.RMIServer $PORT $AUTOPILOT_FOLDER --no-zookeeper os=linux no_time
java "-Djava.rmi.server.hostname=localhost" -jar rmi-model-server.jar port=$PORT autopilots_folder=$AUTOPILOT_FOLDER no-zookeeper default_config os=linux no_time
\ No newline at end of file
echo "Starting RMIModelServer on port $PORT with Autopilot folder: $SOFTWARES_FOLDER"
java "-Djava.rmi.server.hostname=localhost" -jar rmi-model-server.jar port=$PORT softwares_folder=$SOFTWARES_FOLDER no-zookeeper
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment