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
Add the "tensorflow-model-analysis" package to the notebook images #544
Add the "tensorflow-model-analysis" package to the notebook images #544
Conversation
More information about this package is [here](https://github.com/tensorflow/model-analysis).
/cc jlewi |
@@ -206,6 +206,9 @@ RUN conda_packages=$(conda list -e | cut -d '=' -f 1 | grep -v '#' | sort) && \ | |||
python -m ipykernel install --user && \ | |||
echo "${pip_only_packages}" | xargs -n 1 -I "{}" /bin/bash -c 'pip install --no-cache-dir {} || true' && \ | |||
pip install --no-cache-dir tensorflow-transform && \ | |||
pip install --no-cache-dir tensorflow-model-analysis && \ | |||
jupyter nbextension install --py --symlink tensorflow_model_analysis --system && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why --symlink?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I included it was that I started with the instructions from the model-analysis README which uses --symlink
, and that part doesn't cause issues in our build (the default install location did cause issues, but that is orthogonal).
From what I understand, passing in --symlink
is considered a best-practice since it saves space on non-Windows systems. However, I don't have a strong preference one way or the other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/retest |
Installing the `tensorflow_model_analysis` nbextension results in the `tensorflow` package being imported. For the CPU image this is fine, but in the GPU image tensorflow relies on `libcuda`, which is not installed (it is expected to be mapped into the running container from the host OS). To work around this, we take the `libcuda.so` stub library (which is meant for building things that link against libcuda), and temporarily make it be loaded when something tries to load `libcuda.so.1`.
…arjur/tensorflow-model-analysis
Added a workaround to the issue where importing tensorflow during the build of the GPU image was failing. PTAL |
@ojarjur Could you add a comment in the Dockerfile explaining the work around? |
…arjur/tensorflow-model-analysis
…rflow-model-analysis extension
@jlewi Done. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jlewi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Update tf jupter notebook images to include tfma (from #544) (#570) * Update tf jupter notebook images to include tfma (from #544) tf1.4 gpu image has issues building with the latest tfma, so that's not updated in this PR /cc @jlewi /cc @ojarjur * Don't update tf images older than 1.6 * Moved OAuth secret from param to named secret (#572)
…ubeflow#544) * Add the "tensorflow-model-analysis" package to the notebook images More information about this package is [here](https://github.com/tensorflow/model-analysis). * Make the tensorflow library importable when building the GPU image. Installing the `tensorflow_model_analysis` nbextension results in the `tensorflow` package being imported. For the CPU image this is fine, but in the GPU image tensorflow relies on `libcuda`, which is not installed (it is expected to be mapped into the running container from the host OS). To work around this, we take the `libcuda.so` stub library (which is meant for building things that link against libcuda), and temporarily make it be loaded when something tries to load `libcuda.so.1`. * Document the LD_LIBRARY_PATH workaround used for installing the tensorflow-model-analysis extension
…ubeflow#570) * Update tf jupter notebook images to include tfma (from kubeflow#544) tf1.4 gpu image has issues building with the latest tfma, so that's not updated in this PR /cc @jlewi /cc @ojarjur * Don't update tf images older than 1.6
…ubeflow#544) * Add the "tensorflow-model-analysis" package to the notebook images More information about this package is [here](https://github.com/tensorflow/model-analysis). * Make the tensorflow library importable when building the GPU image. Installing the `tensorflow_model_analysis` nbextension results in the `tensorflow` package being imported. For the CPU image this is fine, but in the GPU image tensorflow relies on `libcuda`, which is not installed (it is expected to be mapped into the running container from the host OS). To work around this, we take the `libcuda.so` stub library (which is meant for building things that link against libcuda), and temporarily make it be loaded when something tries to load `libcuda.so.1`. * Document the LD_LIBRARY_PATH workaround used for installing the tensorflow-model-analysis extension
…ubeflow#570) * Update tf jupter notebook images to include tfma (from kubeflow#544) tf1.4 gpu image has issues building with the latest tfma, so that's not updated in this PR /cc @jlewi /cc @ojarjur * Don't update tf images older than 1.6
* Ui changes trigger CI based on version * Make earlystop version in prow config
More information about this package is here.
This change is