You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current way we onboard team members the visualization workflow is with the documentation in this repo, as well as the helpful-code directory that includes a notebook with code and more documentation, a python script, a requirements.txt file, and instructions for setting up a fresh python environment with the requirements.txt. For team members that are not very fluent with python and setting up environments, understanding the setup steps can be a hurdle. It would be extra helpful to set up a docker container to help onboard new team members. The docker work in progress in the viz-workflow repo may serve this purpose, but that workflow is more complicated with parallelization, and it will be improved over time. So the best way to onboard people may be to create a separate (lighter) docker container for this repo that stays unchanged over time, without unnecessary parallelization. This approach would assume that the user has beginner experience with docker, at least enough to know how to pull a published image.
Another option is to create a binder for the helpful-code notebook, and keep the requirements.txt setup for the script. After all, new team members will need to have an understanding of environments eventually.
The text was updated successfully, but these errors were encountered:
The current way we onboard team members the visualization workflow is with the documentation in this repo, as well as the
helpful-code
directory that includes a notebook with code and more documentation, a python script, arequirements.txt
file, and instructions for setting up a fresh python environment with therequirements.txt
. For team members that are not very fluent with python and setting up environments, understanding the setup steps can be a hurdle. It would be extra helpful to set up a docker container to help onboard new team members. The docker work in progress in theviz-workflow
repo may serve this purpose, but that workflow is more complicated with parallelization, and it will be improved over time. So the best way to onboard people may be to create a separate (lighter) docker container for this repo that stays unchanged over time, without unnecessary parallelization. This approach would assume that the user has beginner experience with docker, at least enough to know how to pull a published image.Another option is to create a binder for the
helpful-code
notebook, and keep therequirements.txt
setup for the script. After all, new team members will need to have an understanding of environments eventually.The text was updated successfully, but these errors were encountered: