Return-Path: X-Original-To: apmail-incubator-ctakes-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-ctakes-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F1DF6D12D for ; Thu, 15 Nov 2012 17:42:19 +0000 (UTC) Received: (qmail 42126 invoked by uid 500); 15 Nov 2012 17:42:19 -0000 Delivered-To: apmail-incubator-ctakes-commits-archive@incubator.apache.org Received: (qmail 42097 invoked by uid 500); 15 Nov 2012 17:42:19 -0000 Mailing-List: contact ctakes-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ctakes-dev@incubator.apache.org Delivered-To: mailing list ctakes-commits@incubator.apache.org Received: (qmail 42090 invoked by uid 99); 15 Nov 2012 17:42:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 17:42:19 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Nov 2012 17:42:18 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 51EDB2388993 for ; Thu, 15 Nov 2012 17:41:58 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r838463 - in /websites/staging/ctakes/trunk/content: ./ ctakes/3.0.0/user-guide-3.0.html Date: Thu, 15 Nov 2012 17:41:58 -0000 To: ctakes-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121115174158.51EDB2388993@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Thu Nov 15 17:41:57 2012 New Revision: 838463 Log: Staging update by buildbot for ctakes Modified: websites/staging/ctakes/trunk/content/ (props changed) websites/staging/ctakes/trunk/content/ctakes/3.0.0/user-guide-3.0.html Propchange: websites/staging/ctakes/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Thu Nov 15 17:41:57 2012 @@ -1 +1 @@ -1409870 +1409895 Modified: websites/staging/ctakes/trunk/content/ctakes/3.0.0/user-guide-3.0.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/3.0.0/user-guide-3.0.html (original) +++ websites/staging/ctakes/trunk/content/ctakes/3.0.0/user-guide-3.0.html Thu Nov 15 17:41:57 2012 @@ -140,7 +140,7 @@ paths on your machine.

An analysis engine (AE) needs to be loaded in order to process text.
-Use the Run -> Load AE menu bar command. Navigate to the file. Click Open.

+Use the Run -> Load AE menu bar command. Navigate to the file: /cTAKESdesc/cdpdesc/analysis_engine/AggregatePlaintextProcessor.xml Click Open.

Copy the text in this example and paste the contents into the Text section of CVD, replacing the text that is already @@ -181,67 +181,53 @@ edu.mayo.bmi.uima.core.type.textsem.Even edu.mayo.bmi.uima.core.type.textsem.EventMention.MedicationEventMention

- -

Then select edu.mayo.bmi.uima.core.type.*textsem.*EntityMention or +

Then select edu.mayo.bmi.uima.core.type.*textsem.*EntityMention or edu.mayo.bmi.uima.core.type.*textsem.EventMention.*MedicationEv entMention**.This will show an Annotation Index in the lower frame. Select any annotation in that lower frame and you will see the text discovered in the -Text frame on the right. You may close CVD if you wish.
+Text frame on the right.

+
Collection processing engine (CPE)

The Collection Processing Engine (CPE) Configuration GUI is for configuring components (aka analysis engine) to process documents (called a pipeline).

-
Open a command prompt and change to the cTAKES_HOME directory:
-
-
Windows:
-
-
Linux:
-
-
-
Note
-
-
Note that cTAKES_HOME must be your current directory unless you are skilled at -setting paths on your machine.
-
-
Start the collection processing engine by running this command:
-
-
Windows:
-
-
Linux:
-
-
The application may take a minute to start on slower hardware.
-
-
-
This will bring up the Collection Processing Engine Configurator. In the -Menu bar click File > Open CPE Descriptor
-
-
-
-
Navigate to the file
-
-
Click Open.
-
-
-
Click the Play button (green/blue play arrow near the bottom).
-
-
-
-
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.
-
-
-
-
Close the CPE application. You may be prompted to save changes. Since this -was just a test you may click the No button.
-
-
-
-
Open a new command prompt and change to the
-
-
No example.
-
-
To test the results there is a comparison tool that will help show that the -results match expectations with the following syntax:
+
+
Open a command prompt and change to the cTAKES_HOME directory.
+Windows: cd \cTAKES-3.0 Linux: cd /usr/bin/cTAKES-3.0
+
+Note: cTAKES_HOME must be your current directory unless you are skilled at setting +paths on your machine.
+
+
+
Start the Collection Processing Engine (CPE) by running this command. The application may take a minute to start on slower hardware:
+Windows: runctakesCPE.bat Linux: runctakesCPE.sh
+
+
+
This will bring up the Collection Processing Engine Configurator. In the +Menu bar click File > Open CPE Descriptor.
+
+
+
Navigate to the file: /cTAKESdesc/cdpdesc/collection_processing_engine/test_plaintext.xml Click Open.
+
+
+
Click the Play button (green/blue play arrow near the bottom).
+
+
+
You should see that one document was processed. A collection of documents was processed, however, +in this case, the collection only contained one just +to show how to do it.
+Close the results window.
+
+
+
Close the CPE application. You may be prompted to save changes. Since this +was just a test you may click the No button.
+
+
+
Open a new command prompt and change to the directory.
+
+
+
To test the results, you will use a comparison tool that will help show that the +results match expectations with the following syntax:
+

Where: is the first file to compare; is the second file to compare; is where the results are written