It does look like that class has hardcoded paths. There may be another pipeline
that is appropriate -- what kind of output are you looking to get from your
documents?
Tim
From: Abraham Tom [a...@practicefusion.com]
Sent: Tuesday, April 15, 2014 12:08 AM
The discussion in the other thread with Abraham Tom gave me an idea I
wanted to float to the list. We have been using some UIMAFit pipeline
builders in the temporal project that maybe could be moved into
clinical-pipeline. For example, look to this file:
http://svn.apache.org/viewvc/ctakes/trunk/c
+1 I think that a factory is a great idea.
I (personally) dislike the descriptor schema, but I think that deprecation is
the way to go until a replacement comes along.
-Original Message-
From: Miller, Timothy [mailto:timothy.mil...@childrens.harvard.edu]
Sent: Tuesday, April 15, 201
+1
-Original Message-
From: Finan, Sean [mailto:sean.fi...@childrens.harvard.edu]
Sent: Tuesday, April 15, 2014 9:05 AM
To: dev@ctakes.apache.org
Subject: RE: suggestion for default pipelines
+1 I think that a factory is a great idea.
I (personally) dislike the descriptor schema, but I
+1
Best regards,
Abraham Tom
Abraham Tom
Data Warehouse Engineer
415.757.4674 (p) | 415.356.0950 (f)
a...@practicefusion.com
http://www.practicefusion.com
www.facebook.com/practicefusion
The contents of this message, together with any attachments, are intended only
+1. And note that once you have a descriptor, you can generate the
XML, so we should arrange to replace the current XML descriptors with
ones generated automatically from the uimaFIT code. That should reduce
some synchronization problems when the Java code was changed but the
XML descriptor was not
