Brewtarget / brewtarget

Main brewtarget source code repository.
GNU General Public License v3.0
312 stars 134 forks source link

Seperate process and equipment #427

Open pricelessbrewing opened 5 years ago

pricelessbrewing commented 5 years ago

So along the lines of #204, and in the idea of increasing support for process steps, will also correspondingly need to add support for more variable ingredient timing of additions.

ie Add dry hops at fermentation step XXX

ie grains at mash step XX (late grain additions, reiterative mashing etc).

ie add bacteria or brett at fermentation step XX

ie add bacteria at mash step XX for souring wort.

In order to do this I was thinking we could seperate the ingredients on the left, and put the processes on the right (mash, boil/whirlpool/chilling, and fermentation would be the top 3).

seperating process steps

This would allow us to support a lot of modern brewing techniques that most software has not supported in the best way, or else just ignored all together. It would also put brewtarget in a good place to transition to #388 easily as I've been working on getting most of this in place for that project.

pricelessbrewing commented 5 years ago

1) Boil: Have a user input for boil length, and temperature.

Will clean equipment profile ( I'm not a fan of tying equipment and processes' together).

Will allow for pasteurization steps which are fairly common in sour/funky/farmhouse brewing as well as raw ales where the wort is not boiled.

2) Whirlpool/chilling.

With more and more hop additions moving to sub boiling temps, this is becoming more and more important. Mimic the mash layout, step time/temp and ramp time/temp. At which point the new whirlpool IBU formula should be able to easily modify it for variable times and temps using the articles posted in the related issue #414.

3) Fermentation.

The current placement in "extras" seems kinda strange as it is. Moving this in line with mash as a process step makes sense. It will also allow for more clarity and make it more evident to the users.