-
Notifications
You must be signed in to change notification settings - Fork 175
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
Place for common configs #1058
Comments
This is a great idea! Never occurred to me, but I can already think of a bunch of places that this would be super useful. It's a nice level of abstraction above the regular objects, but below networks... Could make our network construction code more concise / consistent. Exciting! |
From the meeting: let's steal Handbrake's terminology and call these "presets". |
Any other presets than thresholding that people have and want to see included? |
Presets for different receptor types could be useful; |
@xchoo has a wide variety of configs that he uses for Spaun, including one for a ramp network if I remember correctly, but I think those more esoteric configs can wait until later. Is the next step for this issue to make a pull request? And by pull request, I mean one containing:
|
Yes, I will add my thresholding config (I think the example above needed some minor changes, I have a working version lying around). |
Added a PR for this. |
#1077 was merged, so this has been done! |
I repeatedly run across situations where I want to create thresholding ensembles and it would be nice to sort of have a network for that. But it is not really a network, but only a set of config options set on the ensemble. So I was wondering if we should have a place for functions that create such configs?
Not sure if there are other common sets of configuration options that get used?
In the thresholding case it would look somewhat like this:
and be used like this
The text was updated successfully, but these errors were encountered: