I can be a tremendous geek at times. I waste far too much time at the computer, and when I hear about a new widget or gadget, I want to try it out and play with it. The new toy: a widget that announces how much (or how little) I've spun.
For those wondering what a widget is, it's basically a little bit of HTML code that can be inserted into a web page that links to another page that feeds data back to the first page. The first widget I played with extensively was the KnitMeter, a little widget that announced how much one had knit (or later, crocheted) during a month. I started listing my knitting projects in March 2009 and, for about 14 months, was very good about updating how much I had knit on each project. Then I stopped.
A couple weeks ago, someone on Ravelry (the source of another widget) mentioned that there was now a version of the KnitMeter for spinners. I checked it out this morning and it's pretty cool! I added the SpinMeter to my profile page on Ravelry, and this evening added it to my blog--it's over there, on the right. I figured out which yarns I had spun so far this year, added them to the SpinMeter, and that number is the number of yards of finished yarn I've produced.
And that's where the "complication" comes in. That pretty large number is the number of finished yarns--usually 2-ply--that I've spun. The amount of yarn I've actually spun is that amount, plus about 10% (to account for shrinkage that occurs when plying and when wet-finishing), multiplied by the number of plies (usually 2) plus the plying run itself. The formula works out like this
X = Y x .10 x 3
So the new toy should keep me on my toes, or keep my toes on the treadles. Right now I've finished spinning 4.1 oz. of very pretty Romeldale that needs to be plied, and I filled one bobbin of the silver Bond ram/Cotwold hogget blend this morning at my guild meeting. Tomorrow or Tuesday will be a marathon plying session (I need to empty bobbins prior to leaving for the Black Sheep Gathering), and then the amount on the SpinMeter should jump again.
No comments:
Post a Comment