As a user I'd like relative paths in ASSIGN statements to work.
While one can give relative paths to an ASSIGN statement already, depending on how the deck is run (think run.py/run.config) the relative paths break. So I think the solution would be to make them absolute (with some "guidance"/configuration by the user in the run.config file) when compiling the deck file.
P.S.: Trying to come up with a smart way of setting the relative paths in a project and passing them to TRNSYS as is is complicated by the fact that TRNSYS has its own way of dealing with relative paths: any path starting with a . (as in .\foo\bar.baz or ..\..\bum\ding.blang is interpreted relative to the TRNSYS installation directory, i.e. in many cases C:\TRNSYSxy (see C:\TRNSYS18\Documentation\06-TRNEdit.pdf).
As a user I'd like relative paths in ASSIGN statements to work.
While one can give relative paths to an ASSIGN statement already, depending on how the deck is run (think
run.py/run.config) the relative paths break. So I think the solution would be to make them absolute (with some "guidance"/configuration by the user in therun.configfile) when compiling the deck file.P.S.: Trying to come up with a smart way of setting the relative paths in a project and passing them to TRNSYS as is is complicated by the fact that TRNSYS has its own way of dealing with relative paths: any path starting with a
.(as in.\foo\bar.bazor..\..\bum\ding.blangis interpreted relative to the TRNSYS installation directory, i.e. in many casesC:\TRNSYSxy(seeC:\TRNSYS18\Documentation\06-TRNEdit.pdf).