Treat OutputFile fileName attribute as relative to the LEMS file directory

[JustasB]

Currently, the value in Include tag, file attribute is treated differently from the fileName attribute of OutputFile tag. They should be treated the same way for consistency.

E.g. <Include file="NML2_SingleCompHHCell.nml"/> looks for NML2_SingleCompHHCell.nml in the same folder as the LEMS file.

However, <OutputFile fileName="ex5_v.dat"> writes to ex5_v.dat in the folder from where jnml is being executed, which is not necessarily the same one where the LEMS file is located.

[pgleeson]

Thanks for pointing this out @JustasB.
I've just noticed that this is not the case with jnml -neuron, only jnml. In the former case the hoc/mod files as well as the generated dat files are created in the folder relative to the LEMS file (were you just referring to models run with jnml?)
I'll look into changing this.

[JustasB]

were you just referring to models run with jnml?<<
Yes, this was happening with jnml alone.

[pgleeson]

This will require a bit of work on the jlems java code, and will change the behaviour of the application in future for anyone running it from a different directory (though it is more consistent with the nml import & behaviour of jnml -neuron, so probably should be changed).
Can you give me an indication of how urgent this is for your workflow @JustasB?

[JustasB]

Not urgent. I'm using a workaround of cd'ing into the target directory in the meantime.