Skip to content
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

Macro(Export FASTA): The header 'Sequence N' is missing, and '>' symbol is located at end of the first sequence #1852

Closed
Zhirnoff opened this issue Mar 19, 2024 · 2 comments · Fixed by #1867 or #1873
Assignees
Labels

Comments

@Zhirnoff
Copy link
Collaborator

Steps to Reproduce

  1. Switch to Macro mode
  2. Add two RNA sequences on canvas
  3. Save as FASTA file and look at preview

Actual behavior
The header 'Sequence N' is missing, and '>' symbol is located at end of the first sequence

Expected behavior
Each molecule should be exported like separate sequence with the header "Sequence N", where N - is the number of sequence

2024-03-19_17h26_25

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser Chrome
  • Version 112.0.5615.138 (Official Build) (64-bit)

Indigo version
[Version 1.19.0-rc.1]

Attachments

2024-03-19_16h57_14

@Zhirnoff Zhirnoff added epic: macromolecules FASTA Bucket: FASTA related issues labels Mar 19, 2024
@Zhirnoff Zhirnoff added this to the Indigo-1.19.0-rc.2 milestone Mar 19, 2024
even1024 added a commit that referenced this issue Mar 22, 2024
…' symbol is located at end of the first sequence (#1867)
even1024 added a commit that referenced this issue Mar 24, 2024
…' symbol is located at end of the first sequence (#1867)
AlexanderSavelyev pushed a commit that referenced this issue Mar 25, 2024
…ing, and '>' symbol is located at end of the first sequence (#1867) (#1873)
@Zhirnoff
Copy link
Collaborator Author

There is no space between inscription and number
2024-03-27_19h39_31

@Zhirnoff
Copy link
Collaborator Author

Zhirnoff commented Apr 2, 2024

Closed after discussion with @vanoprenko

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment