remove manual execution from recipes user guide
@@ -91,59 +91,3 @@ with beam.Pipeline() as p:
By default the pipeline runs using Beam's [DirectRunner](https://beam.apache.org/documentation/runners/direct/).
See [runners](https://beam.apache.org/documentation/#runners) for more.
-
-## Manual Execution
-
-```{warning}
-We are considering dropping manual execution from the Pangeo Forge API.
-```
-
-A recipe can be executed manually, step by step, in serial, from a notebook
-or interactive interpreter. The ability to manually step through a recipe
-is very important for developing and debugging complex recipes.
-There are four stages of recipe execution.
-
-### Stage 1: Cache Inputs
-
-Recipes may define files that have to be cached locally before the subsequent
-steps can proceed. The common use case here is for files that have to be
-extracted from a slow FTP server. Here is how to cache the inputs.
-
-```{code-block} python
-for input_name in recipe.iter_inputs():
- recipe.cache_input(input_name)
-```
-
-If the recipe doesn't do input caching, nothing will happen here.
-
-### Stage 2: Prepare Target
-
-Once the inputs have been cached, we can get the target ready.
-Preparing the target for writing is done as follows:
-
-```{code-block} python
-recipe.prepare_target()
-```
-
-For example, for Zarr targets, this sets up the Zarr group with the necessary
-arrays and metadata.
-This is the most complex step, and the most likely place to get an error.
-
-### Stage 3: Store Chunks
-
-This is the step where the bulk of the work happens.
-
-```{code-block} python
-for chunk in recipe.iter_chunks():
- recipe.store_chunk(chunk)
-```
-
-### Stage 4: Finalize Target
-
-If there is any cleanup or consolidation to be done, it happens here.
-
-```{code-block} python
-recipe.finalize_target()
-```
-
-For example, consolidating Zarr metadata happens in the finalize step.
