Brew Vision: Brewing Pipeline Management Application

[poptarts]

If i package 2 kegs from a ten gallon batch on the same date, but only start drinking one of them, is there a way to make the pipeline know that Im not drinking the second keg yet?

Use the split batch, so do the first package, say its 5 gallons or w/e you keg size is, then go back to the brew, hit split batch and package another keg off of it. Then you will have 2 packages of the same beer, and you can put one on tap one not on tap etc.

 

[kpr121]

I think i set it up correctly as you explained. Batch was split and packaged into two kegs. First keg was put on tap. Second keg was not. But in pipeline its showing them both being drank currently and ending at same time.

Maybe I'm doing something wrong, but I would think that the second keg would have an estimated start drinking date on the day that the first keg is estimated kicked.

I've attached a screenshot

 

[poptarts]

I look at the database and see what you having going on, looks like it might be a bug though.

 

[poptarts]

I think i set it up correctly as you explained. Batch was split and packaged into two kegs. First keg was put on tap. Second keg was not. But in pipeline its showing them both being drank currently and ending at same time.

Maybe I'm doing something wrong, but I would think that the second keg would have an estimated start drinking date on the day that the first keg is estimated kicked.

I've attached a screenshot

Ok so looking at the database for your brown trout stout.
It appears you did use the split package correctly and have 2 kegs of that beer that were packaged on 2/14/2015

There are no drinks reported for either beer at the moment.

Your brew says it will condition for 1 week, and that has passed. So Im assuming the past action for both of them is ageing. And the pipeline is telling you that both are ready to drink and you can start drinking bother of them right now. The pipeline has little info to go off of so it assumes if you start drinking them today they will be gone when it says. The pipeline treats each keg as its own beer so it has no way of knowing that you wont drink the one till the other is gone so it is estimating that they will each run out at the same time. If you want them to be linked in that way, it may be best to just say you have a 10 gallon keg instead of 2 5 gallon kegs.
What If I coded a way to link kegs, or set up some way to say you wont drink x till x is gone or something, cause thats realistic, I mean I only have 4 taps so I cant drink any of my kegged beers till one on tap is gone?
Thoughts suggestions? But, as of now it is behaving as intended but maybe not what we want.

 

[kpr121]

I have no clue how to program so not sure how much work this is but I think it would be nice if you had a 'tap date' where you could assign each keg's tap date. Because sometimes people might tap both kegs off a ten gallon batch at the same time (for instance, they are testing the difference in yeast or dry hops), and other times you want to piggy back the kegs one after another.

Sorry if I'm being a PITA~! I can truly see myself using this type of software for the long haul! If you had a brewsmith like recipe calculator inbedded it would be the bee's knees!

 

[kpr121]

Ok so looking at the database for your brown trout stout.
It appears you did use the split package correctly and have 2 kegs of that beer that were packaged on 2/14/2015

There are no drinks reported for either beer at the moment.

Your brew says it will condition for 1 week, and that has passed. So Im assuming the past action for both of them is ageing. And the pipeline is telling you that both are ready to drink and you can start drinking bother of them right now. The pipeline has little info to go off of so it assumes if you start drinking them today they will be gone when it says. The pipeline treats each keg as its own beer so it has no way of knowing that you wont drink the one till the other is gone so it is estimating that they will each run out at the same time. If you want them to be linked in that way, it may be best to just say you have a 10 gallon keg instead of 2 5 gallon kegs.
What If I coded a way to link kegs, or set up some way to say you wont drink x till x is gone or something, cause thats realistic, I mean I only have 4 taps so I cant drink any of my kegged beers till one on tap is gone?
Thoughts suggestions? But, as of now it is behaving as intended but maybe not what we want.

Thanks for the input. Im not sure what the best way to go about it would be, but would prefer the function to be able to individually inventory kegs (i.e. not pretend that its one 10 gallon keg).

Maybe a tap priority list or something?

Can you simply make it so that a beer thats not tapped cannot be consumed?

 

[poptarts]

How about this logic.
In pipeline if currently all taps are full, it wont assume you will start drinking x beer until the next tap blows.
So say we have 4 taps, the 4 beers on tap are estimated to last till 3/15, 3/20, 2/30 and 5/30
Outside of those 4 the pipeline will guess you wont start drinking any kegged beers till 2/30 regardless if they are ready or not.

 

[poptarts]

Can you simply make it so that a beer thats not tapped cannot be consumed?

This is true for kegged beers already, but I will carry logic over to the pipeline estimation algorithm. Thanks for all the feedback, love it.

 

[kpr121]

How about this logic.
In pipeline if currently all taps are full, it wont assume you will start drinking x beer until the next tap blows.
So say we have 4 taps, the 4 beers on tap are estimated to last till 3/15, 3/20, 2/30 and 5/30
Outside of those 4 the pipeline will guess you wont start drinking any kegged beers till 2/30 regardless if they are ready or not.

I like this logic.

Great stuff you got here! I'll be sure to play around with it a little bit more and let you know of any other bugs/comments.

Gonna have to log a couple "drinks" tonight, you know, for testing purposes.

 

[poptarts]

Agree lol

 

[sandyeggoxj]

Nice. I'm all setup. Looks pretty cool. Took me a bit to figure it out. I will be kegging a DIPA in about 8 days and that will be good to test this out. I will have to keep the tablet handy and use it to log the drinks and see how well it works.

 

[poptarts]

Nice. I'm all setup. Looks pretty cool. Took me a bit to figure it out. I will be kegging a DIPA in about 8 days and that will be good to test this out. I will have to keep the tablet handy and use it to log the drinks and see how well it works.

My 50$ tablet I bought just showed up, got it for one reason and one reason only.

 

[forge33]

My 50$ tablet I bought just showed up, got it for one reason and one reason only.

Nice, I need to find a good place for mine.

http://imgur.com/dPSWml8

Mounted between the taps? xD

 

[poptarts]

Ok pretty jealous of your setup. I would maybe just get a tablet stand and set it on the bar somewhere, maybe by the water bottle?

 

[MarshmallowBlue]

Oh I saw your labels in the label thread. Those are great.

 

[forge33]

Ok pretty jealous of your setup. I would maybe just get a tablet stand and set it on the bar somewhere, maybe by the water bottle?

Good idea, half the countertop is still removable so i can still pass a wire if I need to for power

 

[poptarts]

yea I picked up a 10ft usb charging cable on amazon for like 5$, hooked up a no sleep app on the tablet, works like a champ.

 

[poptarts]

I like this logic.

Great stuff you got here! I'll be sure to play around with it a little bit more and let you know of any other bugs/comments.

Gonna have to log a couple "drinks" tonight, you know, for testing purposes.

I slid in that logic, so if a beer is kegged and all taps are full, the pipeline will not guess you will be drinking it until the soonest tapped beer is gone. However if the beer is not packaged it wont because I dont know if it will be bottled or kegged. I think I will add a field to brew so you can mark if you intend to keg or not.

 

[poptarts]

Just pushed a ton more patches and updates, lots more features on the way.

 

[kpr121]

Hey poptarts, im getting an error when going to pipeline, copied the log below (edit: deleted from this thread to avoid cluttering, will send through the contact page). Not sure if its a bug on my inputs or what.

I am loving what you are doing here, especially with the upcoming grain/hops inventory tracking, recipe builder, and of course the taplist/pipeline feature.

Cheers

 

[poptarts]

Did you figure out your issue? PS Untappd Integration Phase 1 has been released.

 

[kpr121]

No pipeline not working for me. Screenshot

View attachment ImageUploadedByHome Brew1425697082.866051.jpg

 

[poptarts]

http://brew.vision/pipeline/225
Hows that for you there boss. You and that stout make a good QA team. Let me know if anything else is acting stupid like that. You should never see those errors.
Cheers

 

[kpr121]

Your the boss!

 

[dyutdy]

Haha. That's pretty awesome! I usually just use my brain app when it comes to inventory management though. Sometimes I use the pencil and paper app too.

 

[poptarts]

Just pushed a ton of documentation.

 

[ColoHox]

Whats the deal with these copy-paste posts from different users?

 

[poptarts]

Not sure, I reported em earlier but not sure what they are trying to do.

 

[poptarts]

Just pushed another boat of code, Hop, Yeast, Fermentable, Misc, and Commercial Beer inventory tracking.

 

[kpr121]

Love it. Gonna have a place to enter alpha acids for hops inventory?

Maybe also add a option to add an "other" inventory for fermentables, hops, yeast? Looks like you got just about all the bases covered but may be nice.