RAMSES issueshttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues2018-03-20T17:39:03Zhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/9AADL Inspector plugin fails when the repository of the project is changed on ...2018-03-20T17:39:03ZEtienne BordeAADL Inspector plugin fails when the repository of the project is changed on the diskWhen launching AADL Inspector with a command line, the path of aadl files is built using the osate project name which does not always match a directory on the diskWhen launching AADL Inspector with a command line, the path of aadl files is built using the osate project name which does not always match a directory on the diskhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/14Validation of AADL model before refinement is applied to unrelated components2017-07-28T15:23:40ZDominique BlouinValidation of AADL model before refinement is applied to unrelated componentsWhen validation is executed on a system instance prior to model refinement, the content of all files refered by the instance is validated. Only the classifiers used by the system should be validated, as there might be unrelated classifie...When validation is executed on a system instance prior to model refinement, the content of all files refered by the instance is validated. Only the classifiers used by the system should be validated, as there might be unrelated classifiers in the same component library file. Performance would be improved as well.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/17Clean example aadl files2018-03-09T12:13:29ZArthur RemaudClean example aadl filesThe examples given by RAMSES don't build because of multiple packages with the same name. They need to be corrected so the user can open all of them with a successful built.The examples given by RAMSES don't build because of multiple packages with the same name. They need to be corrected so the user can open all of them with a successful built.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/18RAMSES Test Suite Refactoring2018-09-14T13:57:41ZDominique BlouinRAMSES Test Suite RefactoringWe would like to be able to launch the various steps of the RAMSES tests suite (e.g.: refinement, analysis, code generation, etc.) independently and for the two different contexts (IDE and command line interface).We would like to be able to launch the various steps of the RAMSES tests suite (e.g.: refinement, analysis, code generation, etc.) independently and for the two different contexts (IDE and command line interface).Alice GoudoutAlice Goudouthttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/21Refactoring of OSATE Command Line Interface and Standalone Setup Classes2017-11-07T13:34:36ZDominique BlouinRefactoring of OSATE Command Line Interface and Standalone Setup ClassesMigrate these classes to utility projects that do not depend on RAMSES.Migrate these classes to utility projects that do not depend on RAMSES.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/22Creation of workflows for the generation of C code2018-03-09T12:13:29ZArthur RemaudCreation of workflows for the generation of C codeWe want to use workflows in RAMSES to separate the different steps of execution. There is already a workflow for the refinement of the aadl model, but not yet for the generation of the C code.
We need to create a different workflow for ...We want to use workflows in RAMSES to separate the different steps of execution. There is already a workflow for the refinement of the aadl model, but not yet for the generation of the C code.
We need to create a different workflow for each target platform (POSIX, OSEK and POK). These workflows should be executed independently of the others by taking in parameters the refined aadl model and the trace of the refinement. They could also be integrated in a bigger workflow executing all steps.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/26Test different types of threads for POSIX and OSEK architectures2018-01-12T14:38:31ZArthur RemaudTest different types of threads for POSIX and OSEK architecturesIn the new runtime code, new types of threads have been added: timed threads, hybrid threads and aperiodic threads. Because the ATL transformation doesn't manage these threads for POSIX and OSEK architectures yet, they need to be tested.In the new runtime code, new types of threads have been added: timed threads, hybrid threads and aperiodic threads. Because the ATL transformation doesn't manage these threads for POSIX and OSEK architectures yet, they need to be tested.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/27Adapt the ports to be connected with data references2018-03-09T12:13:29ZArthur RemaudAdapt the ports to be connected with data referencesIn the new runtime, the data ports and the data references are not managed the same way. So now, the ports can't be connected to a data reference, which is not the expected behavior. We need to accept connections with data references, in...In the new runtime, the data ports and the data references are not managed the same way. So now, the ports can't be connected to a data reference, which is not the expected behavior. We need to accept connections with data references, in input and output.
This implies to change the C code of the runtime, and also the ATL transformation to generate data references in place of data port where it should be. We need also to get these data references to register them in the port, which will be different than other ports.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/28Management of modes to receive informations from ports2018-01-19T15:44:29ZArthur RemaudManagement of modes to receive informations from portsFor now, the output ports of a thread manage the different modes which change the recipient of the message, but not the input ports. This is explain by the lack of data reference in ports source or recipient which bring the problem (see ...For now, the output ports of a thread manage the different modes which change the recipient of the message, but not the input ports. This is explain by the lack of data reference in ports source or recipient which bring the problem (see issue #27).
Something similar to the output ports can be done, but it will be different to get the correct informations to initialize this.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/29Remove the return instruction when the state is not final2018-01-19T17:00:34ZArthur RemaudRemove the return instruction when the state is not finalIn the generation of code, in the file activity.c, there is a return instruction after the call of the thread's main function. This is not correct when the thread is not actived in all modes, because it ends the thread whereas it should ...In the generation of code, in the file activity.c, there is a return instruction after the call of the thread's main function. This is not correct when the thread is not actived in all modes, because it ends the thread whereas it should just iterate on the loop.
The origin of this line is in the file AadlBaToCUnparser.java at the line 649 in the project fr.tpt.aadl.ramses.generation.c.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/30Leave the main function of a thread when the mode has changed2018-01-19T17:03:55ZArthur RemaudLeave the main function of a thread when the mode has changedWhen the mode changes, some threads should passed to sleep state, but it doesn't. There is nothing that makes them leave their main loop in the file subprogram.c.
This function should end when the mode is not the same.When the mode changes, some threads should passed to sleep state, but it doesn't. There is nothing that makes them leave their main loop in the file subprogram.c.
This function should end when the mode is not the same.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/32Problem of queue full2018-01-23T10:42:50ZArthur RemaudProblem of queue fullWhen there is a thread which can change the current mode, it has a output port taking events to know when this switch is triggered. The problem is that this output port is never used somewhere else, and the events' queue is quickly full....When there is a thread which can change the current mode, it has a output port taking events to know when this switch is triggered. The problem is that this output port is never used somewhere else, and the events' queue is quickly full.
Maybe the planned thread and/or the emergency thread need to have a Receive_Input call to free space in the queue ?https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/43Updating RAMSES leads to corrupted installation2018-08-17T10:22:03ZDominique BlouinUpdating RAMSES leads to corrupted installationOne needs to uninstall then re-install. Updationg should be sufficient.One needs to uninstall then re-install. Updationg should be sufficient.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/45Change path generation in Makefiles for them not to be absolute2018-11-13T13:23:58ZFerdinand LemaireChange path generation in Makefiles for them not to be absoluteCurrently, the generated paths in Makefiles are absolute based on the user who generated the code's machine. If the code is put on another system, it won't be possible to "make" it because of that.Currently, the generated paths in Makefiles are absolute based on the user who generated the code's machine. If the code is put on another system, it won't be possible to "make" it because of that.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/46Create a script to download sources of the runtime on the targeted system2018-11-13T14:13:14ZFerdinand LemaireCreate a script to download sources of the runtime on the targeted systemThe generated code from RAMSES needs the runtime files and the common components files to be built. If the generated code alone is deployed on the targeted system, it won't build because of the missing files. A solution would be to write...The generated code from RAMSES needs the runtime files and the common components files to be built. If the generated code alone is deployed on the targeted system, it won't build because of the missing files. A solution would be to write a script that download the runtime files on the targeted system.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/47Some Dispatch Protocols are not Handled for Model Refinement2018-11-14T13:10:36ZDominique BlouinSome Dispatch Protocols are not Handled for Model RefinementWhen a sporadic or aperiodic dispatch protocol is set to a thread, the model refinement crashes. At least we would need a validation error.When a sporadic or aperiodic dispatch protocol is set to a thread, the model refinement crashes. At least we would need a validation error.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/51At compile time, put object files in a subfolder of the output dir2018-12-20T11:55:16ZEtienne BordeAt compile time, put object files in a subfolder of the output dirIn case osate is installed in a directory without write permissions, compilation of the runtime source code fails.In case osate is installed in a directory without write permissions, compilation of the runtime source code fails.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/53Check existence of Target property2021-11-09T16:37:12ZEtienne BordeCheck existence of Target propertyEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/54Parameter connections of threads are preserved in the refined model2021-11-09T16:44:59ZEtienne BordeParameter connections of threads are preserved in the refined modelEtienne BordeEtienne Bordehttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/55Missing Data_Model in set of with clauses in the refined model2021-11-09T16:45:19ZEtienne BordeMissing Data_Model in set of with clauses in the refined modelEtienne BordeEtienne Borde