Skip to content

OTS v1.7.0

Choose a tag to compare

@averbraeck averbraeck released this 18 Mar 13:02

The following issues have been addressed:

  • Issue #2. Renaming GTU to Gtu in all classes.
  • Issue #3. Simplify Route/CompleteRoute, and delete CompleteRoute.
  • Issue #4. Remove cloning since it is not implemented properly.
  • Issue #5. Remove LongitudinalDirectionality from the code.
  • Issue #6. Simplify and streamline Compatibility. The code has Compatibility and Compatible interfaces. It is not clear what the difference is, since they both have the isCompatible(..) method. The structure has been heavily simplified.
  • Issue #7. Make Sensors a full infrastructure element.
  • Issue #8. Handle DEFAULTS in another way. DefaultsNl now includes default LinkTypes. DefaultsRoadNl contains default LaneTypes. An instance can be reached at DefaultsRoad.NL. DefaultsRoad extends Defaults. Through static methods getByName default types may be found. Defaults has a protected static helper method such that subclasses can easily find fields in their own class.
  • Issue #9. Move route finding methods from Lane to LaneBasedGtu.
  • Issue #10. Remove GTUDirectionality from the code.
  • Issue #11. Rename acronyms to camel case, and in case of class names, to Pascal case.
  • Issue #12. Detector and DetectorType to replace Sensor.
  • Issue #13. LinkType.isConnector() to give false by default.
  • Issue #14. Create NodeType class.
  • Issue #15. Book Gtu on Lane only with reference point.
  • Issue #17. Make class names in comments consistent with refactoring (directionality removed; Xml -> Xml, OTS -> Ots, etc.).
  • Issue #19. Add a HierarchicallyTyped interface.
  • Issue #21. Remove deprecated demo's.
  • Issue #23. repair wrong brake lights equation.
  • Issue #24. Simplifying inheritance structure of Gtu.
  • Issue #25. Simplifying inheritance structure of CrossSectionElement.
  • Issue #26. Imports in XML not parsed.
  • Issue #27. Add marker type to GTU type.
  • Issue #28. Make StripeAnimation.TYPE a property of a Stripe.
  • Issue #29. Conflicts based on null GtuType.
  • Issue #30. LaneBasedGenerator based on null GtuType.
  • Issue #31. Simplify and finish sampler tables.
  • Issue #32. Sampler does not sample a new GTU correctly.
  • Issue #33. Merge ots-kpi and djutils-data table functionality.
  • Issue #34. Lane.ADD_GTU_EVENT lane in payload and event order.
  • Issue #35. Sampler generics types to include LaneData.
  • Issue #36. What to do with the compressedfiles package in ots-base?
  • Issue #37. Self-referring links in manual are broken.
  • Issue #38. Simplifying Sensor class structure and names.
  • Issue #39. A* shortest path algorithm added.
  • Issue #42. LoopDetectors should be able to present themselves as a Table.
  • Issue #43. Visualization of GTU generators and generator functionality.
  • Issue #44. GTU generation from injection files.
  • Issue #45. TrafflicLightDetector operations.
  • Issue #48. Simplifying LaneBasedGtuCharacteristicsGenerator inheritance structure.
  • Issue #49. Change Type from abstract class to interface?
  • Issue #50. Remove package [road].network.factory.xml.demand?
  • Issue #51. Remove source from deprecated event scheduling method calls (DSOL update).
  • Issue #52. Simplify Network/Link/Node inheritance structure.
  • Issue #53. Streamline object.trafficlight and ots-trafficcontrol.
  • Issue #54. Lane nextLanes/prevLanes override.
  • Issue #55. Removal of duplicate resources.
  • Issue #56. Merge ots-xsd project into ots-xml project.
  • Issue #57. Streamline XSD management.
  • Issue #58. Provide GTUs with a flexible String attribute.
  • Issue #60. Exporting SuperDemo as an executable JAR file.