Closed sooheelee closed 7 years ago
Tagging @cmnbroad as requested.
Looks like Mutect2 has a private Mutect2Engine, and Mutect2Engine has an M2ArgumentCollection, both of which contain fields with @Argument annotations. For these (nested) arguments to be visible to the command line parser/doc, they need to be both annotated in the containing class with @ArgumentCollection, and instantiated by the constructor (i.e., Mutect2's Mutect2Engine would have to be instantiated by the constructor). Otherwise, they may have to be refactored.
@sooheelee @cmnbroad These are arguments for the stand-alone filtering CLI FilterMutectCalls
. There were good reasons for doing this, which I think will be worth the nuisance.
So to be clear, you guys have a handle on how to make the arguments appear in the docs? Is this something you can do in the near future? We need the arguments to appear in the docs for the beta release.
Yes, all solved. These parameters that I thought were missing in Mutect2 are actually now in the new tool FilterMutectCalls and do show up in the documentation.
This is likely intentional but we should still show these parameters in the #docs.
Test command:
Error message:
Here's what the autodoc shows. Notice the lack of
--tumor_lod
description. This is only 1 of 13 parameters within the M2FiltersArgumentCollection that are absent.