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

First wort hop adjustment too high by a factor of 100 #177

Closed
Copper280z opened this issue Feb 10, 2016 · 9 comments
Closed

First wort hop adjustment too high by a factor of 100 #177

Copper280z opened this issue Feb 10, 2016 · 9 comments
Assignees
Milestone

Comments

@Copper280z
Copy link

For example, half an ounce of citra in a 5.5 gallon batch with a 60 min boil outputs a reasonable 19.5 IBU, changing that to first wort results in 1,948.2 IBU, which seems high.

image
image

Edit: I just found the IBU adjustments and they're set to 10,000 for FW and mash. I have not fiddled with these, but I did change units from metric to imperial at the start. Seems like this is just a bad initial config. Also, the units for this adjustment are unclear that it's percent and not a multiplier.

@rocketman768 rocketman768 changed the title Changing hop use to first wort results in nonsensical IBU number First wort hop adjustment too high by a factor of 100 Feb 10, 2016
@rocketman768
Copy link
Member

Thanks!

@rocketman768 rocketman768 added this to the v2.3.1 milestone Feb 10, 2016
rocketman768 added a commit to rocketman768/brewtarget that referenced this issue Feb 10, 2016
@rocketman768 rocketman768 self-assigned this Feb 10, 2016
rocketman768 added a commit that referenced this issue Feb 10, 2016
Fixes #177: first wort hop adjustment 100x too high
@punkrawkgeek
Copy link

Was just wondering if this was still being worked on or not...

@dpettersson
Copy link
Contributor

This issue is closed since 2016-02-10.
I assume that it was solved by that time since @rocketman768 merged and closed it.

May i ask if the problem has returned?

@punkrawkgeek
Copy link

first wort

Just doesn't look right... I am also running the Linux 64 version...

@jawsdaws
Copy link
Contributor

Are you running 2.3.0? It looks like this wasn't fixed until 2.3.1.

@punkrawkgeek
Copy link

@jawsdaws Where do I get 2.3.1?? I've looked everywhere... :\

@jawsdaws
Copy link
Contributor

@punkrawkgeek
Copy link

@jawsdaws Uninstalled and reinstalled the newest one. Still the same thing... Any other ideas???

@jpkilpi
Copy link

jpkilpi commented Nov 12, 2017

I can confirm that the issue is still there in 2.3.1.

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

6 participants