EmbeddedMontiArc issueshttps://git.rwth-aachen.de/groups/monticore/EmbeddedMontiArc/-/issues2021-10-24T16:00:12+02:00https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/36Descriptive Task results2021-10-24T16:00:12+02:00Jean MeuriceDescriptive Task resultsRight now, simulations only return `SUCCESS` or `FAILURE`. While the reason for failure can be better seen when using a GUI (like in the basic-simulator), this makes it hard to understand problems in a CI/CLI setting.
## Task
- Return ...Right now, simulations only return `SUCCESS` or `FAILURE`. While the reason for failure can be better seen when using a GUI (like in the basic-simulator), this makes it hard to understand problems in a CI/CLI setting.
## Task
- Return descriptive reasons when `Tasks` fail. (Ex: "Collided with ...", "Timeout", ...)https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/applications/mnistcalculator/-/issues/18Design a streamtest template for MNISTCalculator2022-07-25T17:10:09+02:00Yuyuan LiuDesign a streamtest template for MNISTCalculatorTo implement:
- A generator for EMADL `streamtest` in `EMADL-Generator`
- (If necessary) An Expansion of grammar in `languagecommon` project.To implement:
- A generator for EMADL `streamtest` in `EMADL-Generator`
- (If necessary) An Expansion of grammar in `languagecommon` project.Yuyuan LiuYuyuan Liuhttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/33Detailed Road Geometry2021-10-20T18:44:21+02:00Jean MeuriceDetailed Road Geometry## Idea
Bring back the "detailed" road geometry: curves for the boundaries, lanes, proper intersection geometry, side-walks, traffic signs, ...
## Tasks
- Generate proper geometry from the abstract OSM road information
- Handle adja...## Idea
Bring back the "detailed" road geometry: curves for the boundaries, lanes, proper intersection geometry, side-walks, traffic signs, ...
## Tasks
- Generate proper geometry from the abstract OSM road information
- Handle adjacent road segments, handle intersections
- Handle number of lanes, transitions from different lane numbers, ...
- Register individual geometry-chunks as "static-objects" in the simulator
- Handle the collision response in the vehicle
- Add "stay on road" checks, ...
- Add proper rigidbody physics for the road-vehicle interactions
- Road markings ("vectorial"/spline representation) + type
- Sidewalks
- Traffic signs, lights, ...
## Notes
- Some old code that did this can be found in `simulation/old-code/environment`.
- *If old code is adapted, it should use the proper [Vector Math](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/wikis/dev-docs/commons/Vectors,-Matrices-and-Math)*
- This can be built up progressively:
- Generate simple rectangular chunks for the road
- Test the junction between segments
- Test detecting overlaps
- Intersections: simple polygons
- More detailed road geometry
- ...https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Middleware/-/issues/24Different values of heuristic for same (max) number of clusters2019-03-11T14:58:36+01:00Alexander David HellwigDifferent values of heuristic for same (max) number of clustersAlexander David HellwigAlexander David Hellwighttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/MathPrettyPrinter/-/issues/3Dimension-Checking2018-12-07T23:43:45+01:00vonWencksternDimension-Checking![image](/uploads/b8c03a75a7f974c72579e47777c6259a/image.png)
das Bild zeigt Variable c mit 1 Zeile und 5 Spalten; aber der Wert der zugewiesen wird hat nur 3 Spalten und 1 Zeile.
Damit ist das Beispiel ja falsch; bitte baut dafür bitte...![image](/uploads/b8c03a75a7f974c72579e47777c6259a/image.png)
das Bild zeigt Variable c mit 1 Zeile und 5 Spalten; aber der Wert der zugewiesen wird hat nur 3 Spalten und 1 Zeile.
Damit ist das Beispiel ja falsch; bitte baut dafür bitte einen entsprechenden CoCo-Check ein.
Und in der HTML-Ausgabe, könnt ihr ja ein rotes Fehlerkreuz vor der Zeilennummer generieren; für das Beispiel damit es anzeigt, dass irgendetwas nicht stimmt.
@jean\-marc.ronck, @armin.mokhtarian, @bram.kohlen: Dies bitte fixen.https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMADL2CPP/-/issues/110Documentation of AutoML techniques2023-06-07T18:30:30+02:00aixaiDocumentation of AutoML techniquesExtend the Readme of EMADL2CPP.
Copy AutoML explainations from our thesisExtend the Readme of EMADL2CPP.
Copy AutoML explainations from our thesisTobias HörnschemeyerNazish QamarHiroshi HamanoAkashKumarDSTobias Hörnschemeyerhttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/21Docu TODO2021-10-24T17:07:31+02:00Hengwen Zhanghengwen.zhang@rwth-aachen.deDocu TODO## User-docs
- [ ] "Autopilot configuration": What to specify ? Quick overview of compiling/running EMA-based autopilots ?
- [ ] SimLang/CarLang/MontiCore links in "Introduction to MontiSim"
- [ ] basic-sim "link to maven tutorial"
## ...## User-docs
- [ ] "Autopilot configuration": What to specify ? Quick overview of compiling/running EMA-based autopilots ?
- [ ] SimLang/CarLang/MontiCore links in "Introduction to MontiSim"
- [ ] basic-sim "link to maven tutorial"
## Dev-docs
- Intro
- [ ] "Intro" text?
- [ ] Overview of next sections & pages
- Simulation
- [ ] Properties: registering the classes (+link to JSON system?)
- [ ] Simulation Methods -> TODOs in wiki page
- [ ] Simulator class and simulation data
- EE-System
- [ ] EE System -> TODOs in wiki page
- [ ] Various EEComponents: explanation of their inner workings
- [ ] EEComponents Development: "How to create an EEComponent sub-class"
- [ ] EE Message reference: which component sends which message and with what type
- World & Geometry
- [ ] OSM loading
- Vehicles
- [ ] Vehicles overview
- [ ] Tasks
- [ ] PhysicalValues
- [ ] PowerTrain
- [ ] Collision: Vehicle objects and hitboxes somewhere?
- [ ] Rigidbody physics
- Visualizations
- [ ] basic-simulator
- [ ] debug-viewer classes (Viewer2D, PhysicsDebug, ...)
- General/Commons
- [ ] Commons Overview
- [ ] Describe "polygon-convexer" ?
- [ ] JSON-Serializer
## Other
- [ ] Move & update documentation in 'hardware_emulator/readme.md'
- [ ] In the `simulation.wiki` repository, there are a bunch of old documentation files under `TO_SORT`. These have to be integrated in the new documentation (or simply deleted).
- [ ] Add in Code: Link to relevant docu pageshttps://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/server/-/issues/5Dynamic Sectoring before simulation2019-10-09T10:53:01+02:00Evgeny KusmenkoDynamic Sectoring before simulationIt should be possible to set the number of sectors WITHOUT having to reparse a mapIt should be possible to set the number of sectors WITHOUT having to reparse a mapHengwen Zhanghengwen.zhang@rwth-aachen.deHengwen Zhanghengwen.zhang@rwth-aachen.dehttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/issues/27Efficient Lidar Lookup / Lidar updates2021-10-20T18:57:18+02:00Jean MeuriceEfficient Lidar Lookup / Lidar updatesRight now the `Lidar` ee-component logic is highly inefficient: it iterates over all the edges of all the buildings in the map *per lidar trace* (8 per vehicle).
It also accesses the vehicle position in a conceptually wrong way.
Its mat...Right now the `Lidar` ee-component logic is highly inefficient: it iterates over all the edges of all the buildings in the map *per lidar trace* (8 per vehicle).
It also accesses the vehicle position in a conceptually wrong way.
Its math can also be improved.
## Spatial Acceleration
Use the grid acceleration structure in `CollisionDetection` and traverse it (up to a max distance) starting from the lidar "ray" origin. Then check the buildings referenced in the grid cell.
- Make `CollisionDetection` available in the [BuildContext](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/wikis/dev-docs/simulation/Initialization-Overview#build-context) for the ee-components.
- Implement a cell traversal + have a hash-set to remove duplicate checks on buildings (a single building can be linked in multiple overlapping cells)
- [Reference for implementation](https://www.scratchapixel.com/lessons/advanced-rendering/introduction-acceleration-structure/grid)
- Choose a sensible max distance for the lidar check after which the grid traversal is stopped.
## Accessing the position
Right now, the Lidar component listens for `true_position` messages. Such messages are intended as "measured position" for use by components that would actually need to get an estimate of the position in a real vehicle. (Such as the Navigation component).
The physics of the Lidar are not dependent on a measured position: they happen in the real world. The Lidar should thus use the position of the dynamic_object of the vehicle.
On the other hand, the distance measured by the lidar could be modeled as imprecise, for example introduction noise.
## Bonus Tasks: Clearer lidar math
- [IPM](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/simulation/-/wikis/dev-docs/commons/Vectors,-Matrices-and-Math#in-place-math-ipm) for the math: store the vectors in the Lidar object and re-use them using IPM functions.
- Vehicle "model matrix":
- The lidar "rays" (position and direction vectors) can be defined in the local vehicle space once.
- When computing/updating, generate one rotation/translation matrix (in extended coordinate space) for the vehicle
- Use this matrix in the `computeShortestDistance()` function to get the lidar ray position and direction in world space
- Overall edge/ray intersection math can be revisited (use simple dot products, edge "normals", ...) + **check if the intersection is "in front" of the ray** (does not seem to be the case/to be verified).https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/languages/EmbeddedMontiArcDL/-/issues/1Einbindung von EMAMOpt statt EMAM2018-10-26T15:02:11+02:00Evgeny KusmenkoEinbindung von EMAMOpt statt EMAMIm Moment benutzt die Sprache Regeln aus EMAM/MontiMath
Damit wir die Arbeit von @christoph.richter hier wiederverwenden können, müsste die Sprache auf MontiMathOpt und EmbeddedMontiMathOpt umgestellt werden.Im Moment benutzt die Sprache Regeln aus EMAM/MontiMath
Damit wir die Arbeit von @christoph.richter hier wiederverwenden können, müsste die Sprache auf MontiMathOpt und EmbeddedMontiMathOpt umgestellt werden.Svetlana PavlitskayaSvetlana Pavlitskaya2018-08-23https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/EMAM2Cpp/-/issues/13Element-wise multiplication does not generate correct armadillo code!2018-07-18T17:56:53+02:00Christoph RichterElement-wise multiplication does not generate correct armadillo code!Math statements:
```
Q^{2,2} A = [1,1;1,1];
Q^{2,2} B = [1,2;3,4];
Q^{2,2} C = A .* B;
```
produce wrong armadillo C++ code:
`mat C = A .* B;`
Armadillo uses % for element wise multiplication.Math statements:
```
Q^{2,2} A = [1,1;1,1];
Q^{2,2} B = [1,2;3,4];
Q^{2,2} C = A .* B;
```
produce wrong armadillo C++ code:
`mat C = A .* B;`
Armadillo uses % for element wise multiplication.Christoph RichterChristoph Richterhttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/utilities/monticore-vscode-commons/-/issues/1Enable auto publish to gitlab npm repository2023-06-25T14:22:08+02:00Alexander David HellwigEnable auto publish to gitlab npm repositoryAlexander David HellwigAlexander David Hellwig2019-12-01https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/emam2someip/-/issues/11Enable multiple callbacks in one adapter2019-07-12T11:48:55+02:00Alexander David HellwigEnable multiple callbacks in one adapterIdea: Encapsulate callback in Class:
Create Class with callback and add pointer to component in constructor. Create an object of this class in the init method of the adapter and register with middleware
If you can think of other alternat...Idea: Encapsulate callback in Class:
Create Class with callback and add pointer to component in constructor. Create an object of this class in the init method of the adapter and register with middleware
If you can think of other alternatives, feel free to implement them insteadMarkus Georg BendelMarkus Georg Bendelhttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/generators/emam2mqtt/-/issues/11Enable multiple callbacks in one adapter2019-06-17T19:14:03+02:00Alexander David HellwigEnable multiple callbacks in one adapterIdea: Encapsulate callback in Class:
Create Class with callback and add pointer to component in constructor. Create an object of this class in the init method of the adapter and register with middleware
If you can think of other alternat...Idea: Encapsulate callback in Class:
Create Class with callback and add pointer to component in constructor. Create an object of this class in the init method of the adapter and register with middleware
If you can think of other alternatives, feel free to implement them insteadGeorg VinogradovGeorg Vinogradovhttps://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/RMIModelServer/-/issues/5[ERR] Could not open DLL/ Could not open SO2019-11-11T16:40:48+01:00Sabrina Wolff[ERR] Could not open DLL/ Could not open SOWhen starting a simulation, an error in the RMIServer occured: "[ERR] Could not open DLL: path\to\RMIModelServer\install\autopilot\AutoPilotAdapter\AutopilotAdapter.dll" or "[ERR] Could not open SO: path\to\RMIModelServer\install\autopil...When starting a simulation, an error in the RMIServer occured: "[ERR] Could not open DLL: path\to\RMIModelServer\install\autopilot\AutoPilotAdapter\AutopilotAdapter.dll" or "[ERR] Could not open SO: path\to\RMIModelServer\install\autopilot\AutoPilotAdapter\AutopilotAdapter.so". The Server wants to open the AutopilotAdapter.so and AutopilotAdapter.dll files located in the "AutopilotAdapter" folder but this folder does not exist. The files are placed in the "autopilot" folder. So to fix it, you just need to create a folder named "AutopilotAdapter" in "autopilot" and place both files into it.
![Unbenajjnnt](/uploads/c3b7888a4fa598a20bd20824b8e26d1e/Unbenajjnnt.jpg)
![Unbenkkklannjjjt](/uploads/c101a42422363c24c6303c224cabdac3/Unbenkkklannjjjt.jpg)Evgeny KusmenkoEvgeny Kusmenkohttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/server/-/issues/26Error when Pushing: "... not allowed to push code to protected branches on th...2019-10-09T10:52:05+02:00ulfetError when Pushing: "... not allowed to push code to protected branches on this project"I created a subproject on Maven, and added my code, as we talked with Mr. Kusmenko.
However, when I try to push, I get the following errors:
`remote: GitLab: You are not allowed to push code to protected branches on this project.`
Norm...I created a subproject on Maven, and added my code, as we talked with Mr. Kusmenko.
However, when I try to push, I get the following errors:
`remote: GitLab: You are not allowed to push code to protected branches on this project.`
Normally, I would have created another branch and would push there, but as far as I remember, this is not what I told by Kusmenko.
For a temporary fix,
I am temporarily creating a branch for BatteryInterface group and I will push my code there.Evgeny KusmenkoulfetEvgeny Kusmenkohttps://git.rwth-aachen.de/monticore/EmbeddedMontiArc/applications/reinforcement_learning/forestrl/-/issues/4Evaluation des Agenten2020-08-21T11:36:04+02:00Evgeny KusmenkoEvaluation des AgentenEs soll geprüft werden, wie gut die Entscheidungen des Agenten sind. Dazu sind folgende Ansätze angedacht:
* Vergleich mit Random-Algorithmus
* Vergleich mit Regelbasierten Ansätzen
* Greedy
* ggf. weitereEs soll geprüft werden, wie gut die Entscheidungen des Agenten sind. Dazu sind folgende Ansätze angedacht:
* Vergleich mit Random-Algorithmus
* Vergleich mit Regelbasierten Ansätzen
* Greedy
* ggf. weitereSascha DewesSascha Deweshttps://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-14