Skip to content
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

Updated title #21

Merged
merged 5 commits into from
Aug 29, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions openeo/NDVI_Timeseries.ipynb

Large diffs are not rendered by default.

24 changes: 12 additions & 12 deletions openeo/UDF.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
"cells": [
{
"cell_type": "raw",
"metadata": {
"collapsed": false
},
"source": [
"---\n",
"execute:\n",
Expand All @@ -11,23 +14,20 @@
" code-fold: false\n",
"jupyter: python3\n",
"---"
],
"metadata": {
"collapsed": false
}
]
},
{
"cell_type": "markdown",
"metadata": {
"collapsed": false
},
"source": [
"# User-Defined Functions (UDF)\n",
"# User-Defined Functions (UDF) in openEO\n",
"\n",
"While openEO supports a wide range of pre-defined processes and allows to build more complex user-defined processes from them, you sometimes need operations or algorithms that are not (yet) available or standardized as openEO process. User-Defined Functions (UDF) is an openEO feature (through the run_udf process) that aims to fill that gap by allowing a user to express (a part of) an algorithm as a Python/R/… script to be run back-end side.\n",
"\n",
"Though several types of algorithms can be used as UDF applications, in this notebook, we showcase a simple example of how to work with UDF using the openEO Python Client library."
],
"metadata": {
"collapsed": false
}
]
},
{
"cell_type": "code",
Expand Down Expand Up @@ -230,9 +230,9 @@
],
"metadata": {
"kernelspec": {
"display_name": "OpenEO",
"display_name": "openeo_py",
"language": "python",
"name": "openeo"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that changing the kernel name might trigger a "Select kernel" popup to users that open this notebook on CDSE jupyterlab when the name does not exist there.

In this case kernel python3 does exist on CDSE jupyterlab, but it's the base python and doesn't have any of the importabt packages, like openeo installed I think

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh sorry for confusion @soxofaan. Changes were made locally and didn't realise that change in markdown could also trigger it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes updated

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYI: under #22 I added a kernel check script that now runs as pre-commit and github actions workflow

"name": "python3"
},
"language_info": {
"codemirror_mode": {
Expand All @@ -244,7 +244,7 @@
"name": "python",
"nbconvert_exporter": "python",
"pygments_lexer": "ipython3",
"version": "3.8.16"
"version": "3.9.16"
}
},
"nbformat": 4,
Expand Down
12 changes: 6 additions & 6 deletions openeo/UDP.ipynb

Large diffs are not rendered by default.