Added models called SimulationRun and Trace.

These should allow for the storing of traces from simulation runs (as the names might suggest).

The ultimate goal might be to support the ability to rerun experiments with the same conditions.
This would require more data to be stored and would need some functionality added to the node-controllers.
However, it would be nice.

For now, it will just allow modellers to store, view and export traces.
Added the record_trace view and URL

This, as yet incomplete, view will take traces uploaded by the node controllers.
It is csrf_exempt, because it is authenticated at each request.
Created a temporary form that can be used to simulate trace uploads.

This will be disappeared eventually.
Merge branch 'master' into recording-traces
Added the ability to send traces from the agent-controller

Currently, this doesn't map back properly to the view in controlserver; that will
need some work.
Added the documentation about the trace user needed for the node controller.
Added the uploaded_media/ directory to the .gitignore

This is so that we don't start committing traces, and potentially any other uploaded media
to git.
If trace upload fails, the error is now printed to the stdout

This allows me to log the errors.
Traces are now stored on the controlserver

The api view has now been written that allows for traces to be uploaded and stored on the server.
Currently there is no concept of a run, and no frontend view to allow for utilising them.
They can currently be accessed in the directory /media/traces/ via HTTP
Merge branch 'master' into recording-traces
Removed trace-test.html

Now that this feature is working properly, the test file is no longer needed.
The URL, view and template have been removed.
Modified the traces view to display traces

At the moment, it's fairly rudimentary. Eventually, I would like to have it sorted by date, and simulation run name.
For now, traces are not associated with a simulation run, so this isn't actually possible.

It might also be nice to have a degree of syntax highlighting in the trace, but this would require the creation of another mode for ace.js.
This is possible, but might be quite hard work.
Merge branch 'master' into recording-traces
Retabbed traces.html

The tabbing was causing problems with my editor...
Improved the interface for the traces. Currently only the frontend

This will allow for the development of the simulation-run aspect, making it easier to view the traces you're interested in.
Traces now largely there

There are a few minor changes that will need to be made. For starters none of the details for the simulation are passed through to the template.
Secondly, there is currently no way of setting the new simulation name.

Thirdly, the delete button isn't associated with a URL and 404s.
The simulation delete button now works

It uses ajax to call the delete method and then reloads the page.
Added the model to main.html that will allow for naming simulations.

Currently it isn't possible to actually save the traces.
Implemented the simulation creation aspect of storing traces.

Traces can now be stored by simulation run. There are some things that could be tidied up, but it will serve for now.
Added links to the traces.html errors

This means that in the event that there are no stored traces, you can still find your way back to the homepage.