ACS issueshttps://git.rwth-aachen.de/groups/acs/-/issues2022-04-25T15:57:26+02:00https://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/publications/cricket-hermit/-/issues/9eval: set up VM again2023-07-12T13:22:42+02:00Niklas Eilingniklas.eiling@eonerc.rwth-aachen.deeval: set up VM againhttps://hedgedoc.k8s.eonerc.rwth-aachen.de/4cOjZ0UZQ2KW2RSgpFMr5A?both#https://hedgedoc.k8s.eonerc.rwth-aachen.de/4cOjZ0UZQ2KW2RSgpFMr5A?both#Niklas Eilingniklas.eiling@eonerc.rwth-aachen.deNiklas Eilingniklas.eiling@eonerc.rwth-aachen.dehttps://git.rwth-aachen.de/acs/public/publications/cricket-hermit/-/issues/15improve hermit network performance2023-07-25T12:02:39+02:00Niklas Eilingniklas.eiling@eonerc.rwth-aachen.deimprove hermit network performanceStefan Lankesslankes@eonerc.rwth-aachen.deStefan Lankesslankes@eonerc.rwth-aachen.dehttps://git.rwth-aachen.de/acs/public/simulation/DistAIXFramework/dbconnector/-/issues/2Outdated / Depcrecated dependencies2023-08-08T15:42:11+02:00Katharina WehrmeisterOutdated / Depcrecated dependenciesWhen doing my own setup of DistAix and the dbconnector, I came across some difficulty in setup due to a few older dependencies. Most of those aren't a functional problem but require an update in documentationWhen doing my own setup of DistAix and the dbconnector, I came across some difficulty in setup due to a few older dependencies. Most of those aren't a functional problem but require an update in documentationKatharina WehrmeisterKatharina Wehrmeisterhttps://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.wege