The FrogPad
 
A forum to get help or talk about Roastmaster…or anything else coffee.

Additional cupping functionality  (Read 2514 times)

nimitzg

  • (2 Posts)
  • *
  • Karma: 0
    • View Profile
I think it would be very helpfull to have the cupping score lay on a star-shape cupping chart rather then the current ranking method alone.
Also if it will be possible to have both effecting each other would be great.
I found the visualization of the cupping very helpfull while deciding on a blend.
The ability to compare simultaneously a few charts one near the other can be much helpfull as well while building a blend.

Danny Hall

  • (363 Posts)
  • *****
  • Karma: 4
    • View Profile
    • Rainfrog
Hello. I agree - not only just one at a time, but spider charts are excellent for overlaying several coffees at once to visually see the differences. I've been hashing out ideas in my head for cuppings over the last couple of months.

I plan to expand on cuppings soon, and that may very well entail different styles of cuppings - i.e. expanded attributes. Some charts can get rather detailed. What attributes are you interested in personally?

Starting small, though, I'd like to offer a spider chart as a means for entering data as well. Seems it would be more fun, and less tedious, to edit values via dragging a node on a chart. Nodes could be locked to, say, .25 increments to keep it tidy.

Thanks for the input!

Danny

tburres

  • (16 Posts)
  • *
  • Karma: 0
    • View Profile
Hey Danny,

I am fairly new to Roastmaster and roasting - I have a new drum roaster on the way and plan to do all my data logging etc using Roastmaster - I would like to keep all my cupping notes in one place, including when I sample roasts from others.  I assume I can load a bean and identify it in the notes to cover this, but thought it might be nice to have a specific set up for this case.

Danny Hall

  • (363 Posts)
  • *****
  • Karma: 4
    • View Profile
    • Rainfrog
Hi

Interesting idea. The update I'm working on now is about to enter beta.

For the following update, I think I'm going to implement a very interesting idea another user proposed - the ability to name a roast. His idea was that if a name is entered, that name would be used in the lists throughout the app to identify that roast. If not, it would simply use the description string that is currently displayed.

I loved that idea, and ashamed I never though of it myself. :) I think, though, that it would be equally beneficial for cuppings, and is probably in line with what you're asking for.

An example for a roast would be "Dark roast for Marie", instead of "Illubabor Camp Cooperative". For a cupping, maybe "Birthday roast from John", or whatever makes sense to you.

What do you think?

Anderson

  • (12 Posts)
  • *
  • Karma: 0
    • View Profile
Dear Danny Hall

Yes! I am very eager to have  the named function also ;D

I can't wait the update anymore :D

Thank you!


tburres

  • (16 Posts)
  • *
  • Karma: 0
    • View Profile
Could work - What I would be looking for is to not have to set up a roaster, a profile, a bean vendor, then a bean  - I would just want to load the details on one screen and be able to add notes regarding my impressions of the flavor for later comparison when I roast a similar coffee.   I am sure I was doing it the hard way as I am still getting used to all the features of Roastmaster, but I ended up loading a lot of data so that I could have a place to say "wow, I totally got the blackberry in that!" 


Thanks again!

Danny Hall

  • (363 Posts)
  • *****
  • Karma: 4
    • View Profile
    • Rainfrog
Funny, when I think about features, I picture code in my head. I remember picturing the code for cuppings when reading your post, which I wrote to handle raw beans (as well as blends and roasts), forgetting that I disallow that in actual usage. The reasons are simply to dissuade users from instinctively choosing a bean, when a roast is actually the better choice.

I can clearly see what you mean now, and how it would be helpful. I'll have a look at this, and see what code ramifications are involved in allowing cuppings of green beans. I can create an opt-in preference, to eliminate the chances of folks learning bad habits, but still allowing the functionality for situations where it can be very beneficial to have that reference.
« Last Edit: August 22, 2014, 04:51:33 PM by Danny Hall »