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
I just stumbled upon this tool and I'm impressed. Looks pretty wonderful.
I work in the Computational Biology Department at St. Jude Children's Research Hospital. I'm the primary author of our WDL QC workflow. It is currently used to ensure new data to our St. Jude Cloud Genomics Platform is of sufficient quality, but we have plans for significantly expanding scope, including displaying integrated QC reports for every cohort/sample on the platform.
I'm interested in writing a WDL wrapper for alfred that we can host in our central tool repository, and then integrate with the QC workflow. However we currently use MultiQC for all our data aggregation and reporting. If alfred isn't integrated with MultiQC, we can't incorporate it into our workflow.
From a technical perspective, it should be quite easy to incorporate alfred into MultiQC. Phil Ewels, the primary maintainer over at the MultiQC repo has made contributing a breeze. And with the fact all your outputs are already in JSON and TSV, it should be just a matter of plugging and chugging.
What do you think about this integration?
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion! MultiQC support would certainly be useful and I'll keep it in mind, but I'm afraid this won't be a quick addition given the current workload.
I just stumbled upon this tool and I'm impressed. Looks pretty wonderful.
I work in the Computational Biology Department at St. Jude Children's Research Hospital. I'm the primary author of our WDL QC workflow. It is currently used to ensure new data to our St. Jude Cloud Genomics Platform is of sufficient quality, but we have plans for significantly expanding scope, including displaying integrated QC reports for every cohort/sample on the platform.
I'm interested in writing a WDL wrapper for
alfred
that we can host in our central tool repository, and then integrate with the QC workflow. However we currently use MultiQC for all our data aggregation and reporting. Ifalfred
isn't integrated with MultiQC, we can't incorporate it into our workflow.From a technical perspective, it should be quite easy to incorporate
alfred
into MultiQC. Phil Ewels, the primary maintainer over at the MultiQC repo has made contributing a breeze. And with the fact all your outputs are already in JSON and TSV, it should be just a matter of plugging and chugging.What do you think about this integration?
The text was updated successfully, but these errors were encountered: