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

TransferWithCosts: Shape of the variable of the combination function is always single element array #2712

Open
jvesely opened this issue Jun 30, 2023 · 0 comments

Comments

@jvesely
Copy link
Collaborator

jvesely commented Jun 30, 2023

$ python3 -c 'import psyneulink as pnl; f = pnl.TransferWithCosts(enabled_cost_functions=pnl.CostFunctions.ALL); f(10); print(f.combine_costs_fct.defaults.variable)'
[0]

the above example combination function takes 3 inputs, but it's not reflected in the shape of the default variable of the combination function.

jvesely added a commit to jvesely/PsyNeuLink that referenced this issue Jun 30, 2023
…t calculation

No support for combination cost function yet, blocked by:
	PrincetonUniversity#2712
CUDA testing needs synchronization of stateful params.

Signed-off-by: Jan Vesely <[email protected]>
jvesely added a commit to jvesely/PsyNeuLink that referenced this issue Jul 1, 2023
…t calculation

No support for combination cost function yet, blocked by:
	PrincetonUniversity#2712
CUDA testing needs synchronization of stateful params.

Signed-off-by: Jan Vesely <[email protected]>
jvesely added a commit to jvesely/PsyNeuLink that referenced this issue Jul 1, 2023
…t calculation

No support for combination cost function yet, blocked by:
	PrincetonUniversity#2712
CUDA testing needs synchronization of stateful params.

Signed-off-by: Jan Vesely <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant