RAMSES issueshttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues2021-10-21T13:48:54Zhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/12The EMFTVM execution pool and environment are created twice when executing a ...2021-10-21T13:48:54ZDominique BlouinThe EMFTVM execution pool and environment are created twice when executing a refinementDominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/52Validation of aadl package name ending with _broken does not work2019-10-22T12:02:05ZAlexandre BarrauxValidation of aadl package name ending with _broken does not workValidation of a package whose name ends with _broken does not work, see the trace below.
The package name was sampled_communications_broken. Changing it to sampled_communications or sampled_communications_toto does work.
ERROR: emftVmTr...Validation of a package whose name ends with _broken does not work, see the trace below.
The package name was sampled_communications_broken. Changing it to sampled_communications or sampled_communications_toto does work.
ERROR: emftVmTransformer:EmftVmTransformer : Error when executing workflow component emftVmTransformer
java.lang.IllegalArgumentException: Default trace already exists for source element list check_Connection_Instance_cnx::[obj:ConnectionInstance -> [], cnx:PortConnection -> []]: check_Connection_Instance_cnx::[obj:ConnectionInstance -> [], cnx:PortConnection -> []]
at org.eclipse.m2m.atl.emftvm.trace.impl.TraceLinkSetImpl.defaultSourceElementListAdded(TraceLinkSetImpl.java:482)
at org.eclipse.m2m.atl.emftvm.trace.impl.TraceLinkSetImpl.eNotify(TraceLinkSetImpl.java:406)
at org.eclipse.emf.common.notify.impl.NotificationImpl.dispatch(NotificationImpl.java:1027)
at org.eclipse.m2m.atl.emftvm.trace.impl.SourceElementListImpl.setDefaultFor(SourceElementListImpl.java:131)
at org.eclipse.m2m.atl.emftvm.impl.RuleImpl$DefaultOnState.createDefaultMapping(RuleImpl.java:432)
at org.eclipse.m2m.atl.emftvm.impl.RuleImpl$IsNotAbstractState.createTraces(RuleImpl.java:1031)
at org.eclipse.m2m.atl.emftvm.impl.RuleImpl.createTraces(RuleImpl.java:2226)
at org.eclipse.m2m.atl.emftvm.impl.ExecEnvImpl.matchAllSingle(ExecEnvImpl.java:2257)
at org.eclipse.m2m.atl.emftvm.impl.ExecEnvImpl.run(ExecEnvImpl.java:2109)
at fr.tpt.mem4csd.workflow.components.atl.workflowemftvm.impl.EmftVmTransformerImpl.doTransformation(EmftVmTransformerImpl.java:512)
at ERROR: emftVmTransformer:EmftVmTransformer : Error when executing workflow component emftVmTransformer
java.lang.IllegalArgumentException: Default trace already exists for source element list check_Connection_Instance_cnx::[obj:ConnectionInstance -> [], cnx:PortConnection -> []]: check_Connection_Instance_cnx::[obj:ConnectionInstance -> [], cnx:PortConnection -> []]
at org.eclipse.m2m.atl.emftvm.trace.impl.TraceLinkSetImpl.defaultSourceElementListAdded(TraceLinkSetImpl.java:482)
at org.eclipse.m2m.atl.emftvm.trace.impl.TraceLinkSetImpl.eNotify(TraceLinkSetImpl.java:406)
at org.eclipse.emf.common.notify.impl.NotificationImpl.dispatch(NotificationImpl.java:1027)
at org.eclipse.m2m.atl.emftvm.trace.impl.SourceElementListImpl.setDefaultFor(SourceElementListImpl.java:131)
at org.eclipse.m2m.atl.emftvm.impl.RuleImpl$DefaultOnState.createDefaultMapping(RuleImpl.java:432)
at org.eclipse.m2m.atl.emftvm.impl.RuleImpl$IsNotAbstractState.createTraces(RuleImpl.java:1031)
at org.eclipse.m2m.atl.emftvm.impl.RuleImpl.createTraces(RuleImpl.java:2226)
at org.eclipse.m2m.atl.emftvm.impl.ExecEnvImpl.matchAllSingle(ExecEnvImpl.java:2257)
at org.eclipse.m2m.atl.emftvm.impl.ExecEnvImpl.run(ExecEnvImpl.java:2109)https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/7Currently it is not possible to generate code when AADL inspector is not inst...2019-02-09T11:24:55ZDominique BlouinCurrently it is not possible to generate code when AADL inspector is not installedhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/5Data type of subcomponent is null when refining CBTC model2019-02-09T11:24:11ZDominique BlouinData type of subcomponent is null when refining CBTC modelWhy is it null? This causes an exception in class AadlToXUnparser line 88.Why is it null? This causes an exception in class AadlToXUnparser line 88.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/23Rewrite the C provided code2019-02-09T11:23:16ZArthur RemaudRewrite the C provided codeThe C code provided needs to be improved in some points.
It needs to be refactored to don't use too many macros to separate the different platforms (POSIX, OSEK and POK) which made it more confused. This should be made by the makefile b...The C code provided needs to be improved in some points.
It needs to be refactored to don't use too many macros to separate the different platforms (POSIX, OSEK and POK) which made it more confused. This should be made by the makefile by including different files for different platform.
The datastructures and the functions should match more the aadl language, and then called the functions depending of the platform. We want an implementation in two levels: one hight-level near of the aadl language and one low-level near of the architecture. These functions have to match the aadl standard (see documentation), so the user can call them in his subprograms' code.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/31Problem of unit for thread's period2019-02-09T11:22:21ZArthur RemaudProblem of unit for thread's periodDuring the generation of code for the example osek-modes_without_datareference, the initialization of period value is wrong for all periodic threads: the value is given in milliseconds in place of microseconds.
This error seems to come ...During the generation of code for the example osek-modes_without_datareference, the initialization of period value is wrong for all periodic threads: the value is given in milliseconds in place of microseconds.
This error seems to come from the call to the function getScaledValue of the AADL meta-model.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/50Test with feature groups2019-02-09T11:21:10ZEtienne BordeTest with feature groupsRAMSES is not tested with models including feature groups.RAMSES is not tested with models including feature groups.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/49Add a variable in aadl model of communication to know if the proc is a sender...2018-12-06T15:18:54ZFerdinand LemaireAdd a variable in aadl model of communication to know if the proc is a sender or a receiverAdd a variable of type communication_role_t. In the_proc_1 it should be a sender while in the_proc_2 it should be a receiver currently.Add a variable of type communication_role_t. In the_proc_1 it should be a sender while in the_proc_2 it should be a receiver currently.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/15Migrate the RAMSES and Behavioral Annex websites to MEM4CSD2018-12-05T19:31:55ZDominique BlouinMigrate the RAMSES and Behavioral Annex websites to MEM4CSDThe old website of these projects (http://penelope.enst.fr/aadl/wiki/Projects) should be migrated to the MEM4CSD website (https://mem4csd.telecom-paristech.fr/blog/)The old website of these projects (http://penelope.enst.fr/aadl/wiki/Projects) should be migrated to the MEM4CSD website (https://mem4csd.telecom-paristech.fr/blog/)https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/48Generation for subprograms with AADL property value for convention property f...2018-12-04T19:44:29ZEtienne BordeGeneration for subprograms with AADL property value for convention property fails if not in the same packageIf the subprogram with AADL convention is in the same aadl package as the call, it works; otherwise the call is done with the value instead of the address of the context.
See line-follower demo to reproduce: move Log subprogram from its...If the subprogram with AADL convention is in the same aadl package as the call, it works; otherwise the call is done with the value instead of the address of the context.
See line-follower demo to reproduce: move Log subprogram from its package to another.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/16Develop a refinement traceability metamodel2018-09-14T13:58:03ZDominique BlouinDevelop a refinement traceability metamodelRAMSES currently uses a class (HookAccess) in order to trace some model elements from the source model to the refined elements of the refined model. This is implemented as a map contained in the class, which cannot be saved in a file for...RAMSES currently uses a class (HookAccess) in order to trace some model elements from the source model to the refined elements of the refined model. This is implemented as a map contained in the class, which cannot be saved in a file for further use. We would like to have a dedicated traceability metamodel that could be saved in a file in order to replace this.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/44Move analysis results metamodel to Gitlab Utilities project2018-09-14T08:49:05ZDominique BlouinMove analysis results metamodel to Gitlab Utilities projectThis is so that SEFA can be independent of RAMSES. See issue #1 of SEFA project and issue #2 of Utilities project.This is so that SEFA can be independent of RAMSES. See issue #1 of SEFA project and issue #2 of Utilities project.Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/2Update RAMSES to use the standard .aadl file extension instead of .aadl22018-09-13T12:05:05ZDominique BlouinUpdate RAMSES to use the standard .aadl file extension instead of .aadl2Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/1RAMSES does not compile with latest OSATE stable release2018-09-13T12:05:05ZDominique BlouinRAMSES does not compile with latest OSATE stable releaseRAMSES does not compile with the latest OSATE code (version 2.2.1).RAMSES does not compile with the latest OSATE code (version 2.2.1).Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/42RAMSES does not compile with OSATE 2.3.42018-07-23T16:05:26ZDominique BlouinRAMSES does not compile with OSATE 2.3.4Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/38Allow partitions to be bound to processors (instead of subcomponents only)2018-07-12T12:29:36ZEtienne BordeAllow partitions to be bound to processors (instead of subcomponents only)RAMSES only supports cases where partitions are defined as subcomponents of a processor. Virtual processors cans also be bound to a processor (with Actual_Processor_Binding). This should be supported as well since it seems to enable bett...RAMSES only supports cases where partitions are defined as subcomponents of a processor. Virtual processors cans also be bound to a processor (with Actual_Processor_Binding). This should be supported as well since it seems to enable better separation of concerns.Etienne BordeEtienne Borde2018-04-30https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/40RAMSES fails referencing source or header files in a different eclipse projet2018-06-18T19:36:25ZEtienne BordeRAMSES fails referencing source or header files in a different eclipse projetIf sources (.c/.h) are in a different project than the main AADL file, the referenced project is not added in the -I option of the generated Makefile.If sources (.c/.h) are in a different project than the main AADL file, the referenced project is not added in the -I option of the generated Makefile.https://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/41Missing package in with clause when uninstantiating a feature2018-06-15T15:25:54ZEtienne BordeMissing package in with clause when uninstantiating a featureWhen producing AADL intermediate model, there is a missing property set in the with clauses. See asterios example from the PST gitlab to reproduce the bugWhen producing AADL intermediate model, there is a missing property set in the with clauses. See asterios example from the PST gitlab to reproduce the bughttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/39Error when comparing the trace files when executing the generated code for th...2018-03-30T08:43:57ZDominique BlouinError when comparing the trace files when executing the generated code for the testsFor example, for the ARINC653 blackboard test, the generated file the_cpu.trace is detected from being different from the reference while it is identical. The differences output is:
Differences were found between file 'tests/arinc653/ar...For example, for the ARINC653 blackboard test, the generated file the_cpu.trace is detected from being different from the reference while it is identical. The differences output is:
Differences were found between file 'tests/arinc653/arinc653-blackboard/output_ref/generated-code/the_cpu/the_cpu.trace' and file 'tests/arinc653/arinc653-blackboard/output/generated-code/the_cpu/the_cpu.trace'!!!
Delete Old line(s) 1-19 1: QEMU 2.5.0 moniPOK kernel initialized2: send value: 23: received value: 24: received value: 25: send value: 36: received value: 37: received value: 38: send value: 49: received value: 410: received value: 411: send value: 512: received value: 513: received value: 514: send value: 615: received value: 616: received value: 617: send value: 718: send value: 819: send value: 9Dominique BlouinDominique Blouinhttps://gitlab.telecom-paris.fr/mbe-tools/RAMSES/-/issues/37Improper exception handling when target runtime platform path is not correct ...2018-03-28T11:40:42ZDominique BlouinImproper exception handling when target runtime platform path is not correct in OSATE CLIWhen the target runtime is not configured, the OSATE command line interface application crashes silently.When the target runtime is not configured, the OSATE command line interface application crashes silently.Dominique BlouinDominique Blouin