Using these user input and other predefined settings, the script then generates the txt2dbf script and another bash script that are executed later.

Transcription

1 Ryan Bravo Research Documentation May 16, 2008 Scripts To facilitate speedy and easy generation of the 2D raster images and videos, I wrote a series of scripts. One bash script governs the whole system, setting environment variables and calling the other scripts. The script takes input. Following a -s flag, the user can specify the starting time in the format hh:mm:ss. Similarly, a -e flag specifies the ending time in the format hh:mm:ss. A -i flag means the number of time steps you want the data to be broken into will follow. If none of these are specified, the defaults are 00:00:00 for start time, 24:00:00 for the end time (A time that is technically not possible but acts as an upper bound), and 96 for the time step. The governing script first calls a PERL script. The PERL script takes a call data file and generates the activity data. The data file must be sorted in chronological order. The data file says a call was made at a certain time at a certain location with a certain tower number and the script aggregates this, replacing the tower number with a hashed number based on location (there are many cases where different towers exist at the same location, their call data must be combined). A data file containing the tower number and its hashed value needs to be included in the directory where the script is executing. The PERL script can read multiple data files now. To cut down on search time, if a user only wants data that is towards the end of the file and to simulate the real time execution of the file, I broke up the large data file into 96 smaller ones (15 minute increments). There is a file name variable that needs to be set, this is the base name for all of the files. The script will then cycle through all of the necessary files as long as they are named correctly. The need to be named as the base name followed by the hour and quarter hour. So if a file contains data for 11:00am-11:15am, the file would need to be named basename for the hour and 0 because it is the first quarter of the hour. Using these user input and other predefined settings, the script then generates the txt2dbf script and another bash script that are executed later. The txt2dbf script generates a dbf file out of the data generated in the PERL script. That dbf file is later loaded into GRASS with the voronoi cell shape file. The bash script that was generated previously is then called. This loads the new shapefiles into GRASS as vector data with the activity snapshots as attributes. This vector is then converted into X snapshots of raster data. Each of these raster files are output as jpg and into an mpeg animation. I have overlayed a road vector on the jpg output by redirecting the output from the computer monitor to a picture file. To run the script you need the main bash scripts, the first script it calls, the tower hash file, and the call activity file. No other files are actually necessary. The script itself creates the SQL file, the second bash script, the activity data file, the jpg pictures, and the mpeg.

2 Console The console was built by mashing a few different technologies together: HTML, PHP, JavaScript, and some other stuff for good measure. The JavaScript is primarily AJAX, specifically an AJAX library called dojo. The console architecture is interesting. The file, console.html, controls the whole thing. Depending on which tab is selected, JavaScript will write whatever it needs to to the browser. The GIS, GIS Sim, Disaster, Call Activity, Data Analysis, and Simulation tabs all work under a similar principle. They call a JavaScript file that calls a PHP file. The PHP reads the contents of a directory (which should contain picture files). The names of those files are then passed back to the JavaScript. The JavaScript generates a slideshow of those files which is displayed in the browser. Here is a handy table to keep these relationships straight: Tab Name JavaScript Php Image folder GIS newfilecheck.js listfolderfile.php Images GIS Sim newfilecheck2.js listfolderfile2.php Images, Images2 Disaster newfilecheck3.js listfolderfile3.php Images, Images2, Images3, Images4 Call Activity activitycheck.js listfolderactivity.php activity_images Data Analysis dataanacheck.js listfolderdataana.php dataana_images Simulation SPSCheck.js listfoldersps.php SPS_images My work on the console focused on 4 of the tabs. I added the GIS Sim and Disaster tabs and made changes to the GIS and Call Activity tabs. GIS Tab The GIS Tab was a slide show of fairly meaningless pictures when I started. Using the scripts I had created over the summer, I replaced the old pictures with an actual day's worth of pictures. listfolderfile.php reads all of the images in the Images folder, and displays them in the slide show. These should only be the output of my scripts. The next step in this work would be to allow the web user to start the script with options, like I've done with the Call Activity tab. GIS Sim and Disaster Tabs I created the GIS Sim and Disaster Tabs. They are basically the GIS Tab with additional slide shows. The GIS Sim tab has real world data with the output of one simulation next to it. The Disaster tab is real world data with the output of 3 simulations next to it. This is all static at this point. The simulations and real world pictures are created and put in the correct folder and the console just reads them. I spent some time this year getting the output of my scripts to look like the simulation output, so the pictures should be scaled to look similar. Call Activity Tab When I started, the Call Activity Tab was a bunch of static images in a slide show that didn't mean anything. Now, it lets the user choose which days to display and input options then generates graphs and shows them.

3 I have data for a simulated day and real data for a 6 day period. Data from any of these days can be shown. It is saved in a data file callact.dat in periods of 5 minutes. The user can input how many minutes they want each data point on the graph to be, in increments of 5 minutes (because the data is in 5 minute chunks). They can also choose how many points go on each graph. When the user submits the form, an exec command calls a shell script, gnumake.sh. It calls databreak.pl which breaks the data file up into increments that correspond to one graph each. databreak.pl also creates a file called gnuscript.gp. The gnumake.sh file then calls the gnuscript.gp file, which makes each graph in a series using gnuplot functions. These graphs are output as.gifs into the activity_images folder. The pictures are all output to the same folder. listfolderactivity.php reads all of the.gif files in the activity_images folder. Using one of those handy slide shows, the new pictures are then displayed on the console. GnuPlot The databreak.pl actually hard codes the gnuscript.gp file. It creates file names, so instead of trying to do intense string manipulation in a gnuplot script (which I doubt it possible), I used a few scripts to have databreak.pl actually hard code what otherwise might be done in a loop. Gnuplot is pretty simple. You set the output type (gif in my script), set the output destination (the filename). Then you set the x and y ranges in the plots. The x range is just the number of data points on the graph. The y range is trickier. I noticed there were never more than 7500 calls in a 5 minute period, so the simplest way to ensure the plots don't go out of range is to multiply the number of 5 minute periods per point (1 for 5 minutes, 2 for 10 minutes, etc) by Then there is a plot command to actually write the graph. Here is the syntax: plot 'datafile' using column_number title 'line_name' with lines That repeats for each line being graphed. Here is an example: plot '/var/www/calldata/newfiledata000.dat' using 1 title 'estimation' with lines, '/var/www/calldata/newfiledata000.dat' using 2 title 'Thursday' with lines Photo Slide shows The photo slide shows that are on a few of the tabs are defined in the Dojo libraries. They have a template located at /js/dojo/src/widget/templates/htmlslideshow.html Changing this will change all the slide shows. This is where you can change default dimensions and stuff. Simulations Towards the end of the semester, I was tasked with running the WIPER simulations created by Tim Schoenharl and Ryan McCune. Ryan wrote simulations where agents follow roads when they flee. He hadn't been able to get his and Tim's simulations working at the same time. Using an old version of

4 Tim's simulations, I got his simulations working. Alec has this older version. I tried dropping Ryan's code into the build, but could not get them to compile. After weeks of work, I found the problem. Ryan wrote his simulations with a newer version of the GeoTools library. Tim's simulations don't work with the new version because some functions are deprecated. Ryan's simulations don't work with the old version because they call functions that don't exist in the old GeoTools. If someone were to work on these simulations again. I would suggest getting the new version of GeoTools and trying to edit Tim's simulations. I don't think GeoTools would reduce functionality in newer versions, so there should be a way to re-code Tim's simulations with the new GeoTools. Ryan McCune's simulations, however, were written with this new functionality in mind. I haven't researched it, but I would think that rewriting his simulations could take major revisions. So I would recommend converting Tim's simulations to the new GeoTools syntax. One problem I encountered with the simulations was picture output. The simulations output what is being displayed on the OpenMap screen. You define the size of the OpenMap window, though, and the window size you choose INCLUDES toolbars and stuff. So if you define the OpenMap window to be 800x600, your picture outputs will actually be something like 791x421 or something like that. The resolution of your screen also matters. I was stuck on a 800x600 screen, so I couldn't make big pictures. The OpenMap screen topped out at the highest resolution of my screen and then took the toolbar pictures off of that. Keep this in mind when you are choosing a window size.

5