ACS issueshttps://git.rwth-aachen.de/groups/acs/-/issues2023-12-15T11:17:46+01:00https://git.rwth-aachen.de/acs/public/teaching/legos/hardware/-/issues/5Add JTAG to the PCBs2023-12-15T11:17:46+01:00Jonathan KlimtAdd JTAG to the PCBsDebugging would be kind of nice
* [x] Data Center
* [x] EC Station
* [ ] Factory
* [x] Hospital
* [ ] House
* [x] Power Plant
* [ ] Skyscraper
* [x] Solar Farm
* [ ] Stadium
* [ ] Substation
* [ ] Supermarket
* [x] Wind Farm
* [ ] Branc...Debugging would be kind of nice
* [x] Data Center
* [x] EC Station
* [ ] Factory
* [x] Hospital
* [ ] House
* [x] Power Plant
* [ ] Skyscraper
* [x] Solar Farm
* [ ] Stadium
* [ ] Substation
* [ ] Supermarket
* [x] Wind Farm
* [ ] Branch (?)
In case of the Power Plant, where the JTAG Pins are already used for Touch Sensing, a Jumper has been added to switch between JTAG or Touch.https://git.rwth-aachen.de/acs/public/teaching/legos/firmware/-/issues/8Audio output for Stadium2022-07-05T16:33:42+02:00Jonathan KlimtAudio output for Stadiumhttps://git.rwth-aachen.de/acs/public/teaching/legos/firmware/-/issues/5PWM Functions into legos common2022-07-15T11:02:30+02:00Jonathan KlimtPWM Functions into legos common- `init_pwm`
- `init_tasks_timer`- `init_pwm`
- `init_tasks_timer`https://git.rwth-aachen.de/acs/public/teaching/legos/firmware/-/issues/4MQTT Topics as part of KConfig2022-07-05T16:27:05+02:00Jonathan KlimtMQTT Topics as part of KConfighttps://git.rwth-aachen.de/acs/public/teaching/legos/hardware/-/issues/2adopt pcbs with many leds to the pca9956 led driver2023-12-15T12:00:23+01:00Matthias Marcus Nowakadopt pcbs with many leds to the pca9956 led driver- [x] Datacenter
- [x] House
- [ ] Factory
- [x] Powerplant
- [x] Branch
- [ ] Skyscraper- [x] Datacenter
- [x] House
- [ ] Factory
- [x] Powerplant
- [x] Branch
- [ ] Skyscraperhttps://git.rwth-aachen.de/acs/public/automation/double-virtualization/distributed-dvam/-/issues/2flows.json2022-07-05T11:02:41+02:00Nikolaus Wirtzflows.jsonflows.json not completely cleaned up
- dv am contains comment nod- e "TODO ?" and nodes debug / log to raspi 4
- data contains a debug node that can be removed
- dv asset
- contains a debug node that can be removed
- path of the...flows.json not completely cleaned up
- dv am contains comment nod- e "TODO ?" and nodes debug / log to raspi 4
- data contains a debug node that can be removed
- dv asset
- contains a debug node that can be removed
- path of the functions need to be updated (should be home\pi\distributed-dvam\functions\ABC, I think)
- Flow 1 can be removed
- all debug nodes after "take time" nodes can be switched offLukas LenzLukas Lenzhttps://git.rwth-aachen.de/acs/public/automation/double-virtualization/distributed-dvam/-/issues/1Documentation2022-07-05T10:31:44+02:00Nikolaus WirtzDocumentationhostnames need to be replaced by dummy hostnames before making repo public
command to generate flows.json files is not correct, should be
`python pi-setup-code.py flows.json`
instead of
`pi pi-setup-code.py flows.json`
python needs to ...hostnames need to be replaced by dummy hostnames before making repo public
command to generate flows.json files is not correct, should be
`python pi-setup-code.py flows.json`
instead of
`pi pi-setup-code.py flows.json`
python needs to be installed (not listed in requirements)
several warnings appear when running
sh pi-setup.sh
![grafik](/uploads/0c03dc735cc6855b022e39c38f23beb2/grafik.png)Lukas LenzLukas Lenzhttps://git.rwth-aachen.de/acs/public/virtualization/rpc-lib/rpc-lib/-/issues/4Consider rewriting with serde2022-07-01T14:12:20+02:00Martin Kröningmartin.kroening@eonerc.rwth-aachen.deConsider rewriting with serdehttps://git.rwth-aachen.de/acs/public/simulation/DistAIXFramework/distaix/-/issues/15Use C++ interface of VILLASnode2022-06-01T15:49:52+02:00Sonja HappUse C++ interface of VILLASnodeWe should switch to the C++ interface of VILLASnode in the `VILLASinterface` class to be compatible with the latest and coming versions of VILLASnode. This entails significant changes in the `VILLASinterface` class.
First and foremost, ...We should switch to the C++ interface of VILLASnode in the `VILLASinterface` class to be compatible with the latest and coming versions of VILLASnode. This entails significant changes in the `VILLASinterface` class.
First and foremost, we have use the "parse" functions of VILLASnode to set the config params of each node. Until now, we access and set these params manually. This is no longer possible because now they are "hidden" behind protected or private members of the VILLASnode `Node` class.
I suggest to move the configuration params for the `VILLASinterface` from the model.props to a separate json file (and specify the json file as config property in the model.props) so that the format of the config is similar to that of VILLASnode. We can read the json file in each process and hand the contents as `json_t` (using libjansson) to the VILLASinterface class.
This approach has one disadvantage: We would need to configure the signals (signal names, types, units) in the json file as well because they have to be known for the parsing process. This collides with the current approach of the `VILLASmessage` class that is used to derive and define a specific message format for an agent behavior and to facilitate the actual transfer of data between VILLASnode and DistAIX. We need to rethink this approach in order to avoid duplication of code and signal definitions.
If have started the work here 390dab5d.
Comments are welcome @felix.wegehttps://git.rwth-aachen.de/acs/public/simulation/DistAIXFramework/distaix/-/issues/14Allow configuration of simulation start time in model.props file2022-04-25T15:57:26+02:00Sonja HappAllow configuration of simulation start time in model.props fileSee !11See !11Felix WegeFelix Wegehttps://git.rwth-aachen.de/acs/public/simulation/DistAIXFramework/distaixweb/-/issues/2Create helm chart for DistAIXweb2022-03-30T15:15:36+02:00Sonja HappCreate helm chart for DistAIXwebFor easy deployment in Kubernetes, a Helm chart for DistAIXweb would be useful.
This should deploy
- Frontend
- Backend
- Ingress
- ConfigMap for Backend
As a basis, example yaml configuration files for k8s are available in the folder ...For easy deployment in Kubernetes, a Helm chart for DistAIXweb would be useful.
This should deploy
- Frontend
- Backend
- Ingress
- ConfigMap for Backend
As a basis, example yaml configuration files for k8s are available in the folder k8s.
The Helm chart can be added to the [ACS Catalogue repository](https://git.rwth-aachen.de/acs/public/catalogue)https://git.rwth-aachen.de/acs/public/deliverables/interflex/flexibilityplatform/backend/-/issues/1Inactivity limit exceeded2023-06-24T13:29:49+02:00Stefan Lankesslankes@eonerc.rwth-aachen.deInactivity limit exceededCan I archive this project?Can I archive this project?https://git.rwth-aachen.de/acs/public/deliverables/interflex/flexibilityplatform/d35/-/issues/1Inactivity limit exceeded2021-12-15T08:05:45+01:00Stefan Lankesslankes@eonerc.rwth-aachen.deInactivity limit exceededCan I archive this project?Can I archive this project?https://git.rwth-aachen.de/acs/public/deliverables/interflex/flexibilityplatform/api/-/issues/1Inactivity limit exceeded2021-12-15T08:04:57+01:00Stefan Lankesslankes@eonerc.rwth-aachen.deInactivity limit exceededCan I archive this project?Can I archive this project?https://git.rwth-aachen.de/acs/public/deliverables/sogno/load-prediction-service/-/issues/1inactivity limit exceeded2021-11-11T11:57:36+01:00Stefan Lankesslankes@eonerc.rwth-aachen.deinactivity limit exceededDo we need this repository or should we archive it (see below).
> Dear GitLab users,
>
> As owners of the group project "acs/public/deliverables/sogno/load-prediction-service" with the ID 35745 (https://git.rwth-aachen.de/acs/public/de...Do we need this repository or should we archive it (see below).
> Dear GitLab users,
>
> As owners of the group project "acs/public/deliverables/sogno/load-prediction-service" with the ID 35745 (https://git.rwth-aachen.de/acs/public/deliverables/sogno/load-prediction-service), we would like to inform you that your project has been marked as inactive according to the GitLab terms of use (https://git.rwth-aachen.de/-/users/terms).
> If you are not a direct owner of the group project, you are being notified as well due to the permission inheritance in GitLab.
>
> The last project activity was on November 08, 2019, thus exceeding the inactivity limit of 24 months.
>
> For projects that are no longer actively maintained but still require read-only access we would like to inform you about GitLab’s archiving feature. Archiving a project automatically excludes it from the project lifecycle.
> A more detailed documentation on this feature can be found on IT Center Help:
> https://help.itc.rwth-aachen.de/service/ubrf9cmzd17m/article/c64a3b17dfaf457ca0911d57e3a92b2f/
>
> If you want to keep the project for other reasons, you can simply perform a new activity on your project within the next 25 weeks. This will automatically mark your project as active.
> Possible activities such as commits, issues, comments, milestones, wikis or membership changes can be found in the project overview in GitLab in the activity section.
>
> In case you are unable to make a change to your project in GitLab, you can alternatively request a 12-month extension of your project via e-mail to servicedesk@itc.rwth-aachen.de.
> In order for your extension request to be processed correctly, please include the project’s ID and name as well as the corresponding GitLab instance (git.rwth-aachen.de / git-ce.rwth-aachen.de) in your request. You can find the project ID at the beginning of this email and in the project overview in GitLab under the project name.
>
> If we cannot detect any changes to your project or archiving of the project and no request for extension is received, the project will be automatically deleted on May 04, 2022.
> After the project is deleted, a project export is available to all project owners for 4 weeks via a randomly generated download link.
>
> You will receive two more reminders before the project is deleted.
>
> Feel free to contact us again for further support.
>
> Kind regards,
> Your IT Centerhttps://git.rwth-aachen.de/acs/public/hermit-os/hermit-docker/-/issues/1[Project-LifeCycle git.rwth-aachen.de] - Inaktivitätslimit überschritten / in...2021-10-19T19:08:30+02:00Nicolas Berr[Project-LifeCycle git.rwth-aachen.de] - Inaktivitätslimit überschritten / inactivity limit exceededSehr geehrte Nutzende von GitLab,
als Inhabende des Gruppenprojekts "acs/public/hermitcore/hermit-docker" mit der ID 31645 (https://git.rwth-aachen.de/acs/public/hermitcore/hermit-docker) möchten wir Sie darüber informieren, dass Ihr Pr...Sehr geehrte Nutzende von GitLab,
als Inhabende des Gruppenprojekts "acs/public/hermitcore/hermit-docker" mit der ID 31645 (https://git.rwth-aachen.de/acs/public/hermitcore/hermit-docker) möchten wir Sie darüber informieren, dass Ihr Projekt gemäß den GitLab-Nutzungsbedingungen (https://git.rwth-aachen.de/-/users/terms) als inaktiv gekennzeichnet wurde.
Sollten Sie nicht direkte Inhabende des Gruppenprojekts sein, werden Sie hiermit aufgrund der Rechtevererbung in GitLab ebenfalls informiert.
Die letzte Aktivität innerhalb des Projekts konnten wir am 20.10.2019 feststellen. Damit wird das Inaktivitätslimit von 24 Monaten überschritten.
Für bereits abgeschlossene Projekte, die nicht mehr aktiv weiterentwickelt werden und noch lesend zur Verfügung stehen sollen, möchten wir Sie auf das Archivierungsfeature von GitLab hinweisen. Die Archivierung eines Projektes führt automatisch dazu, dass dieses vom Projekt-LifeCycle ausgeschlossen wird.
Eine detaillierte Dokumentation zu dem Archivierungs-Feature finden Sie auf IT Center Help:
https://help.itc.rwth-aachen.de/service/ubrf9cmzd17m/article/c64a3b17dfaf457ca0911d57e3a92b2f/
Sollten Sie das Projekt aus anderen Gründen weiterhin vorhalten wollen, können Sie innerhalb der nächsten 25 Wochen ganz einfach eine neue Aktivität an Ihrem Projekt tätigen. Dadurch wird die Kennzeichnung Ihres Projekts automatisch wieder aufgehoben.
Alle in Ihrem Projekt getätigten Aktivitäten, wie Commits, Issues, Kommentare, Milestones, Wikis oder Mitgliedschaftsänderungen finden Sie in der Projektübersicht in GitLab unter dem Punkt Activity.
Ist es Ihnen nicht möglich eine Änderung am Projekt in GitLab vorzunehmen, können Sie alternativ auch eine Verlängerung Ihres Projekts um 12 Monate per E-Mail an servicedesk@itc.rwth-aachen.de beantragen.
Damit Ihr Verlängerungsantrag korrekt zugeordnet werden kann, geben Sie bitte die ID und den Namen Ihres Projekts sowie die zugehörige GitLab Instanz (git.rwth-aachen.de / git-ce.rwth-aachen.de) im Antrag mit an. Die Projekt ID finden Sie am Anfang dieser E-Mail sowie in der Projektübersicht in GitLab unter dem Projektnamen.
Sofern wir keine neue Aktivität am Projekt oder Archivierung des Projekts feststellen können, und auch kein Antrag auf Verlängerung eingeht, wird das Projekt am 12.04.2022 automatisch gelöscht.
Nach der Löschung des Projekts steht allen Projektinhabenden für 4 Wochen ein Projekt-Export über einen zufällig generierten Downloadlink zur Verfügung.
Sie erhalten noch zwei weitere Erinnerungsmails vor der Löschung des Projekts.
Bei Rückfragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen
Ihr IT Centerhttps://git.rwth-aachen.de/acs/public/cloud/mas/clonemapy/-/issues/5Don't call logging.basicConfig2021-08-18T15:32:29+02:00Fabian WüllhorstDon't call logging.basicConfigIn the agency you call the basicConfig of the logging module:
This does not include the names of the modules.
Can we either update the name using `'%(asctime)s - %(name) - [%(levelname)s] - %(message)s'` or don't call the basicConfig i...In the agency you call the basicConfig of the logging module:
This does not include the names of the modules.
Can we either update the name using `'%(asctime)s - %(name) - [%(levelname)s] - %(message)s'` or don't call the basicConfig in here and set it in the agentlib instead?
```python
try:
log_type = os.environ['CLONEMAP_LOG_LEVEL']
if log_type == "info":
logging.basicConfig(format='%(asctime)s - [%(levelname)s] - %(message)s',
level=logging.INFO)
else:
logging.basicConfig(format='%(asctime)s - [%(levelname)s] - %(message)s',
level=logging.ERROR)
except KeyError:
logging.basicConfig(format='%(asctime)s - [%(levelname)s] - %(message)s',
level=logging.ERROR)
```https://git.rwth-aachen.de/acs/public/simulation/DistAIXFramework/distaix/-/issues/11CI: Create unit tests for VILLASnode interface2022-06-01T14:41:45+02:00Sonja HappCI: Create unit tests for VILLASnode interfaceWe should come up with some simple unit tests for the VILLASinterface class for the supported node types mqtt and nanomessage to ease the debugging.
For example, a ping pong between two agents could work to test basic functionality.We should come up with some simple unit tests for the VILLASinterface class for the supported node types mqtt and nanomessage to ease the debugging.
For example, a ping pong between two agents could work to test basic functionality.https://git.rwth-aachen.de/acs/public/simulation/powersystemsimulation.jl/-/issues/1Remove `Plots` from package deps2021-06-28T17:11:18+02:00Felix WegeRemove `Plots` from package depsFor convenient use in examples, `Plots` is added as package dependency. Remove asap if possible!For convenient use in examples, `Plots` is added as package dependency. Remove asap if possible!Felix WegeFelix Wegehttps://git.rwth-aachen.de/acs/public/exam-tools/exam_scan_manager/-/issues/23Highlight duplicate matr. nrs.2022-08-17T13:33:50+02:00Jonathan KlimtHighlight duplicate matr. nrs.