Closed pb-cdunn closed 5 years ago
when isMainModule:
import cligen
dispatchMulti(
...
[overlapFilter.falconRunner, cmdName = "m4filt-falconRunner",
help = {
"lasJson": "List of las files from falcon, e.g ../1-preads_ovl/las-merge-combine/las_fofn.json",
"idtStage1": "Stage one percent identity filter, formatted as percentage, overlaps < %idt are skipped",
"idtStage2": "Stage two percent identify filter",
"minLen": "Minimum read length, reads shorter than minLen will be discarded",
"minCov": "Minimum number of overlaps on either side of a read",
"maxCov": "Maximum number of overlaps on either side of a read",
"maxDiff": "Reads are skipped is abs(5p-3p) overlap counts > maxDiff",
"bestN": "Keep N best overlaps at 5prime AND 3prime of a read",
"minDepth": "Depths lower than minDepth are considered gaps",
"gapFilt": "Run depth filter, takes a little more time",
"nProc": "Number of processes to run locally",
"filterLog": "Write read filter stats to this file",
"outputFn": "Final m4 overlap file",
}
],
So, you mean long options associated with boolean-valued parameters not sub-commands, of course. I will have to look into this. For my own commands with bool parameters I have no trouble issuing flexible spelling.
Well, I haven't tried this except as a sub-command.
Oh, ho! It works if the long option for a bool is the last thing on the command-line, but fails if it's earlier. The plot thickens. ;-)
(I didn't mean to sound flip...This is definitely a bona fide bug I should fix. Will have to debug it, though.)
It's fine. I love it!
It also only happens if the parameter
!= optionNormalize(parameter)
. So, if you need an instant fix you can probably use gapfilt
in your Nim code, though in the long-term I do feel a burning need to fix this. (Anything with mixed case doesn't even make it into OptParser.noLongVal
.)
Ooops - I mean longNoVal
.
Oh, I probably don't need a fix at all. Just thought you would be interested.
I plan to switch all these to gap_filt
etc. in the code, and then I'll bet --gap-filt
will work fine.
Well, I am interested and I'm going to fix it..once I figure it out. (Not sure if gap_filt
will work either since normalizing is also needed there.)
github auto-closed this. I think it's fixed. Let me know if otherwise.
Thanks. We'll have to update our subtree, so just assume it's fixed unless we find a problem.
Ok.
I've switched most args to
--posix-style
, but I am forced still to use--gapFilt
because of the above.