ExternalVendorCode/trick
1
0
Fork 0
mirror of https://github.com/nasa/trick.git synced 2024-12-21 06:03:10 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
6691b14e9e
trick/docs/tutorial/TutVariableServer.md
Scott Fennell 66c5852566 update doc links
2019-11-20 12:53:56 -06:00

477 lines
18 KiB
Markdown
Raw Blame History

| [Home](/trick) → [Tutorial Home](Tutorial) → Variable Server |
|------------------------------------------------------------|
# Trick Variable Server
**Contents**
* [What Is The Variable Server?](#what-is-a-variable-server)
* [Variable Server Sessions](#variable-server-sessions)
* [A Simple Variable Server Client](#a-simple-variable-server-client)
* [Listing - CannonDisplay_Rev1.py](#listing-CannonDisplay_Rev1-py)
* [Running The Client](#running-the-client)
* [How The Client Works](#how-the-client-works)
* [Getting Values Just Once](#getting-values-just-once)
* [Running the Client From the Input File](#running-the-client-from-the-input-file)
* [A More Realistic Example](#a-more-realistic-example)
***
This tutorial section will demonstrate how to write a Trick variable server
client. We'll be writing the clients in Python, but they can be written in any
language. We'll start out with a minimal client and then gradually update it.
We'll be interfacing with our Cannon ball simulation.
***
<a id=what-is-the-variable-server></a>
## What is The Variable Server?
Every Trick simulation contains a **Variable Server**, a TCP/IP network service
for interacting with the simulation while it's running. Like the input-file
processor, the variable server uses a Python interpreter that's bound to the
simulation's variables and functions. So, just as in an input file, one can set
variable values and call functions from a variable server client. A variable
server specific API also exists to get simulation data back to the client.
The Trick Sim Control Panel, and Trick-View are, for example, both variable
server clients.
<a id=variable-server-sessions></a>
### Variable Server Sessions
Each variable server connection creates a **variable server session**, whose
configuration identifies what, when, and how data will be sent from the server
to the client. A session configuration consists of the following information:
* A list of names of the variables whose values are to be sent in messages to
the client.
* The rate at which messages are transmitted to the client.
* How messages are encoded. (ASCII or binary).
* Whether messages are guaranteed to be time homogenous.
* Whether message transmission is synchronous with the main simulation thread.
* Whether data transmission is paused (inactive), or unpaused (active).
* The debug state of the connection.
* An optional name, to identify the connection when debug messages are enabled.
![VarServerSessions](images/VarServerSessions.png)
The primary purpose of the [**variable server API**](#the-variable-server-api)
is to configure the sessions.
## Approach
Calling functions and setting simulation variables using the variable server is
done as in the input file. That is, the client sends Python code to the variable
server where it's executed, to call functions, set variables, or both. In the
following sections we'll see examples of these. We'll also learn how to use the
variable server API to get data back to the client.
<a id=a-simple-variable-server-client></a>
## A Simple Variable Server Client
The listing below implements a very simple variable server client for our
cannonball simulation. It connects to the simulation, requests cannonball
position data, and prints the periodic responses to the screen.
<a id=listing-CannonDisplay_Rev1-py></a>
**Listing - CannonDisplay_Rev1.py**
```python
#!/usr/bin/python
import sys
import socket
# Process the command line arguments.
if ( len(sys.argv) == 2) :
trick_varserver_port = int(sys.argv[1])
else :
print( "Usage: vsclient <port_number>")
sys.exit()
# Connect to the variable server.
client_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
client_socket.connect( ("localhost", trick_varserver_port) )
insock = client_socket.makefile("r")
# Request the cannon ball position.
client_socket.send( "trick.var_pause()\n" )
client_socket.send( "trick.var_ascii()\n" )
client_socket.send( "trick.var_add(\"dyn.cannon.pos[0]\") \n" +
"trick.var_add(\"dyn.cannon.pos[1]\") \n"
)
client_socket.send( "trick.var_unpause()\n" )
# Repeatedly read and process the responses from the variable server.
while(True):
line = insock.readline()
if line == '':
break
print line
```
<a id=running-the-client></a>
### Running the Client
To run the variable server client :
* Create a new file called *CannonDisplay_Rev1.py* in your home directory,
and copy the contents of the above listing above into it.
* Make the file executable. Example: ```% chmod +x CannonDisplay_Rev1.py```.
* Execute, but don't "Start" the cannonball simulation.
* Find the variable server port number in the bottom left hand corner of the Sim
Control Panel, as shown below.
* Execute the script with the port number as an argument. Example:
```$ ~/CannonDisplay_Rev1.py 50774 &```
![Cannon](images/SimControlPanel.png)
The output of the script will display three columns of numbers. The left most
number is the [variable server message type](#variable-server-message-types).
Here, a message type of 0 indicates that the message is the (tab delimited) list
of the values we requested. This is the only message type we'll be concerned
with in this tutorial. The two columns to the right of the message number are
the values of ```dyn.cannon.pos[0]``` and ```dyn.cannon.pos[1]```, in the order
that they were specified in the script.
```
0 55.85863854409634 24.0875895
0 60.18876556301853 25.2730495
0 64.51889258194073 26.36040950000001
0 68.84901960086293 27.34966950000001
0 73.17914661978513 28.24082950000001
```
<a id=how-the-client-works></a>
### How the Client Works
The script first gets the variable server's port number, and creates a TCP/IP connection to it.
The script then configures the variable server session, with the commands listed below, to periodically send the cannonball position with the following commands:
* **trick.var_pause()**
* **trick.var_ascii()**
* **trick.var_add("dyn.cannon.pos[0]")**
* **trick.var_add("dyn.cannon.pos[1]")**
* **trick.var_unpause()**
The [**var_pause**](#api-var-pause), and [**var_unpause**](#api-var-unpause) commands
are generally used at the beginning, and ending of variable server session configurations. [**var_pause**](#api-var-pause) tells the variable server to stop
sending data, if it is. [**var_unpause**](#api-var-unpause), tells the variable server to start sending data.
The [**var_ascii**](#api-var-ascii) command then tells the variable server to send messages using an ASCII encoding (rather than
binary).
The two [**var_add**](#api-var-add) commands add "dyn.cannon.pos[0]"
and "dyn.cannon.pos[1]" to the session variable list.
:warning: Please notice that the quotes around the variable names must be escaped with the '\' (baskslash) character.
```
client_socket.send( "trick.var_add(\"dyn.cannon.pos[0]\") \n" +
"trick.var_add(\"dyn.cannon.pos[1]\") \n"
)
```
When the [**var_unpause**](#api-var-unpause) command is executed, messages containing the values of the variables listed in the session variable list will be repeatedly created, and sent to the client.
By default, the variable server sends data every 0.1 seconds (that is, 10 hertz). This is equivalent to commanding: [**var_cycle(0.1)**](#api-var-cycle).
The script then enters a while-loop that repeatedly 1) waits for, 2) reads, and 3) prints the raw responses from the variable server. The responses are encoded in ASCII, as specified by [**var_ascii**](#api-var-ascii), and are of the following format:
```
0\t<variable1-value>[\t<variable2-value>...\t <variableN-value> ]\n
```
<a id=getting-values-just-once></a>
## Getting Values Just Once
Suppose we wanted to get the value of the initial angle of our cannon. We don't need to get it repeatedly, because it doesn't change. We just want to get it once, and then to repeatedly get the position data, which changes over time.
For this situation we can use the [**var_send**](#api-var-send) command, which tells the variable server to send the values specified in the session variable list immediately, regardless of whether [**var_pause**](#api-var-pause) was previously commanded.
To demonstrate how this works, let's add the following code to our script, right after the line where we sent the **var_ascii** command.
```python
client_socket.send( "trick.var_add(\"dyn.cannon.init_angle\")\n")
client_socket.send( "trick.var_send()\n" )
line = insock.readline()
print line
client_socket.send( "trick.var_clear()\n" )
```
In this snippet of code, we add ```dyn.cannon.init_angle``` to the session variable list.
Then we call [**var_send**](#api-var-send) to tell the variable server to send us the value, and wait for the response by calling ```insock.readline()```. When it arrives, we print it.
Before the script adds the cannon position variables, we need to remove ```dyn.cannon.init_angle```, otherwise we'll be getting this in our messages too. We can do this in one of two ways. We can 1) call
[**var_clear**](#api-var-clear) to clear the the list, or 2) we can call [**var_remove**](#api-var-remove). Specifically we could do the following:
```client_socket.send("trick.var_remove(\"dyn.cannon.init_angle\")\n )```
So, when we run the modified client, the first three lines of the output should look something like the following.
```
0 0.5235987755982988
0 0 0
0 0 0
```
The first line contains the message type ( which is zero), followed by the value of ```dyn.cannon.init_angle```. Subsequent lines contain the position data like before.
<a id=running-the-client-from-the-input-file></a>
## Running a Client From The Input File
Rather than having to start a client each and every time from the command line,
we can easily start it from the input file using the function
```trick.var_server_get_port()``` as illustrated in the following input file
script.
```python
#==================================
# Start the variable server client.
#==================================
varServerPort = trick.var_server_get_port();
CannonDisplay_path = os.environ['HOME'] + "/CannonDisplay_Rev1.py"
if (os.path.isfile(CannonDisplay_path)) :
CannonDisplay_cmd = CannonDisplay_path + " " + str(varServerPort) + " &" ;
print(CannonDisplay_cmd)
os.system( CannonDisplay_cmd);
else :
print('Oops! Can\'t find ' + CannonDisplay_path )
```
Add this to the bottom of RUN_test/input.py to give it a try.
***
<a id=a-more-realistic-example></a>
## A More Realistic Example
```python
#!/usr/bin/python
import sys
import socket
import math
from Tkinter import *
# Client Parameters
HEIGHT, WIDTH = 500, 800 # Canvas Dimensions
MARGIN = 20 # Margins round the axes.
SCALE = 3 # Scale = 3 pixels per meter.
ballRadius = 5 # Ball radius in pixels.
MODE_FREEZE = 1
MODE_RUN = 5
# Variable and Callback for the Fire Button
fireCommand = False
def cannonFire():
global fireCommand
fireCommand = True
# Process the command line arguments.
if ( len(sys.argv) == 2) :
trick_varserver_port = int(sys.argv[1])
else :
print( "Usage: vsclient <port_number>")
sys.exit()
# Create a Canvas to draw on.
tk = Tk()
canvas = Canvas(tk, width=WIDTH, height=HEIGHT)
tk.title("CannonBall Display")
canvas.pack()
# Add a FIRE button
buttonFrame = Frame()
buttonFrame.pack(side=BOTTOM)
fireButton = Button(buttonFrame,text="fire",command=cannonFire)
fireButton.pack(side=LEFT)
# Add an Initial Speed Scale
speedScale = Scale(buttonFrame, from_=5, to=50, label="Initial Speed", orient=HORIZONTAL)
speedScale.pack(side=LEFT)
speedScale.set(50)
# Add an Initial Angle Scale
angleScale = Scale(buttonFrame, from_=5, to=80, label="Initial Angle", orient=HORIZONTAL)
angleScale.pack(side=LEFT)
angleScale.set(30)
# Create coordinate axes on the canvas.
xAxis = canvas.create_line(MARGIN,HEIGHT-MARGIN,WIDTH,HEIGHT-MARGIN)
yAxis = canvas.create_line(MARGIN,HEIGHT-MARGIN,MARGIN,0)
# Create an oval object to represent the cannonball.
cannonBall = canvas.create_oval(0,0,ballRadius,ballRadius, fill="orange")
# Create a text field on the canvas for the simulation mode display.
modeText = canvas.create_text(WIDTH/2, 20, text="--unknown-mode--")
impactTimeText = canvas.create_text(WIDTH/2, 40, text="")
impactPosText = canvas.create_text(WIDTH/2, 60, text="")
# Connect to the variable server.
client_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
client_socket.connect( ("localhost", trick_varserver_port) )
insock = client_socket.makefile("r")
# Request the cannon ball position.
client_socket.send( "trick.var_set_client_tag(\"myvsclient\") \n")
client_socket.send( "trick.var_debug(3)\n" )
client_socket.send( "trick.var_pause()\n" )
client_socket.send( "trick.var_ascii()\n" )
client_socket.send( "trick.var_add(\"dyn.cannon.pos[0]\") \n" +
"trick.var_add(\"dyn.cannon.pos[1]\") \n" +
"trick.var_add(\"trick_sys.sched.mode\")\n" +
"trick.var_add(\"dyn.cannon.impact\") \n" +
"trick.var_add(\"dyn.cannon.impactTime\") \n" )
client_socket.send( "trick.var_unpause()\n" )
# Repeatedly read and process the responses from the variable server.
while(True):
line = insock.readline()
if line == '':
break
# Split the response line into value fields.
field = line.split("\t")
# Update Ball Position
x,y = float(field[1]), float(field[2])
cx,cy = (x*SCALE+MARGIN), (HEIGHT-y*SCALE-MARGIN)
canvas.coords(cannonBall,cx-ballRadius,cy-ballRadius,cx+ballRadius,cy+ballRadius)
# Update Sim Mode
simMode = int(field[3])
if simMode == MODE_FREEZE:
canvas.itemconfigure(modeText, fill="blue", text="FREEZE")
elif simMode == MODE_RUN:
canvas.itemconfigure(modeText, fill="red", text="RUN")
else:
canvas.itemconfigure(modeText, text="--unknown-mode--")
impact = int(field[4])
if simMode == MODE_RUN:
if impact:
canvas.itemconfigure(impactTimeText, text="Impact time = " + field[5])
canvas.itemconfigure(impactPosText, text="Impact pos = (" + field[1] + "," + field[2] + ")")
client_socket.send( "trick.exec_freeze()\n")
# Command the sim from Freeze to Run, when the "Fire" button is pressed.
if simMode == MODE_FREEZE:
if fireCommand:
fireCommand = False
fireButton.config(state=DISABLED)
client_socket.send( "dyn.cannon.init_speed = " + str(speedScale.get()) + " \n")
client_socket.send( "dyn.cannon.init_angle = " + str(angleScale.get()*(math.pi/180.0)) + " \n")
client_socket.send( "trick.cannon_init( dyn.cannon )\n")
client_socket.send( "trick.exec_run()\n")
tk.update()
# Keep the window open, when the data stops.
tk.mainloop()
```
## Appendix
<a id=variable-server-message-types></a>
### Variable Server Message Types
| Name | Value | Meaning |
|-------------------|-------|---------|
| VS\_IP\_ERROR | -1 | Protocol Error|
| VS\_VAR\_LIST | 0 | A list of variable values. |
| VS\_VAR\_EXISTS | 1 | Response to var\_exists( variable_name )|
| VS\_SIE\_RESOURCE | 2 | Response to send_sie_resource|
| VS\_LIST\_SIZE | 3 | Response to var_send_list_size or send_event_data|
| VS\_STDIO | 4 | Values Redirected from stdio if var_set_send_stdio is enabled|
<a id=the-variable-server-api></a>
### The Variable Server API
The following functions are a subset of variable server API functions that are used in this tutorial:
<a id=api-var-add></a>
**var\_add( variable_name )** -
Add a name to the session variable list. The value of the added variable will transmitted in subsequent variable server messages.
<a id=api-var-ascii></a>
**var\_ascii()** -
Set data response messages to the following ASCII encoded format (default):
**0\t**\<variable**1**-value\>[**\t**\<variable**2**-value\>...**\t** \<variable**N**-value\> ]**\n**
Where:
* **N** is the number of variables in the session variable list.
* **\t** is a tab character.
<a id=api-var-binary></a>
**var\_binary()** -
Set response encoding to binary.
<a id=api-var-cycle></a>
**var\_cycle( period )** -
Set data response message period in seconds. (default = 0.1 seconds, i.e., 10 hertz)
<a id=api-var-pause></a>
**var\_pause()** -
Halt periodic responses.
<a id=api-var-unpause></a>
**var\_unpause()** -
Resume periodic responses.
<a id=api-var-send></a>
**var\_send()** -
Send response immediately.
<a id=api-var-clear></a>
**var\_clear()** -
Clear the session variable list.
<a id=api-var-exit></a>
**var\_exit()** -
End the connection to the variable server.
<a id=api-var-remove></a>
**var\_remove( variable_name )** -
Remove the given name from the session variable list.
<a id=api-var-set-client-tag></a>
**var\_set\_client\_tag( text )** - Name the current connection, for debugging.
<a id=api-var-debug></a>
**var\_debug( level )** -
Set the debug level. Set level to 3 for all debug messages, and 0 for no debug messages.
<a id=api-var-sync></a>
**var\_sync( mode )**
Set the synchronization mode of the variable server session, where the modes are:
* **0 = fully asynchronous** (default)
This means that periodic data messages are not guaranteed to
be time homogeneous. That is, data may not all be associated with
a the exact same sim time. The variable server data messages are
written from a thread other than the main thread.
* **1 = sync data gather, async socket write**
This means that periodic data messages are guaranteed to
be time homogeneous, but are written from a thread other
than the main simulation thread.
* **2 = sync data gather, sync socket write**
This means that periodic data messages are guaranteed to
be time homogeneous, but are written from the main simulation thread.
[Next Page](ATutMonteCarlo)
Reference in New Issue View Git Blame Copy Permalink