Closed twVolc closed 8 months ago
Ok I'm now not sure this is the issue - I tried loading the same config again to double check and it's still throwing the error even after the edits... Going to investigate a bit further
ohhhhhh I've been an idiot, scrap this whole issue.... I had changed the name of the processed folder, so it wasn't able to find the file because it was looking in a folder that no longer exists....
I get the following error when trying to load in a config file that was generated at the end of processing:
It looks like this is related to back/forward slashes. The PCS lines in the config file are saved as:
note the 2 backslashes (after Seq3 and Processed_4).
I edited this to
And it loads in fine. So it looks like the program is able to deal with a separator of "/" or "\" prior to the filename, but that all directory separators need to be consistently the same. For some reason on saving the final data (presumably due to the fact that the program itself creates the "Processed_x" directory so adds the separator itself) separators get muddled and the file path isn't readable.
Probably the easiest solution (rather than ensuring consistency in writing pathnames), is to make sure reading the paths can deal with either separator simultaneously? Or maybe that's more convouted than just changing the separator used when generating the new Processed directory.