Output format #198
Merged
Output format #198
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ozguzMete
force-pushed
the
outputFormat
branch
2 times, most recently
from
5a337ed to
7acb42d
Compare
|
Follow up as reported by @rmadupuri : #210 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A possible solution for the issue #194
There are lots of empty columns in the output file. You will be able to use option-format option to supply an output format.
As an example, you can create a file with the following line:
Hugo_Symbol,Entrez_Gene_Id,Center,NCBI_Build,Chromosome
the application will only output these columns + any other column/s required by the application.
Order is preserved.
Currently, it only supports commas as the separator. You can use any number of spaces you like...