EmbeddedMontiArc issueshttps://git.rwth-aachen.de/groups/monticore/EmbeddedMontiArc/-/issues2019-03-12T12:32:24+01:00https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/hardware_emulator/-/issues/1CI pipeline2019-03-12T12:32:24+01:00Evgeny KusmenkoCI pipelinecreate windows ci pipeline
add tests to pipeline
make sure tests are executed on runnercreate windows ci pipeline
add tests to pipeline
make sure tests are executed on runnerJean MeuriceJean Meuricehttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/15Vergleich der Clustering Algos mit zufälligem Clustering(Monte Carlo)2019-03-12T20:34:42+01:00Alexander David HellwigVergleich der Clustering Algos mit zufälligem Clustering(Monte Carlo)Dinh-An HoDinh-An Ho2019-03-14https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/applications/mnistcalculator/-/issues/1Finalizing project2019-03-13T14:40:12+01:00Evgeny KusmenkoFinalizing projectPlease add a short README.md describing purpose, structure of the project and how to build, execute it.
Please create a pipeline executing these steps, i.e. instead of mvn clean install, just execute something like build.sh, generate.sh ...Please add a short README.md describing purpose, structure of the project and how to build, execute it.
Please create a pipeline executing these steps, i.e. instead of mvn clean install, just execute something like build.sh, generate.sh in the gitlab-ci scriptChristopher Jan-Steffen BrixNils FreyerChristopher Jan-Steffen Brixhttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/11Height data2019-03-25T18:00:42+01:00Evgeny KusmenkoHeight dataCurrently there is no height data in the simulation;
- please investigate sources for height data
- implement height data in the environment
- make sure it is visible in the visualization
The interface of the height provider should be s...Currently there is no height data in the simulation;
- please investigate sources for height data
- implement height data in the environment
- make sure it is visible in the visualization
The interface of the height provider should be similar to the friction providerMichael OsetinskiMichael Osetinski2019-01-30https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/9Camera sensor2019-03-25T18:00:42+01:00Evgeny KusmenkoCamera sensorIn order to make decisions based on what a vehicle sees, we need a simulated camera sensor.
Such a sensor is required to deliver (stylized/abstract) pictures of the environment in front of the car. Such a picture can then be used for CV...In order to make decisions based on what a vehicle sees, we need a simulated camera sensor.
Such a sensor is required to deliver (stylized/abstract) pictures of the environment in front of the car. Such a picture can then be used for CV tasks etc.
Make sure, several cameras can be mounted at different positions on top of the vehicle to obtain a 3D picture in a post-processing step.Yanjiang Heyanjiang.he@rwth-aachen.deYanjiang Heyanjiang.he@rwth-aachen.de2019-01-21https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/8Dynamic friction2019-03-25T18:00:42+01:00Evgeny KusmenkoDynamic frictionA friction coefficient determines several properties of the physical driving behavior. Develop a friction coefficient provider which is used to obtain the friction coefficient for a given position on the map.
Note, that the implementati...A friction coefficient determines several properties of the physical driving behavior. Develop a friction coefficient provider which is used to obtain the friction coefficient for a given position on the map.
Note, that the implementation of a friction provider might differ:
- It might "know" the friction coefficient for different types of surfaces, check the current surface and return the corresponding coefficient.
- It might read the friciton coefficient from a given friction map.Benjamin StutteTheresa TäuberBenjamin Stutte2019-02-13https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/7Environment Enhancement2019-03-25T18:00:43+01:00Evgeny KusmenkoEnvironment EnhancementCurrently, there are only streets and lawns you can see in the visualization. Accrodingly there is nothing in the simulated environment but a street graph and vehicles.
Please extend the environment builder so that it extracts buildings...Currently, there are only streets and lawns you can see in the visualization. Accrodingly there is nothing in the simulated environment but a street graph and vehicles.
Please extend the environment builder so that it extracts buildings , waters, etc. from the OSM provided and instantiate corresponding objects in the simulation. Make sure these objects have an influence on driving, e.g. a vehicle cannot drive through a building.
In a second step it is necessary to extend the visualization so that buildings and waters are rendered as such in the 3D visualization.Florisa MartinsDanilo TrottaFlorisa Martins2019-01-20https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/SimulationLanguage/-/issues/3Refactor ExplicitVehicle2019-03-26T13:46:55+01:00Evgeny KusmenkoRefactor ExplicitVehiclereplace X and Y by latitude and longitude
create nice function calls to access start position and destination positionreplace X and Y by latitude and longitude
create nice function calls to access start position and destination positionHengwen Zhanghengwen.zhang@rwth-aachen.dePascal Maurice PortaHengwen Zhanghengwen.zhang@rwth-aachen.de2019-03-19https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/26Eval: Why do we use the cluster numbers we use(min, max, same as auto?)2019-03-28T18:05:51+01:00Alexander David HellwigEval: Why do we use the cluster numbers we use(min, max, same as auto?)2019-03-14https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/29Use Silhouette index2019-03-28T18:06:02+01:00Alexander David HellwigUse Silhouette indexwith all number of clusters?with all number of clusters?Alexander David HellwigAlexander David Hellwig2019-03-14https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/17Faulty search for minimal value in SplineDeterminator class2019-03-31T20:30:47+02:00Benjamin StutteFaulty search for minimal value in SplineDeterminator classThe method `getMinimumSplineForSetAndPoints` initializes the variable `minDist` with `Double.MAX_VALUE` but its content is never overwritten when a smaller value is found. Consequently, the comparison in [line 188](https://git.rwth-aache...The method `getMinimumSplineForSetAndPoints` initializes the variable `minDist` with `Double.MAX_VALUE` but its content is never overwritten when a smaller value is found. Consequently, the comparison in [line 188](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/geometry/osmadapter/SplineDeterminator.java#L188) evaluates to `true` with every iteration and the method always returns the last element in the given set and not neccessarily the correct one.https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/16Bug in initialization of LinearSplineDeterminator2019-03-31T20:30:54+02:00Benjamin StutteBug in initialization of LinearSplineDeterminatorInside the [initBounds()](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/geometry/osmadapter/LinearSplineDeterminator.java#L66) method we check for...Inside the [initBounds()](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/geometry/osmadapter/LinearSplineDeterminator.java#L66) method we check for a `y` but assign an `x`-coordinate.https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/14Possible typo in doCalculationStep method of ModelicaPhysicalVehicle2019-03-31T20:31:11+02:00Benjamin StuttePossible typo in doCalculationStep method of ModelicaPhysicalVehicleShouldn't [this line](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/vehicle/src/main/java/simulation/vehicle/ModelicaPhysicalVehicle.java#L568) be
`double brakeAcceleration4 = simulationVehicle....Shouldn't [this line](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/vehicle/src/main/java/simulation/vehicle/ModelicaPhysicalVehicle.java#L568) be
`double brakeAcceleration4 = simulationVehicle.getVehicleActuator(VEHICLE_ACTUATOR_TYPE_BRAKES_BACK_RIGHT).getActuatorValueCurrent();`?https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/30MonteCarlo plot starts at 0 instead of 12019-04-01T15:06:51+02:00Alexander David HellwigMonteCarlo plot starts at 0 instead of 1https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/15WorldModel.java: possibly several bugs in methods used to access wheel positions2019-04-08T10:44:32+02:00Benjamin StutteWorldModel.java: possibly several bugs in methods used to access wheel positionsBoth [`getDistanceLeftFrontToStreetBorder`](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/WorldModel.java#L349) and [`getDistanceRightFrontToStree...Both [`getDistanceLeftFrontToStreetBorder`](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/WorldModel.java#L349) and [`getDistanceRightFrontToStreetBorder`](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/WorldModel.java#L359) call `getBackLeftWheelGeometryPosition()` to determine the wheel position while it should be `getFrontLeftWheelGeometryPosition()` and `getFrontRightWheelGeometryPosition()` respectively.
Furthermore, the methods [`getDistanceFrontRightWheelToRightStreetBorder`](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/WorldModel.java#L377) [`getDistanceBackRightWheelToRightStreetBorder`](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/blob/master/environment/src/main/java/simulation/environment/WorldModel.java#L387) return `minStreet.getDistanceToLeft` while it seems like it should be `minStreet.getDistanceToRight`.https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/visualization/-/issues/4Buildings on Streets2019-04-08T17:36:53+02:00Danilo Lourenco TrottaBuildings on StreetsBuildings are parsed from OSM files and placed corresponding to these coordiantes.
But still in certain Maps some buildings are placed completly or halfway on the street.Buildings are parsed from OSM files and placed corresponding to these coordiantes.
But still in certain Maps some buildings are placed completly or halfway on the street.https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/visualization/-/issues/3Houses, Waters, etc.2019-04-08T17:36:53+02:00Evgeny KusmenkoHouses, Waters, etc.Extend the visualization such that it can visualize houses, waters, and possibly other objects or variants of objects (e.g. different kinds of streets)Extend the visualization such that it can visualize houses, waters, and possibly other objects or variants of objects (e.g. different kinds of streets)Danilo TrottaDanilo Trotta2019-01-21https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/31Split clustering code into own project2019-04-10T09:42:00+02:00Alexander David HellwigSplit clustering code into own projectAlexander David HellwigAlexander David Hellwighttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Cpp/-/issues/28Add automatic test execution for cmake build script2019-04-11T18:49:39+02:00Alexander David HellwigAdd automatic test execution for cmake build scriptBasic idea:
Add to CMakeLists.txt
add_custom_target(run_${component.name}_StreamTests ALL
COMMAND ${component.name}_StreamTests
WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
)Basic idea:
Add to CMakeLists.txt
add_custom_target(run_${component.name}_StreamTests ALL
COMMAND ${component.name}_StreamTests
WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
)Alexander David HellwigAlexander David Hellwighttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/21ROS2: Message -> C++ generation2019-05-05T11:16:17+02:00Alexander David HellwigROS2: Message -> C++ generation.h files generated from .msg files can lead to compilation errors..h files generated from .msg files can lead to compilation errors.Alexander David HellwigAlexander David Hellwig