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
If you manage to run the example in this repo the output should look like this (the whole header in a message JSON key):
Which is quite far from ideal in terms of representation and formatting, isn't it? Think about the applications that might consume that output and try to weed out some specific detail... at present, that could be impractical to say the least.
If testing/deploying your solution in this AWS-coupled code gets on the way, feel free to create your own repository and present the solution there, together with some tests.
Happy hacking!
The text was updated successfully, but these errors were encountered:
Hello prospective GSoC 2022 candidate!
This challenge, should you take it, consists on extending the method
bam_header_as_json
so that the BAM header's return value is a well-formed and formatted JSON. The particular final JSON representation is majorly up to you as there can be as many representations as use cases (and perhaps even opinions?). While some previous knowledge of the bioinformatics formats is valuable, it is not required for this task.If you manage to run the example in this repo the output should look like this (the whole header in a
message
JSON key):Which is quite far from ideal in terms of representation and formatting, isn't it? Think about the applications that might consume that output and try to weed out some specific detail... at present, that could be impractical to say the least.
According to the official hts spec, the SAM (uncompressed BAM) header, there are multiple fields in the header, some of them are even formalized as protobuffer structs by Google. Is a direct representation useful and flexible enough for multi-format export functionality? How would you represent an IR (Internal Representation) for those fields so that future format exporters can read from that definition with performance and ease of use in mind?
If testing/deploying your solution in this AWS-coupled code gets on the way, feel free to create your own repository and present the solution there, together with some tests.
Happy hacking!
The text was updated successfully, but these errors were encountered: