|
Are you using backprop or RNT?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark,
The Stanford system uses a "Recursive Neural Tensor Network" to train its sentiment model. The sentences are first parsed and processed into a set of "binary trees" with sentiment scores (0, 1, 2 for -ve, neutral & +ve in my case) attached to each word and phrase. I'm afraid I'm not an expert in the theory of NLP so not sure how that fits into "backprop or RNT." I've learnt a bit about the overall field of NLP & a fair bit about the Stanford approach with the hope of creating my application without making some dumb error but that's as far as it goes.
|
|
|
|
|
Hmm. If they want predictions, they should go with backpropagation, rather than RNT(N). RNT isn't quite as "intelligent" (which, partly, means that you can understand its decisions, because it's more instance-tree population, ergo a percentage player, than a genuinely "intelligent" solution).
Backprop seems ideally suited to the problem you're working on, but I suppose it's not someone's "pet concept" at the moment. That's universities, for you.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Interesting. I'll have to look into backprop.
|
|
|
|
|
A friend of mine is a computational linguist. He says that at best it's gotten to about 85%, but that's with well structured source. What surprises me is that even with highly specific data, getting it better gets very complicated (though even in the highly specific stuff he recently worked on, 50% accuracy saves so much time that even that level of accuracy is worth it.)
|
|
|
|
|
Joe,
Interesting. What do you mean when you say:
Joe Woodbury wrote: 50% accuracy saves so much time that even that level of accuracy is worth it.)
|
|
|
|
|
If you're using natural language processing to assist in some task which is completed by humans, getting 50% completely right could save those humans a tremendous amount of time. Further, getting 85% accuracy with, say, even a 10% error rate may actually cause the humans to take even more time than if they hadn't used the computer program in the first place.
|
|
|
|
|
It's pretty hard to convince the general public that AI's making any sort of headway considering how easy it still is for something that should be as simple as Windows Update to completely mess up their computer.
(I realize this is apples and oranges...but you go ahead and explain it to those not in the field...)
|
|
|
|
|
If your salt and pepper wish you a Merry Christmas, is that seasons greetings?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
No, it's "seasonings greets"!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
It's: seasons' greetings. (punctuation)
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
The expected sage advice: during this chili season, it thyme to curry favor with your condiments.*
*Condom-Mints are, perhaps, a popular seasonal snack, but I won't mention it, asI was tempted to extend he pun but didn't.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
If they are talking to you, you have had way too much of Nagy's favorite.
... such stuff as dreams are made on
|
|
|
|
|
I might have to Mrs. Dash out of here on that one.
|
|
|
|
|
St. Valentines Day is the season to curry flavour with parsley, sage, rosemary, and thyme.
Especially in Scarborough.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
I've just had a support call from a customer to make some changes to a bespoke customer management and invoicing system, that I interfaced to their accounting system. I gave my normal one year of free support after delivery and acceptance, and offered continued support after that for a fee. This they declined, as the company "was undergoing a management and ownership change".
I never heard from them again.
Until today, that is.
I just hope I can remember what the hell I was writing TWELVE YEARS AGO!
Apparently, "It just worked".
|
|
|
|
|
Chris C-B wrote: Apparently, "It just worked". Or they've finally started using it
|
|
|
|
|
Actually, that was the first thing I asked - "What? Have you just started using it then?".
Apparently, it was been in continued use throughout.
I should have charged them more.
|
|
|
|
|
Chris C-B wrote: I should have charged them more.
You can, this time!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Yup! Charge like a wounded rhino.
|
|
|
|
|
Chris C-B wrote: Charge like a wounded rhino
I believe that wouldn't be fair, the prices should reflect the appropriate level twelve years ago.
Instead, just use the original price for starters and since the support continues from where you left off years ago, collect the 'late' annual fees from missing 12 yrs added only with nominal index raises for each year. Reasonable, don't you think?
|
|
|
|
|
Chris C-B wrote: This they declined So they got eleven years of maintenance-free software.
ms can't manage eleven days -- but people with a history of working for them still get job offers.
Incomprehensible, that
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Wow! Kudos for an apparently very well designed and robust application!
Now, figure out some way to assure some recurring revenue for your hard work! All of our stuff requires an annual fiscal year rollover process that we control...no support agreement, no rollover. It's worked well for us.
"Go forth into the source" - Neal Morse
|
|
|
|
|
The trouble is, I work on both sides of the fence. Not only do I write LOB applications for some clients, for other clients I am an IT consultant. Those clients get really pissed when they have to fork out a large chunk of change for a year-end roll-over. I personally, believe that in most cases it could be automated. As a result, I always provide a process that will close the old year, and open the new year, usually with a wizard type approach for the client's accounting staff to follow.
Sill me, I guess.
|
|
|
|
|