Closed blahah closed 9 years ago
one thing that was odd to me was that the '-o' input flag applies only to CSV files and not all the outputs produced
noted - I think we will eliminate the -o
argument once this new structure is used, as it will not really be needed (it's easy to just rename the transrate_results
if necessary)
Why not use it to specify the output path (or prefix) for everything? You can keep the working directory as the default
that seems a reasonable idea
@rozovr thanks, I implemented your idea and it will be in the next release
Currently, passing in multiple assemblies with the same filename, but in different directories will break transrate. This is because the filename (without the path) is used as the identifier when creating interim files.
Also, the working directory fills up with lots of files. This is ugly and makes debugging and interpretation harder for users.
The solution should be to create a neat directory structure. This could use a
transrate_results
subdirectory in the working directory. This directory would contain a single directory per assembly, with the unique part of each assembly's path, with/
replaced by_
.So for example, if the user passed in:
the following structure would be created: