agent config files currently have to be local to the .assisi file

[rmm-fcul]

not sure whether they should assume being local to the agent script, or always assume fully-qualified path?

certainly, should correctly handle an absolute path. Relative paths are more ambiguous in complex setups - relative to where tool was executed, relative to agent script, relative to project file?

[rmm-fcul]

Testing run_multiagent alone, seems no problem with the .conf files:

• relative paths are ok. (this is relative to the agent behaviour script)
• no path is ok (==> conf in same directory as agent script)
• absolute path is ok

these are all tested assuming run_multiagent is executed local to where the agent scripts are.

need to verify the working dir used by exec_sim_timed tools.

[rmm-fcul]

the issue is more to do with exec_sim_timed and the assumption made in the config script, which defines how the --conf option is written for each of the agents (in the agent listing).

If the agent listing contains an absolute path (for both agent script and config), run_multiagent works fine from anywhere.

Perhaps a good solution is to write a fully qualified path at the spawn time. Relative paths make sense for the main utils .conf file. The alternative is to close as wont-fix