Closed molikd closed 1 year ago
Notes on language:
One of the first things to think about, what language to use? (1.) The language should be well adapted, (2.) have a firm grasp of yaml reading and writing and (3.) should have descent package management that allows for depositing the wrapper into /usr/local/bin so the end user can have the script in the PATH.
Of the languages that I personally know, that would be Perl, Python, Julia... and awk...
...regardless the package should be built in such a way that the data is entered into a intermediary data structure and converted to the required output directory, If written correctly we can expose intermediary data structure for use with other applications, this probably leaves out awk, as fun as that would be to write, leaving Perl, Python, and Julia. That'd be pandas for the data structure. Class::Struct in perl and struct in Julia.
As heavy weight as Perl's package management is, it is the most fully featured, and is the easiest to place packages into /usr/local/bin.
Python is probably the most heavily used language of the three, especially for bioinformatics work. On the other hand, perl is pretty descent for these file manipulations.
Probably go for perl.
Also the perl DBI package is great, someone will use this package and that in tandem for some really neat services
I forgot that pip has the ability to add command line abilities, we'll go with python
This is has been completed.
Create and Document tickets required for conversion script