James: EXCELLENT suggestion. Last time I checked CTAKES was way out of date.
Makes sense that one of us should play "red rover" and keep cTakes up to date. I just this moment sent a message to iDASH to start the update conversation. --Andy On Oct 30, 2013, at 8:04 AM, "Masanz, James J." <[email protected]> wrote: > Andy, > > You might want to talk with the folks at iDASH. > They have an image with a number of NLP tools installed, but it doesn't have > the latest version of cTAKES. > > http://idash.ucsd.edu/nlp/natural-language-processing-nlp-ecosystem > > Perhaps they would be open to your help with upgrading to a later version of > cTAKES. > > -- James > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > andy mcmurry > Sent: Tuesday, October 29, 2013 6:34 PM > To: [email protected] > Subject: Re: cTAKES user interface > > Ricard: > > Groovy idea. > Virtual Machine could benefit from that as well. > > *## IMHO: These are parallel tasks that I think are higher priority than > new features. > *It isn't as glamorous as playing Jeopardy, but deploy issues are keeping > users out -- if I were to guess A LOT of the potential user base looks at > ctakes and says "wow that amazing! " > > then they look at how complex it will be to do their simple "Hello Ctakes" > example and the 15 minutes of attention -- we are one walk to the soda > machine away from being either embraced or forgotten. It really is that > basic -- if it takes to long to get started, chances are new users -- wont. > > The documentation is nicely done and this is absolutely no criticism of > that. > In fact, I apologize for being so out of touch (was thesis writing ). > > It just feels like 1992 all over again and your compiling linux just to > find out you didn't tweak your VGA card settings right, and now your stuck. > But you still think linux rocks. > > 2013 is here and linux now runs out of the box. > The OS itself has changed less in features and more in ease of use. > > I know its not Jeopardy but we gotta do it. > *## I'm going to make a VM (Ubuntu 13.10) for myself and let everyone kick > it around. **I strongly encourage the Groovy deploy targets as Richard > suggested. * > > This really isn't an either | OR. > We need to be able to have easier turn around on cTakes so we can get back > to Jeopardy. > > *## Who agrees, and are there any counter proposals? * > > > AndyMC > > > > > > > On Tue, Oct 29, 2013 at 3:49 PM, Richard Eckart de Castilho > <[email protected]>wrote: > >> Maven allows to do marvelous things on the CLI, provided you throw in an >> additional component: Groovy. >> >> We did some amazing self-contained Groovy scripts with uimaFIT and DKPro >> Core which you might find interesting >> >> http://code.google.com/p/dkpro-core-asl/wiki/DKProGroovyCookbook >> >> -- Richard >> >> On 29.10.2013, at 23:09, "Miller, Timothy" < >> [email protected]> wrote: >> >>> I think this is also an area where Maven integration was a small step >> backwards (I greatly appreciate the steps forward it allowed). I used to >> run stuff from the command line and in scripts more often but it's slightly >> less straightforward setting up the classpath with maven -- before you >> could put a simple java -cp lib/*.jar <class name> in a script, now I'm not >> sure how to go about it using maven. I'm sure there's a way, but I am >> afraid of falling down the maven rabbit hole. >>> Tim >>> >>> >>> On Oct 29, 2013, at 5:53 PM, Chen, Pei wrote: >>> >>>> +1 >>>> Pan, the short answer is yes- it can be done in CLI. >>>> The problem is that most of us who are already familiar with the nitty >> gritty are probably doing this with some sort of custom scripts or solution. >>>> Cc' the dev group to get a fresh perspective; not sure what the easiest >> would be-- run the CPE via command line with default input/output >> directories or running a Driver Main Class as part of examples. >>>> >>>> --Pei >> >>
