...
Step
| Example | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. Do no try this until AFTER cTAKES 4.0 is released (this 4.0 document is still a DRAFT): On the cTAKES downloads page, download the User Installation package.
|
| |||||||||||||||||
2. (Recommended) Verify the downloaded files against a signature to ensure you have the proper and complete file. From the following directory, download the signature file that corresponds to your download from step 1 https://www.apache.org/dist/ctakes/ctakes-4.0.0/ Please do not download any of the files that end with .zip or .gz directly from apache.org/dist - use the downloads page listed in step 1 if you need to download cTAKES itself so that a mirror can be used. | No example | |||||||||||||||||
3. Unzip the file you downloaded into a directory that you want to be the cTAKES install location. The compressed files contain a single directory at the top level. This folder we will call <cTAKES_HOME>. It is the directory that contains subdirectories like bin, desc, resources, lib. You will need to refer to this directory later.
Linux:
| Windows:
| |||||||||||||||||
4. Download the cTAKES resources ZIP file with a matching version from the ctakesresources project (More information on cTAKES models). These resources are required to operate cTAKES.
| Windows:
| |||||||||||||||||
5. Copy (or move) the resources to cTAKES_HOME.
| Windows:
Linux:
Mac OSX:
|
...
Step
| Example | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. If you do not have a UMLS username and password, you may request one at UMLS Terminology Services. | No example | |||||||||||||||||||
2. Once you have your UMLS username and password, edit the following files. Find the lines in each script that runs java and add the ctakes.umlsuser and ctakes.umlspw parameters to the java command with your credentials. Make sure you substitute your actual ID and password if you cut and paste the example.
Linux:
|
In the examples below, the rest of the lines after
If you use special characters in your user name or password, you may need to escape them or for windows, place the string in quotes For example, if your username and password were literally myusername and mypassword, you could insert them before the -cp option so the start of the java command would look like this:
Windows: If you use special characters in your umls user name or password, you can place them in double-quotes:
The rest of the line after Linux: If you use special characters in your user name or password, you may need to escape them | |||||||||||||||||||
2a. You may also specify your UMLS Credentials as environment variables to your operating system, but the dots will need to be replaced with underscores. | Linux:
|
...
Step
| Example | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. Open a command prompt and change to the cTAKES_HOME directory:, which is the directory that contains subdirectories like bin, desc, resources, lib.
|
Linux:
| ||||||||||||
2. Create a directory for some test data. |
| ||||||||||||
3. Download this sample file and place it into the testdata directory. | No example | ||||||||||||
4. Start the collection processing engine by running this command: | Windows:
Linux:
| ||||||||||||
5. This will bring up the Collection Processing Engine Configurator. In the Menu bar click File >Open CPE Descriptor | |||||||||||||
6. Navigate to the following file, which uses the AggregateCdaProcessor
| No example | ||||||||||||
7. Change the Collection Reader input directory to testdata, which contains a CDA file(s). Within the CAS Consumers pane of the same window, change the output directory to testdata/output | |||||||||||||
8. Click the Play button (green/blue play arrow near the bottom).
| |||||||||||||
9. You should see that one document was processed. You did process a collection of documents. In this case the collection only contained one just to show how to do it. Close the results window.
| |||||||||||||
10. Close the CPE application. You may be prompted to save changes. Since this was just a test you may click the No button. | No example |
...
The analysis engines and collection processing engines shipped with cTAKES for some of the annotators are described in the following table.
Warning |
---|
TBD - TODO - fix this - cTAKES 3.1 binary distributions did not include test data. Loading the CPE descriptors into the CPE tool will require resetting the input and output directories. Test files could be obtained from the cTAKES 2.5 release binary distribution. Look for a testdata directory in cTAKES_HOME. |
...