Skip to content

Commit b43e703

Browse files
authored
Update docs/source/en/modular_diffusers/write_own_pipeline_block.md
1 parent 9fae382 commit b43e703

1 file changed

Lines changed: 0 additions & 1 deletion

File tree

docs/source/en/modular_diffusers/write_own_pipeline_block.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,6 @@ In this tutorial, we will focus on how to write a basic `PipelineBlock` and how
2121

2222
Before we dive into creating `PipelineBlock`s, we need to have a basic understanding of `PipelineState` - the core data structure that all blocks operate on. This concept is fundamental to understanding how blocks interact with each other and the pipeline system.
2323

24-
2524
In the modular diffusers system, `PipelineState` acts as the global state container that `PipelineBlock`s operate on - each block gets a local view (`BlockState`) of the relevant variables it needs from `PipelineState`, performs its operations, and then updates `PipelineState` with any changes.
2625

2726
While `PipelineState` maintains the complete runtime state of the pipeline, `PipelineBlock`s define what parts of that state they can read from and write to through their `input`s, `intermediates_inputs`, and `intermediates_outputs` properties.

0 commit comments

Comments
 (0)