Let's say I want to modify the 3x3 example to only use the first two casus, casu-001, casu-002. I modify the file "local.dep" (sim-01 just has entries for these 2 casus).
The errors are as follows:
deploy.py stage assumes that all elements of the arena are present in the .dep file, and so breaks if they are not present.
Traceback (most recent call last):
File "...assisipy/deploy.py", line 185, in <module>
project.deploy()
File "...assisipy/deploy.py", line 156, in deploy
self.prepare()
File "...assisipy/deploy.py", line 117, in prepare
shutil.copy(os.path.join(self.project_root,self.dep[layer][casu]['controller']),'.')
KeyError: 'casu-003'
A possible workaround - if really needed:
it is possible to work around if we run deployment with a complete element list (to generate all the files), and then execute assisirun.py with a partial .dep file. However, this is not an elegant solution because it requires maintenance of two .assisi files or editing during the workflow, and if the reason some were omitted is due to hardware use (for a simultaneous experiment, or temporariliy unavailable casu), the deployment could also fail.
remark on simulation side:
sim.py stage also spawns everything in the .arena file (it is only passed the arena file and not the .assisi setup file so clearly it can't know; whether it should follow the deployment restriction is not clear to me).
Let's say I want to modify the 3x3 example to only use the first two casus, casu-001, casu-002. I modify the file "local.dep" (sim-01 just has entries for these 2 casus).
The errors are as follows:
A possible workaround - if really needed:
remark on simulation side: