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
The new way of formatting a fasta dictionary from the input fasta file seems to be broken.
The output CSV file contains some strange chars like : "('FASTA_HEADER'," where FASTA_HEADER is the name of the sequence. The extra comma is a problem in a CSV file.
The sequence also has some chars on the end that shouldn't be there. I think it's the result of a tuple being formatted as a string and then split into a dictionary.
There are also a few array slices when writing the CSV file: chromosome[1::] that seem redundant.
Functions responsible are formatted and generate_dictionary. It looks like it might be an unintended consequence of attempting to speed up the code.
Hi Hans
The new way of formatting a fasta dictionary from the input fasta file seems to be broken.
The output CSV file contains some strange chars like : "('FASTA_HEADER'," where FASTA_HEADER is the name of the sequence. The extra comma is a problem in a CSV file.
The sequence also has some chars on the end that shouldn't be there. I think it's the result of a tuple being formatted as a string and then split into a dictionary.
There are also a few array slices when writing the CSV file: chromosome[1::] that seem redundant.
Functions responsible are formatted and generate_dictionary. It looks like it might be an unintended consequence of attempting to speed up the code.
This should be simple to fix.
Kind regards
Derek
WANTED.csv
The text was updated successfully, but these errors were encountered: