You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by "Masanz, James J." <Ma...@mayo.edu> on 2013/02/11 17:48:44 UTC

checking out 3.0.0-incubating from SVN branch and merging resources

Here's what I did to test the clinical-pipeline aggregates after checking out source from 3.0.0-incubating branch into Eclipse

 - download resources from sourceforge.net per README
   http://svn.apache.org/viewvc/incubator/ctakes/branches/ctakes-3.0.0-incubating/README?view=markup
 - merge that resources folder contents into ctakes-dictionary-lookup/resources
 - I used launch configuration UIMA_CVD--clinical_documents_pipeline
 - Added ctakes-dictionary-lookup/resources to the classpath (I did it via the Classpath tab on the launch configuration)

To test the UMLS aggregate, I added the following to the VM arguments on the Arguments tab of the Run configuration popup
-Dctakes.umlsuser=jmasanz -Dctakes.umlspw=REDACTED

In my opinion, we can wait to simplify these steps until next release.

-- James

Regards,
James Masanz
Senior Analyst/Programmer
Department of Information Technology
Phone: (507) 722-1727
masanz.james@mayo.edu

Mayo Clinic
mayoclinic.org 



RE: checking out 3.0.0-incubating from SVN branch and merging resources

Posted by "Masanz, James J." <Ma...@mayo.edu>.
It might not have been clear that in what I wrote earlier, to use other top-level pipelines from other (sub)projects, would require similar updates. Plus for relation extraction, some other instructions would be needed since the way resources are resolved is different for that subproject (something to sync in a later release)

I propose that we do one of the following two things to simplify, for people who check out the 3.0.0-incubating source, the process of (and documention for) using the resources from ctakes-reources-3.0.1 from sf.net. NOTE that neither of these require changing /canceling RC7.

Document how people can do their own build so they end up with a single resources directory (like what is in the bin distribution) and can simply unzip ctakes-reources-3.0.1.zip from sf.net over that single directory and not have to update any classpaths. (similar to http://incubator.apache.org/ctakes/ctakes-release-guide.html, or just point them there once those are verified to be up-to-date)

OR 

Upload to SF.net an alternative version of ctakes-reources-3.0.1 that has resources separated out into directory structure that matches the source structure where, e.g. assertion has its own resources directory, chunker has its own resources directory, dictionary lookup has its own resources directory, etc.
This would allow people to unzip over the top of the top level ctakes directory and have things end up in the appropriate (sub)project resources directories, and not have to update classpaths to locate the resources fron SF.net. 

-- James Masanz


> -----Original Message-----
> From: ctakes-dev-return-1190-Masanz.James=mayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-1190-Masanz.James=mayo.edu@incubator.apache.org]
> On Behalf Of Masanz, James J.
> Sent: Monday, February 11, 2013 10:49 AM
> To: 'ctakes-dev@incubator.apache.org'
> Subject: checking out 3.0.0-incubating from SVN branch and merging
> resources
> 
> 
> Here's what I did to test the clinical-pipeline aggregates after checking
> out source from 3.0.0-incubating branch into Eclipse
> 
>  - download resources from sourceforge.net per README
>    http://svn.apache.org/viewvc/incubator/ctakes/branches/ctakes-3.0.0-
> incubating/README?view=markup
>  - merge that resources folder contents into ctakes-dictionary-
> lookup/resources
>  - I used launch configuration UIMA_CVD--clinical_documents_pipeline
>  - Added ctakes-dictionary-lookup/resources to the classpath (I did it via
> the Classpath tab on the launch configuration)
> 
> To test the UMLS aggregate, I added the following to the VM arguments on
> the Arguments tab of the Run configuration popup -Dctakes.umlsuser=jmasanz
> -Dctakes.umlspw=REDACTED
> 
> In my opinion, we can wait to simplify these steps until next release.
> 
> -- James
> 
> Regards,
> James Masanz
> Senior Analyst/Programmer
> Department of Information Technology
> Phone: (507) 722-1727
> masanz.james@mayo.edu
> 
> Mayo Clinic
> mayoclinic.org
>