Duplicate IDs in org.fortiss.af3.efficientdeployment (Task / Nodes / Message / BusChannel)
- Testing the implementation of #2309, the following example projects
with duplicate IDs in
Tasks
, Nodes
, Signals
,Messages
,
BusChannels
objects have been detected.
- It should be verified if there is an error with the corresponding
unique ID assignment scheme
- Once the fix for #2309 has been committed, the duplicates can be
easily fixed by loading the corresponding example and exporting it.
- Shell script to check for duplicate IDs:
for i in `find . -name "*.af3_23"`; do grep "id\=" $i | perl -pi -e "s/.*\s(id\=\"[0-9]+\").*$/\$1/g" | sort -n | uniq.exe -d && echo $i; done;
./plugins/org.fortiss.af3.scheduling/test-data/ACC-DAG-Test2.af3\_23
./plugins/org.fortiss.af3.scheduling/test-data/ACC\_partitions.af3\_23
./plugins/org.fortiss.af3.scheduling/test-data/Partitioning\_Emergency.af3\_23
./plugins/org.fortiss.af3.scheduling/test-data/Thesis.af3\_23
./plugins/org.fortiss.af3.scheduling/test-data/ThesisExample\_biggest48.af3\_23
<Nodes id=“52” name=“ecu1” LocalMemory=“200”
AllocatedTasks="//@rootElements.3/@histories.0/@manualPlatformEntry.0/@generatedDeploymentEntries.0/@efficientDeployment/@Tasks.0
//@rootElements.3/@histories.0/@manualPlatformEntry.0/@generatedDeploymentEntries.0/@efficientDeployment/@Tasks.1
//@rootElement
*(from redmine: issue id 2314, created on 2015-03-16, closed on 2016-03-07)*
* Relations:
* parent #2317