You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Correct me if I am wrong, but currently, the hdf5 file with psite information is saved in working dir and not in defined output-dir, this makes it fail if output-dir is not the working directory for the call.
This was tested on the latest version through Conda.
The text was updated successfully, but these errors were encountered:
Yes, it would be saved in working dir. RiboCode only provides an option for defining the outputs of annotation files. The hdf5 file will be named according to the information in the config file.
There should be an advanced FAQ where this is stated, together with the fact you can drastically speed up RiboCode if you input a hdf5 file directly. Had to tinker a lot to get this working and understand it all, nice for others to know :)
Correct me if I am wrong, but currently, the hdf5 file with psite information is saved in working dir and not in defined output-dir, this makes it fail if output-dir is not the working directory for the call.
This was tested on the latest version through Conda.
The text was updated successfully, but these errors were encountered: