Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fermentables wrong colour unit in default database #366

Open
jensnielsen opened this issue Mar 30, 2017 · 5 comments
Open

Fermentables wrong colour unit in default database #366

jensnielsen opened this issue Mar 30, 2017 · 5 comments

Comments

@jensnielsen
Copy link

Hi

I noticed a lot of my fermentables had their colour listed in the wrong unit so I scrapped my database and restored the default one (brewtarget/data/default_db.sqlite from develop branch) but I still have the same issue. I haven't checked them all but those I have checked are wrong. For example

And so on. The numbers are in Lovibond but shown and used as srm.

Or am I missing something? I'm on 2.3.0 for Windows.

@kapinga
Copy link
Contributor

kapinga commented Apr 1, 2017

Edit: Please disregard, this isn't exactly right (Lovibond and SRM are not equivalent), as explained in my comment below.


As far as I can tell, Lovibond is approximately equivalent to SRM (see BeerSmith and Wikipedia):

The SRM color is approximately equal to the old lovibond scale in most cases.

SRM is a more modern measurement than Lovibond, and has a well-defined quantitative measurement. To quote Wikipedia:

The Standard Reference Method or SRM[1] is one of several systems modern brewers use to specify beer color. Determination of the SRM value involves measuring the attenuation of light of a particular wavelength (430 nm) in passing through 1 cm of the beer, expressing the attenuation as an absorption and scaling the absorption by a constant (12.7 for SRM; 25 for EBC).

@jensnielsen
Copy link
Author

jensnielsen commented Apr 1, 2017

Nice, that's interesting. I based my knowledge of colours on this page, which has quite a big difference between SRM and L: https://www.brewtoad.com/tools/color-converter

The reason I discovered this is because I added a recipe for a clone beer and didn't get the colour the recipe told me I'd get (according to the slider in Brewtarget, I haven't actually checked the colour of a finished product) but if I change the colour values of the malts according to the Brewtoad formula it's spot on.

I did brew the clone beer in two versions, one according to the original recipe and one where I added some chocolate malt to get the Brewtarget slider to where I wanted it. I think the unmodified one is closer to the original but I will go and buy a bottle so I can compare. This of course doesn't prove anything but it's interesting...

But I guess we can agree Lovibond is obsolete and should not be used

@kapinga
Copy link
Contributor

kapinga commented Apr 1, 2017

tl;dr: Brewtarget is actually showing the Lovibond color of the malts/fermentables, even though it says SRM. The color calculations the correctly use these Lovibond color units to estimate the final beer color in SRM.


I answered too quickly last night, the situation is somewhat more complex than I thought. This StackExchange thread has a good discussion. Lovibond is still commonly used to measure malt color as you noted (at least in the US, I can't speak to elsewhere), but SRM (which relies on transmission through a liquid) is used for beer color. There are several formulas for estimating the final beer's SRM color based on the color of the malt, although the appropriate units for malt color aren't entirely clear.

Brewtarget takes all this into account (you can select which formula is used for calculating color in the options dialog). The BeerXML format (which Brewtarget is based on internally, for better or for worse) even notes that the color of malts should be recorded in Lovibond degrees (but SRM for liquid extract).

Without worrying about units for the moment, Brewtarget calculates the beer's color by adding up all the 'Malt Color Unit' (MCU) contribution of each fermentable (MCU = grain_color * lbs_grain / gal_water). The MCU value is then fed into whichever formula the user has chosen (by default Morey's approximation) to predict the SRM of the final beer. Morey notably did not explain in his post which units should be used to calculate MCU in the first place.

The question then is: what units are appropriate for calculating MCU? Brewtarget internally acts as if all fermentables have SRM color units, but I'm having trouble figuring out what color units should appropriately be used when calculating MCU. Although SRM and Lovibond are supposedly 'similar', Wikipedia later claims that the formula to convert them is:

SRM = 1.3546 x L - 0.76

This is similar for small numbers (5 L == 6 SRM), but definitely introduces significant differences at high levels of coloration. As far as I can tell, most calculations implicitly use the Lovibond color of the malt to get the MCU, so that seems like the correct calculation is:

Lovibond malt color -> MCU -> SRM beer color

Assuming that should be MCU calcuated using Lovibond units, then Brewtarget is doing the calculations correctly. The only problem then is that Brewtarget says that malt colors are in SRM when they are actually in degrees Lovibond. (There's a secondary problem that (liquid) extracts should probably be treated differently, but aren't as far as I can tell.)

@pricelessbrewing
Copy link
Contributor

@kapinga I think until we have more information on what MCU is supposed to use, some brief research shows it should probably be lovibond used in the fermentable database and the unit labels changed accordingly. I think it's better to be up front, and be wrong (potentially), then to misslabel the units we're using.

fermentables: lovibond

Beer color: srm.

@pricelessbrewing
Copy link
Contributor

Additionally, malsters always provide their color information in lovibond, not srm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants