data_generator and Simlated Dataset Manager -
    Updated to allow for user inputted velocity

    Deleted redundant code in request part of SDM
    (code extraneously copied value to msg sent out)

   In find_measurent(), updated to differentiate
   landmark over relative observations ( & prefer)

   Need to figure out what's wrong with velocity
   Then, need to test communication

time index even when no measurement available at a particular time

Replaced hard-coded assumption with
find_nearest_time_idx()

Updated journal 2 sim parameters
Still debugging!

realtime plot merge

Currently testing communication

added relative observations
added testing for relative observations

TODO - multiple robots (modify datastructures), math
stays the same
Tested on both simulated and real-world data, works in both cases

Small tweaks in parameter passing in simulated dm

(only had to modify generation of groundtruths)
changed initial starting states of robots in dm
added some basic path plotting code to test_simulation

Added a data-generator class to
generate data for simulated_dataset-manager

- internal robot_ctr that resets correctly
Order is (assuming 2 robots):
1: odo, meas
2: odo, meas
1: odo, meas
...

used when no measurement available for a given time

simulation now supports multiple landmarks
added handling for no measurement data
available at a given time (sim not over)

-working on incorporating multiple landmarks
-working on incorporating multiple robots
-working on handling of end of simulation vs. no meas. data available

Added custom noises to simulated_dataset_manager.py
Thorough review of simulated_dataset_manager reveals that it works correctly!
fixed delta_t with regards to alternation between measurement and odometry updates -> scheduling of this will change in next commit
will add multiple robots

Refactored some more elements of the code to be interchangable. Currently debugging communications of request/response messages.

1st iteration, next step is to add dynamic generation.