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
Copy file name to clipboardexpand all lines: README.md
+12-122
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,18 @@ pip compile
18
18
19
19
torch_scatter needs gcc-c++ and python3-devel packages to build successfully.
20
20
21
+
with poetry you need to release the tensorflow-probability dependency from phasespace such that the line in ```.venv/lib/python3.10/site-packages/phasespace-1.8.0.dist-info/METADATA``` becomes
22
+
```
23
+
Requires-Dist: tensorflow-probability (>=0.15)
24
+
```
25
+
To achieve this, you may want to run
26
+
```
27
+
poetry add phasespace
28
+
```
29
+
prior to the installation of the other packages using
30
+
```
31
+
poe
32
+
21
33
changed module dependencies in phasespace:
22
34
23
35
before:
@@ -44,125 +56,3 @@ run kedro mlflow init
44
56
45
57
46
58
47
-
48
-
49
-
## Overview
50
-
51
-
This is your new Kedro project, which was generated using `Kedro 0.17.7`.
52
-
53
-
Take a look at the [Kedro documentation](https://kedro.readthedocs.io) to get started.
54
-
55
-
## Rules and guidelines
56
-
57
-
In order to get the best out of the template:
58
-
59
-
* Don't remove any lines from the `.gitignore` file we provide
60
-
* Make sure your results can be reproduced by following a [data engineering convention](https://kedro.readthedocs.io/en/stable/12_faq/01_faq.html#what-is-data-engineering-convention)
61
-
* Don't commit data to your repository
62
-
* Don't commit any credentials or your local configuration to your repository. Keep all your credentials and local configuration in `conf/local/`
63
-
64
-
## How to install dependencies
65
-
66
-
Declare any dependencies in `src/requirements.txt` for `pip` installation and `src/environment.yml` for `conda` installation.
67
-
68
-
To install them, run:
69
-
70
-
```
71
-
kedro install
72
-
```
73
-
74
-
## How to run your Kedro pipeline
75
-
76
-
You can run your Kedro project with:
77
-
78
-
```
79
-
kedro run
80
-
```
81
-
82
-
## How to test your Kedro project
83
-
84
-
Have a look at the file `src/tests/test_run.py` for instructions on how to write your tests. You can run your tests as follows:
85
-
86
-
```
87
-
kedro test
88
-
```
89
-
90
-
To configure the coverage threshold, go to the `.coveragerc` file.
91
-
92
-
## Project dependencies
93
-
94
-
To generate or update the dependency requirements for your project:
95
-
96
-
```
97
-
kedro build-reqs
98
-
```
99
-
100
-
This will copy the contents of `src/requirements.txt` into a new file `src/requirements.in` which will be used as the source for `pip-compile`. You can see the output of the resolution by opening `src/requirements.txt`.
101
-
102
-
After this, if you'd like to update your project requirements, please update `src/requirements.in` and re-run `kedro build-reqs`.
103
-
104
-
[Further information about project dependencies](https://kedro.readthedocs.io/en/stable/04_kedro_project_setup/01_dependencies.html#project-specific-dependencies)
105
-
106
-
## How to work with Kedro and notebooks
107
-
108
-
> Note: Using `kedro jupyter` or `kedro ipython` to run your notebook provides these variables in scope: `context`, `catalog`, and `startup_error`.
109
-
>
110
-
> Jupyter, JupyterLab, and IPython are already included in the project requirements by default, so once you have run `kedro install` you will not need to take any extra steps before you use them.
111
-
112
-
### Jupyter
113
-
To use Jupyter notebooks in your Kedro project, you need to install Jupyter:
114
-
115
-
```
116
-
pip install jupyter
117
-
```
118
-
119
-
After installing Jupyter, you can start a local notebook server:
120
-
121
-
```
122
-
kedro jupyter notebook
123
-
```
124
-
125
-
### JupyterLab
126
-
To use JupyterLab, you need to install it:
127
-
128
-
```
129
-
pip install jupyterlab
130
-
```
131
-
132
-
You can also start JupyterLab:
133
-
134
-
```
135
-
kedro jupyter lab
136
-
```
137
-
138
-
### IPython
139
-
And if you want to run an IPython session:
140
-
141
-
```
142
-
kedro ipython
143
-
```
144
-
145
-
### How to convert notebook cells to nodes in a Kedro project
146
-
You can move notebook code over into a Kedro project structure using a mixture of [cell tagging](https://jupyter-notebook.readthedocs.io/en/stable/changelog.html#release-5-0-0) and Kedro CLI commands.
147
-
148
-
By adding the `node` tag to a cell and running the command below, the cell's source code will be copied over to a Python file within `src/<package_name>/nodes/`:
149
-
150
-
```
151
-
kedro jupyter convert <filepath_to_my_notebook>
152
-
```
153
-
> *Note:* The name of the Python file matches the name of the original notebook.
154
-
155
-
Alternatively, you may want to transform all your notebooks in one go. Run the following command to convert all notebook files found in the project root directory and under any of its sub-folders:
156
-
157
-
```
158
-
kedro jupyter convert --all
159
-
```
160
-
161
-
### How to ignore notebook output cells in `git`
162
-
To automatically strip out all output cell contents before committing to `git`, you can run `kedro activate-nbstripout`. This will add a hook in `.git/config` which will run `nbstripout` before anything is committed to `git`.
163
-
164
-
> *Note:* Your output cells will be retained locally.
165
-
166
-
## Package your Kedro project
167
-
168
-
[Further information about building project documentation and packaging your project](https://kedro.readthedocs.io/en/stable/03_tutorial/08_package_a_project.html)
0 commit comments