COS 301 Team Broadsword navigation
| Surname | Name | Student Number |
|---|---|---|
| Bondjobo | Jocelyn | u13232852 |
| Brijlal | Yashvir | u14387744 |
| du Plooy | Andries | u15226183 |
| Jones | Keanan | u13036892 |
| Nxumalo | Banele | u12201911 |
| van Schalkwyk | John | u14307317 |
The Broadsword team will be responsible for the implementation of the Web Navigation system. A documentation of our system has also been provided.
- Start nsq server
- Start MongoDB
- Run navigationLocal.js in main branch directory
- Navigate to "Nav Node Server" directory and run index.js to start server
Example code has been given on how the other modules can communicate with Navigation and how Navigation expects them to communicate back.
Running a full demo with only the examples can be done simply by using the following steps:
- Start an nsq server by using makefile command "make test-comms"
- Start MongoDB
- Run navigationLocal.js in main branch directory
- Start "Nav Node Server > index.js" (example screenshot under img/captureOne.jpg)
- Start "Nav Node Server > nsqExampleAccess.js" (example screenshot under img/captureTwo.jpg)
- Start "Nav Node Server > nsqExampleGIS.js" (example screenshot under img/captureThree.jpg)
-
As of the time this code is published, there are apparently problems with GIS. This causes a GIGO type of effect, meaning that the code either will produce errors if GIS returns the wrong format, or Access will retreive junk routes.
To try and combat this, the cache validation system has been disabled (the code for it can be seen, but is made to never be triggered).
IMPORTANT: If GIS works, the caching system can be activated by un-commenting the code in the file "Nav Node Server > index.js", line 90. (Please refer questions to contact person) - Note: Whenever index.js is terminated via the command prompt. A new terminal should be opened and the index.js file should be run again.