Cannot write log files to subdirectories

[ms609]

I would like to write the output of a simulation to a subdirectory within TREvoSim_output. (Windows gets grumpy when there are too many files within a single directory – and it will make my output easier to navigate.)

If I specify a Basename of dir/file

I see an error at the end of the run:

Ideally TREvoSim would create the dir subdirectory. Failing that, it would be helpful to have some input validation so the user sees the error before beginning a run.

[RussellGarwood]

I had not considered this before - thanks for the suggestion. Can you clarify, though - I could make the software create dir for you, no worries, but then that would still result in - if you were e.g. doing a batch - a large number of files in that directory, just nested under one TREvoSim output folder. So would it be preferable to add an output option of e.g. "one folder per replicate" or something along those lines?

[RussellGarwood]

(sorry, I accidentally closed rather than commenting!)

[ms609]

I can see two use cases here:

• General: A user wants to put .nex files in a separate directory to .tnt files
• The one I have in mind: a user will edit a setting, then edit the directory name. So for example, I have procedurally generated some settings files that set the "number of taxa" option, and I want these files to also set directory names for output that look something like <NTAXA>_taxa. (I appreciate that I could instead set the working directory, but this would mean having the settings.xml files in lots of different directories instead of in one place.)

[RussellGarwood]

With the above commit this is now implemented - FYI you need to use forward slashes for paths (I note this, because on windows the native separator is a backslash). If you enter a path via the GUI with backslashes, the software replaces this with a forward slash, but if you are loading it programatically, you will need to ensure you use a forward slash otherwise the software will provide an error message. I'll add this to the documentation.