py-why / py-why/EconML

Warnings In Tutorial DeepIV

Open
#606 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
4.8k
Forks
827
PR merge metrics
No merged PRs in 30d

Description

I am learning about this package and going through the (very helpful) tutorial for DeepIV

I pick up a warning in cell 6, indicating:

WARNING:tensorflow:
The following Variables were used a Lambda layer's call (lambda_8), but
are not present in its tracked objects:
  <tf.Variable 'dense_10/kernel:0' shape=(2, 128) dtype=float32>
  <tf.Variable 'dense_10/bias:0' shape=(128,) dtype=float32>
  <tf.Variable 'dense_11/kernel:0' shape=(128, 64) dtype=float32>
  <tf.Variable 'dense_11/bias:0' shape=(64,) dtype=float32>
  <tf.Variable 'dense_12/kernel:0' shape=(64, 32) dtype=float32>
  <tf.Variable 'dense_12/bias:0' shape=(32,) dtype=float32>
  <tf.Variable 'dense_13/kernel:0' shape=(32, 1) dtype=float32>
  <tf.Variable 'dense_13/bias:0' shape=(1,) dtype=float32>
It is possible that this is intended behavior, but it is more likely
an omission. This is a strong indication that this layer should be
formulated as a subclassed Layer rather than a Lambda layer.

Later steps continue to work so it is just a warning, but but hopefully it can be resolved.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with notebooks/Deep IV Examples.ipynb and reproduce the warning in cell 6. Inspect the Lambda layer associated with the reported variables and determine the intended correction; the work is done when the warning no longer appears and the later tutorial steps still run successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, tensorflow
Domain
documentation, machine-learning
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.