Anonymous | Login | Signup for a new account | 2024-11-22 13:53 MST |
My View | View Issues | Report Issue | Change Log | Roadmap | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0001359 | MEGA | [All Projects] Feedback | public | 2019-08-16 00:51 | 2023-04-14 19:04 | ||||||||
Reporter | guest | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||||
Status | new | Resolution | open | ||||||||||
Platform | OS | ||||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0001359: reading fasta | ||||||||||||
Description | For SOME fasta files containing nucleotide seqs, when opening via MEGA-X it automatically reads it as a protein files (as if A, C, G... indicate amino acids rather than nucleotides). In a few cases I aligned a genetic assemblage of seqs, exported it as fasta, and this very same export can now only be read as if it was of protein sequences. I can't find any consistent difference between my fastas that read properly and those that open as proteins. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attach Tags | (Separate by ",") | ||||||||||||
First Name | Zohar | ||||||||||||
Last Name | Yanai | ||||||||||||
yanaizohar@gmail.com | |||||||||||||
Confirm Email | yanaizohar@gmail.com | ||||||||||||
Attached Files | |||||||||||||
Issue History | |||
Date Modified | Username | Field | Change |
2019-08-16 00:51 | guest | New Issue | |
2022-03-08 07:37 | guest | Note Added: 0005022 | |
2023-04-14 19:04 | guest | Note Added: 0006822 |
Copyright © 2000 - 2024 MantisBT Team |