-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signature of type "mrnaseq"
?
#58
Comments
Legacy, could be removed. I've been saving it for a metadata refactor,
that's all.
|
OK. I won't propose to touch it if going to be removed. If it is going to stay I'd propose to:
|
something like it will stay & I agree with your suggestions :)
On Sat, Dec 03, 2016 at 07:04:18AM -0800, Laurent Gautier wrote:
OK. I won't propose to touch it if going to be removed. If it is going to stay I'd propose to:
- make the type a parameter when creating instances of class `SourmashSignature`
- add a parameter to the command type (e.g., `--signature-type`) to specify that type. The default would be `"unspecified"`.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#58 (comment)
--
C. Titus Brown, ctbrown@ucdavis.edu
|
This was referenced Apr 18, 2017
6 tasks
6 tasks
Removed in #335. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why does a
.sig
signature file declares itself of type"mrnaseq"
(while the input could well be genomic DNA) ?https://github.com/dib-lab/sourmash/blob/master/sourmash_lib/signature.py#L36
The text was updated successfully, but these errors were encountered: