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
Feature Request: While I understand the necessity for ID conversion, the way it's implemented breaks downstream processing of the results. There are two ways to solve this (that I can think of), provide a translation from the old identifiers to the new in an output file, or convert back before outputting the final files.
The text was updated successfully, but these errors were encountered:
Sorry for the delayed response. Which ID conversion were you referring to? Can you please provide a little bit more information on the original format, the new format, and the expected format?
I am revisitin this issue. The ID conversion code implemented in LTR_retriever was to help users that don't know how to format their sequence IDs before any whole genome annotations. It's always recommended to format seq IDs before analysis. The current ID length allocation is limited to 13 characters because the downstream rmblast restrict ID length to 50 characters (If I remember correctly). The remaining length is reserved to contain coordinate information in intermediate files. Please refer to more discussions in #16#93. Your proposed translation system may work, but still require users to tidy up sequence IDs before any analysis.
Feature Request: While I understand the necessity for ID conversion, the way it's implemented breaks downstream processing of the results. There are two ways to solve this (that I can think of), provide a translation from the old identifiers to the new in an output file, or convert back before outputting the final files.
The text was updated successfully, but these errors were encountered: