Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to specify the group refiner(s) used in a canonical search #27

Open
wilfwilson opened this issue Sep 28, 2021 · 0 comments
Open
Labels
kind: new feature New features/capabilities nature: technical Uninteresting mathematically and fiddly things topic: canonical Relating to ‘canonical’ searches topic: interface Stuff relating to user-facing Vole interface (including the GAP wrapper) topic: refiners Relating to implementations of refiners in Vole/associated packages

Comments

@wilfwilson
Copy link
Collaborator

Currently, with the standard GAP interface, you can specify refiners for the thing that you want to canonise, but Vole does its own thing with the first argument, i.e. the group G that you are canonising in.

It would be nice if you could tell Vole which refiners it should use for the group (does that even make sense?).

@wilfwilson wilfwilson added kind: new feature New features/capabilities topic: refiners Relating to implementations of refiners in Vole/associated packages topic: canonical Relating to ‘canonical’ searches nature: technical Uninteresting mathematically and fiddly things topic: interface Stuff relating to user-facing Vole interface (including the GAP wrapper) labels Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: new feature New features/capabilities nature: technical Uninteresting mathematically and fiddly things topic: canonical Relating to ‘canonical’ searches topic: interface Stuff relating to user-facing Vole interface (including the GAP wrapper) topic: refiners Relating to implementations of refiners in Vole/associated packages
Projects
None yet
Development

No branches or pull requests

1 participant