as it will lead to API inconsistencies. If you fundamentally disagree with a design choice, please open a Feedback issue instead so that it can be discussed whether a certain design pattern/design choice shall be changed everywhere in the library and whether we shall update our design philosophy. Consistency across the library is very important for us. Please make sure to add links to the original codebase/paper to the PR and ideally also ping the original author directly on the PR so that they can follow the progress and potentially help with questions. If you are unsure or stuck in the PR, don’t hesitate to leave a message to ask for a first review or help.  Copied from mechanism A unique and important feature to understand when adding any pipeline, model or scheduler code is the # Copied from mechanism. You’ll see this all over the Diffusers codebase, and the reason we use it is to keep the codebase easy to understand and maintain. Marking code with the # Copied from mechanism forces the marked code to be identical to the code it was copied from. This makes it easy to update and propagate changes across many files whenever you run make fix-copies. For example, in the code example below, StableDiffusionPipelineOutput is the original code and AltDiffusionPipelineOutput uses the # Copied from mechanism to copy it. The only difference is changing the class prefix from Stable to Alt.   Copied # Copied from diffusers.pipelines.stable_diffusion.pipeline_output.StableDiffusionPipelineOutput with Stable->Alt