brewtarget-devs team mailing list archive

[mik firestone <mikfire@xxxxxxxxx>]

I hadn't thought to associate with the equipment profile. I was just
storing it as options. But I like that idea.

Brewer's friend offers "decoction", "fly sparge", "infusion", "sparge" and
"temperature" for mash steps. I was resisting the temptation to make fly
sparge and batch sparge as different things. In my mind, there is a sparge
step. It would be the settings that would define if it were a fly or batch
sparge step.

Mik


On Wed, Apr 9, 2014 at 2:02 PM, Philip Lee <rocketman768@xxxxxxxxx> wrote:

> Simplifying and compartmentalizing that info sounds like a good idea to
> me. I also agree that the way we do sparging is broken.
>
> Is the process attached to the equipment? I can imagine I might have
> different processes for different sets of equipment.
>
> How does the other brewing software handle this kind of info?
>
>
> On Tue, Apr 8, 2014 at 10:20 PM, mik firestone <mikfire@xxxxxxxxx> wrote:
>
>> One of the things I would like to include in v2.1 is a new options tab
>> called "Process" where you can define things like you crush your own
>> grains, you add grain to water, you fly sparge, etc.
>>
>> Depending on what you have selected, it will have different effects. For
>> example, stating that you crush your own grain adds a new step saying to
>> crush the grains and modifies later steps to simple say "add crushed grain".
>>
>> Sparging is presenting me a problem. Currently, the only way we know a
>> step is a sparge step is that the name of the step is "Final Batch Sparge".
>> This fails on numerous levels: I am fairly certain our European brewing
>> brethren do not spell it "final batch sparge"; changing the name of the
>> step breaks the mash wizard; and I just sort of cringe at doing this.
>>
>> I would propose we deviate from the BeerXML standard* and create a new
>> mash type called "Sparge" that we can use to show a mash step is a sparge.
>> I will need to contemplate how this will affect the interface and if there
>> is any way to retroactively guess if a step is a sparge or not. When
>> spitting the recipe out to BeerXML, we will change the type from "Sparge"
>> to "Infusion" so that we retain compatibility with the spec.
>>
>> I want to make sure this idea has merit and meets with general approval
>> before putting a lot of work into it. If it does, I will submit the
>> necessary tickets and split that activity out from my current playing
>> around. If it doesn't, I will grumble a lot and continue with the text
>> parsing.
>>
>> Mik
>>
>> * - In a broader sense, I really would prefer to simply ditch the spec
>> entirely in the database and only worry about it in the XML output routines.
>>
>> --
>> In a world of ninja v. pirate, I pilot a Gundam
>>
>> --
>> Mailing list: https://launchpad.net/~brewtarget-devs
>> Post to     : brewtarget-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~brewtarget-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Philip G. Lee
> rocketman768@xxxxxxxxx
>
> --
> Mailing list: https://launchpad.net/~brewtarget-devs
> Post to     : brewtarget-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~brewtarget-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
In a world of ninja v. pirate, I pilot a Gundam