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

Update _discrete_tune.py #155

Merged
merged 10 commits into from
Nov 9, 2022
Merged

Update _discrete_tune.py #155

merged 10 commits into from
Nov 9, 2022

Conversation

ddkohler
Copy link
Contributor

@ddkohler ddkohler commented May 25, 2022

Allow call(v) to work when v is an array type.

Resolves #156

@ksunden
Copy link
Member

ksunden commented May 30, 2022

I think this should rather return an ndarray with the value for every entry. thoughts?

ddkohler and others added 2 commits May 31, 2022 10:18
__call__:
array input gives array output
docstring
@ddkohler
Copy link
Contributor Author

I agree with you @ksunden . It gives the most consistency with the Tune class.

I've implemented the change and am waiting for testing on Waldo.

@ksunden
Copy link
Member

ksunden commented Jul 29, 2022

@ddkohler status?

@ddkohler
Copy link
Contributor Author

still needs to be tested on Waldo. I'll try to get someone to use it soon...

@ddkohler ddkohler merged commit 868d221 into master Nov 9, 2022
@ddkohler ddkohler deleted the DicreteTune-call-array branch November 9, 2022 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

DiscreteTune: __call__ fails for array argument
2 participants