bfdistance: one filter vs a set of filters about howdesbt

[rsharris]

It's now tagged as release 2.00.15 .

As I am doing less and less with github these days, the chance that I will remember to update version numbers and do things like tag releases (or even how to tag a release) decreases.

[rsharris]

(currently, it seems ignoring if --list= is also specified, but I may be wrong)

Actually, it accumulates all the filenames specified on the command line, plus any that are in a file specified by --list=.

To maintain backward compatibility, I would add another option, something like --reference=. And then compute the distance between that reference BF and any other bfs specified (whether by filename or by --list).

I'd also need to figure out whatever other commands behave the same as bfdistance and implement the same for those.

At present, I don't have a built version of the program on my machine, and when I attempted to build it I ran into a problem with access to h files for one of the libraries. So it'll be a while before I implement this.

[cumbof]

The --reference=<filename> solution in conjunction with <filename> or --list=<filename> would be great to have!
You would probably do the same for the bfoperate command.

[rsharris]

Thanks — I think bfoperate is the only similar command.

I'm not sure if reference is the best name for this option. What do you think of these alternatives: focus, base, basis, common, target, kernel, ground, center, keystone, core, object? I'm leaning toward focus.

[cumbof]

I agree, focus is probably the best one, I would go with that

[rsharris]

Added --focus=<filename>. Only added to bfdistance. I looked at bfoperate but decided that uses the collection of filters differently, So I didn't think --focus=<filename> made sense there.

I added more detail to the usage message ?bfdistance.

[cumbof]

That’s awesome! Could you also create a new release or pre-release so that I can update the conda package as well?

[cumbof]

Thanks!