Hey, as we discussed on our latest conversation, I started my partial work on the main qc workflow development trying to reach feature parity with h3agwas/qc.
I'd like to receive a review on this, we need to discuss the implementation paths into the internal logic of optional inputs need to be adapted to DSL-2 also the checked input is a channel manipulation technique that could be translated into a function or maybe a process to be executed. We can discuss the possibilities on this PR, I also decided to not touch the produceReports process until we shape the complete workflow methods.
I Kindly request your point of view on this small step onto the development on QC workflow, it certainly needs more organization and separation of the modules into sub-sub-workflows, but I'm not completely sure about this organization.
Hey, as we discussed on our latest conversation, I started my partial work on the main qc workflow development trying to reach feature parity with h3agwas/qc.
I'd like to receive a review on this, we need to discuss the implementation paths into the internal logic of optional inputs need to be adapted to DSL-2 also the checked input is a channel manipulation technique that could be translated into a function or maybe a process to be executed. We can discuss the possibilities on this PR, I also decided to not touch the
produceReportsprocess until we shape the complete workflow methods.I Kindly request your point of view on this small step onto the development on QC workflow, it certainly needs more organization and separation of the modules into sub-sub-workflows, but I'm not completely sure about this organization.
related to #32 and #29
Kindly, Davi.