I just completed a good scrub updating the SourceForge.net project websites for JWords and AutoSummary. I removed most of the unused features, uploaded & organized documentation, and configured the SF.net web hosting service. No new file releases are available (or pending), but the SourceForge.net page and documentation should make JWords & AutoSummary much more accessible and easier to use.
Javadoc source code documentation was uploaded onto SourceForge for both of the projects. Additionally, I created step-by-step instructions for getting each program up and running, which should be easy to follow for even the non-programmer. And finally, I posted more extensive project descriptions to the respective documentation pages.
The updated SourceForge.net project websites can be viewed at:
JWords Java Interface for WordNet
AutoSummary Semantic Analysis Engine
My SourceForge.net developer profile can be found at:
http://sourceforge.net/users/greenbacker/
Showing posts with label jwords. Show all posts
Showing posts with label jwords. Show all posts
Sunday, April 15, 2007
Tuesday, August 9, 2005
JWords Update Release Notice
I am happy to announce that the latest version of the JWords Java Interface for WordNet has been released. JWords 0.2.0 Alpha includes new methods for calculating the relative likeliness that a word will appear as a particular part of speech, which may be used for statistical semantic analysis (like POS tagging), as well as an updated documentation. These features were specifically designed for a forthcoming semantic analysis package... which will be released shortly.
JWords is available for download at SourceForge.net http://sourceforge.net/projects/jwords/
Javadoc documentation for JWords is available here.
JWords is available for download at SourceForge.net http://sourceforge.net/projects/jwords/
Javadoc documentation for JWords is available here.
Monday, August 8, 2005
Have you ever seen the sun rise ... twice in a row ... three times...?
Paul Graham recently had a very interesting article about what businesses can learn from open source.
The entire piece was very well written, and the author makes a lot of good points, but what captured my imagination the most was the part about the optimal working environment for a programmer. Paul says that people working in the comfortable surroundings of their own home are often exponentially more productive than corporate rats in a stuffy cubicle farm. Based on my own personal experience, I would certainly agree. I find I do my best work in marathon sessions, often involving massive amounts of caffeine and highly irregular sleep patterns. I understand many programmers share similar experiences. Once I get 'in the zone,' as they say, I will work solidly for hours on end paying little attention to time or the world around me. Were I restricted to a structured work environment constantly struggling against interruptions and distractions like co-workers, meetings and email, I fear my programming would suffer.
I am currently working hard to finish up the next release of JWords, as well as the initial release of another semantic analysis tool. I've been trying to complete this stuff for weeks now, but I find the only way I can get anything done is if I rush straight home from work and devote the entire evening to programming. If I decide to go workout, play basketball, see a movie or go out to dinner, and try to pick up where I left off and program a little bit at a time, I never get anything done. By the time I sit down and get going, its time to sign off for the night. My old friend the all-nighter is no longer an option with my responsibilities at work. Usually weekends offer a real chance to get down to business, but I'm afraid my willpower is just barely too weak to resist the temptation of living it up at the beach. But on those rare occasions when I can devote a significant amount of time to this endeavor, and everything is firing on all cylinders, nothing else compares.
The entire piece was very well written, and the author makes a lot of good points, but what captured my imagination the most was the part about the optimal working environment for a programmer. Paul says that people working in the comfortable surroundings of their own home are often exponentially more productive than corporate rats in a stuffy cubicle farm. Based on my own personal experience, I would certainly agree. I find I do my best work in marathon sessions, often involving massive amounts of caffeine and highly irregular sleep patterns. I understand many programmers share similar experiences. Once I get 'in the zone,' as they say, I will work solidly for hours on end paying little attention to time or the world around me. Were I restricted to a structured work environment constantly struggling against interruptions and distractions like co-workers, meetings and email, I fear my programming would suffer.
I am currently working hard to finish up the next release of JWords, as well as the initial release of another semantic analysis tool. I've been trying to complete this stuff for weeks now, but I find the only way I can get anything done is if I rush straight home from work and devote the entire evening to programming. If I decide to go workout, play basketball, see a movie or go out to dinner, and try to pick up where I left off and program a little bit at a time, I never get anything done. By the time I sit down and get going, its time to sign off for the night. My old friend the all-nighter is no longer an option with my responsibilities at work. Usually weekends offer a real chance to get down to business, but I'm afraid my willpower is just barely too weak to resist the temptation of living it up at the beach. But on those rare occasions when I can devote a significant amount of time to this endeavor, and everything is firing on all cylinders, nothing else compares.
Thursday, July 14, 2005
It Knows...
That's what I said to myself while working on my project tonight.
Work was really slow today, so I had some time to scrutinize the probability algorithm for my part-of-speech disambiguator. Basically, the tool I'm working on now is meant to correctly identify the part-of-speech for each word in a given phrase. When I got home and tinkered with the code a bit, I was astonished with how well it worked. The program is now analyzing all possible combinations, and reports the instance it determines is most likely to occur, based on general usage statistics.
When I realized it was doing what I hoped it would do, and the statistical formula was working properly, I was pleasantly surprised. Later on, I will combine this with other methods of semantic analysis in an attempt to determine the specifc meaning of each word in a sentence. But for now, I'm cleaning up the code a bit, and improving the performance by eliminating unnecessary steps. The algorithm is working... but its slow, with an efficiency on the order of O(4^n)! Once I speed it up and get it into a presentable format, I will make it available to download and try out.
Not exactly what you would call a 'Eureka!' moment, but I was pleased nonetheless.
Work was really slow today, so I had some time to scrutinize the probability algorithm for my part-of-speech disambiguator. Basically, the tool I'm working on now is meant to correctly identify the part-of-speech for each word in a given phrase. When I got home and tinkered with the code a bit, I was astonished with how well it worked. The program is now analyzing all possible combinations, and reports the instance it determines is most likely to occur, based on general usage statistics.
When I realized it was doing what I hoped it would do, and the statistical formula was working properly, I was pleasantly surprised. Later on, I will combine this with other methods of semantic analysis in an attempt to determine the specifc meaning of each word in a sentence. But for now, I'm cleaning up the code a bit, and improving the performance by eliminating unnecessary steps. The algorithm is working... but its slow, with an efficiency on the order of O(4^n)! Once I speed it up and get it into a presentable format, I will make it available to download and try out.
Not exactly what you would call a 'Eureka!' moment, but I was pleased nonetheless.
Wednesday, February 23, 2005
JWords Alpha Release
I am pleased to announce that the first alpha testing version of the JWords Java Interface for WordNet has been released under the BSD License.
JWords is a simple and easy to use Java interface for the WordNet 2.0 command line tool. It provides classes and methods to create and use JWord objects containing the information stored in the WordNet lexical reference system.
I created JWords because I wasn't happy with any of the other Java APIs available for WordNet. I plan on using WordNet as the primary lexicon for autosummary software I am creating, and I needed to create a custom-tailored interface to suit my needs. By treating words as objects, and using the WordNet command line tool to handle the burden of reading the database files, JWords offers a simple and versatile way to access a wealth of lexical information.
JWords is available for download at SourceForge.net http://sourceforge.net/projects/jwords/
Javadoc documentation for JWords is available here.
JWords is a simple and easy to use Java interface for the WordNet 2.0 command line tool. It provides classes and methods to create and use JWord objects containing the information stored in the WordNet lexical reference system.
I created JWords because I wasn't happy with any of the other Java APIs available for WordNet. I plan on using WordNet as the primary lexicon for autosummary software I am creating, and I needed to create a custom-tailored interface to suit my needs. By treating words as objects, and using the WordNet command line tool to handle the burden of reading the database files, JWords offers a simple and versatile way to access a wealth of lexical information.
JWords is available for download at SourceForge.net http://sourceforge.net/projects/jwords/
Javadoc documentation for JWords is available here.
Subscribe to:
Posts (Atom)