# Recipes Overview

A recipe is a timeline of tasks in a linear order. A recipe can be for a specific plant and for specific CEM Module, as modules could have different attributes and tools.

# Recipe Timeline

When a recipe is started, the starting time and date will be the UNIX timestamp and all the other tasks will be based on that. Recipes will be in a database and can be cloned and adopted to fine tune some settings and test.

Following questions need to be discussed.

We will need to talk about how to handle interrupts by the user. What happens if a task during a running recipe is stopped? Is ther e a resume function?

Should there be a function to overwrite the temperature for all future tasks? Maybe a bulk edit function.

We will probably store a recipe in the database, as it is easier to update it and connect it to the interface. To exchange recipes there should be some kind of JSON File.

# Datebase Format for recipe

# Step

A recipe conists of timed steps. Each steps has values and routines.

# Routine

A routine has an interval and a duration time. This means it is repeating tasks for a certain amount of times every interval. Best example would be the ebb flow irrigation of the plants.