vograno

This bug is still there (current stable) and `update_process.py` fails with the same error on a gpu-less computer. Does anyone know a workaround?

> This seems interesting. I assume you'd want to wire it through to the HamiltonNode that's returned from driver.list_available_variables()? Yes

> ... The internal `FunctionGraph` does have the bi-directional linking, so the building blocks are there. To me it sounds like you'd want to change a bit of how the...

Let me propose a less fascinating, but simpler example to work with. 1. There are two kinds of nodes, Red and Blue. 2. Let y denote the node ouput, and...

> To clarify, you wouldn't expect the following to work normally though right? > > ```python > # this should not work > result = driver.execute(final_vars=['output_node'], inputs={"x": {"some": "value"}}) >...

Thank you guys. I appreciate your receptiveness and responsiveness. Take your time. A couple of notes just in case 1. For the function, consider leveraging the `inspect` module approach, the...

But I wanted to know the name of the function parameter which the source binds to. This doesn't affect DAG execution, but it does affect the function-algebra stuff you mentioned...

Here is a specific example ``` @parameterize( o1=dict(x=source('fun_x_input')), ) def fun(x: dict, i: int) -> dict: return x ``` Assume that 'fun_x_input' is an input node and it feeds into...

Are you saying there will be a `var` named 'fun' even though the generated node name is 'o1'?

UPDATE: let me run your example to see what info I get. I still need to know the function name and signature and the exact argument it is wired too....