Versions Compared

Old Version 92

changes.mady.by.user Troy Bleeker

Saved on

compared with

New Version 93

changes.mady.by.user Troy Bleeker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Step

Example

1. Launching the UIMA CAS Visual Debugger (CVD) or the Collection Processing Engine (CPE) from Eclipse can now be accomplished in the ctakes-clinical-pipeline project. Navigate to:

Code Block
langnone
<cTAKES_HOME>
  \ctakes-clinical-pipeline
    \resources
      \launch
        \UIMA_<CVD | CPE>GUI--clinical_documents pipeline.launch

where you must select between CVD and CPE in the command. Right-click on the launch file and select Run-As -> UIMA_<CVD | CPE>GUI-clinical_documents.

Info

Note: Don't forget to set the location of the resources and your UMLS user ID and password if you have not done so for a particular project or run configuration.



2. (Optional) Process data.

Now that you can launch the tools, the User Guide has steps to walk you through processing test data if you want to go there.

Note

The User Guide describes files in the form that they came in the binary distributions. That form does not match the form when you checkout the code as we have done here.

For developers there is only one directory named "desc" in a path. When you use the User Guide you must ignore the first "desc" shown in a path.

No example

...

Step

Example

1. Launching the UIMA CAS Visual Debugger (CVD) or the Collection Processing Engine (CPE) can now be accomplished in the ctakes-clinical-pipeline project:

Windows:

Code Block
langnone
cd \cTAKES-3.0
set MAVEN_OPTS=-Xmx2g -Xms1g
mvn -Prun<CVD|CPE> compile

Linux:

Code Block
langnone
cd /cTAKES-3.0
export MAVEN_OPTS="-Xmx2g -Xms1g"
mvn -Prun<CVD|CPE> compile

where you must select between CVD and CPE in the command.


2. (Optional) Process data.

Now that you can launch the tools, the User Guide has steps to walk you through processing test data if you want to go there.

Note

The User Guide describes files in the form that they came in the binary distributions. That form does not match the form when you checkout the code as we have done here.

For developers there is only one directory named "desc" in a path. When you use the User Guide you must ignore the first "desc" shown in a path.


No example

...