Closed julesjacobsen closed 6 years ago
This seems quite reasonable to me. I would also suggest we create a JavaFX app to run the Exomiser that would guide users through the development of a reasonable set of settings. I will profile something like that and we can see how it looks.
I vote yes as well. A long time since I used them and too complicated to use them nowadays me thinks with all the new options
On Tue, Jan 2, 2018 at 4:49 PM, Jules Jacobsen notifications@github.com wrote:
Phew! Glad you agree. We could also add a couple of presets for people to choose from based on the demos in the cli distribution e.g. exome https://github.com/exomiser/Exomiser/blob/master/exomiser-cli/src/main/resources/examples/test-analysis-exome.yml and genome https://github.com/exomiser/Exomiser/blob/master/exomiser-cli/src/main/resources/examples/test-analysis-genome.yml these could take the form:
steps: [ exomePreset: {} ]
or
steps: [ genomePreset: {} ]
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/exomiser/Exomiser/issues/241#issuecomment-354812349, or mute the thread https://github.com/notifications/unsubscribe-auth/AE7uPHCKiBbP5PNbU5Mfec8eWVms_cHmks5tGl4cgaJpZM4RQuRl .
The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.
Done in version 10.0.0
The cli options have become too numerous and are limited to the original exomiser algorithm only. They also use a parallel code path to the analysis API which means implementing new features requiring user input requires more than twice as much coding, testing and more opportunities for new bugs as well as inconsistent functionality/features depending on whether people use the analysis scripts or the cli switches.
For the next major version -
10.0.0
I'd like to propose completely dropping the cli commands as this will significantly reduce the burden of dead code and legacy logic. We've supported this for over three major versions (7.0.0
-9.0.0
), in which time the functionality of the analysis API has completely eclipsed the cli switches and provides a huge amount of added flexibility. It looks brutal, but it should help simplify things for both the user, the maintainers and also aid reproducibility as the script becomes the single point of entry to the analysis.@damiansm, @pnrobinson - comments please.
So we'll keep these:
And remove all these: