You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ctakes.apache.org by "Sean (JIRA)" <ji...@apache.org> on 2012/11/20 20:42:58 UTC
[jira] [Created] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
Sean created CTAKES-101:
---------------------------
Summary: Term spotting pipelines returning 'unknown' classifications
Key: CTAKES-101
URL: https://issues.apache.org/jira/browse/CTAKES-101
Project: cTAKES
Issue Type: Bug
Components: ctakes-pad-term-spotter, ctakes-smoking-status
Affects Versions: 2.6-incubating, 3.0-incubating
Environment: Linux and Windows OS
Reporter: Sean
Fix For: 2.6-incubating
The problem seems to have stemmed from the reorganization of the path structures with the latest cTAKES release. Due to time and resource constraints we were not able to test each project independently. This will be fixed in current and future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
Posted by "Pei Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504771#comment-13504771 ]
Pei Chen commented on CTAKES-101:
---------------------------------
Do you recall the exception? Or details on how to recreate/ where the problem lies in the desc path?
It may be already fixed in 3.0 and trunk since we updated all the paths as part of the ASF move.
> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>
> Key: CTAKES-101
> URL: https://issues.apache.org/jira/browse/CTAKES-101
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-pad-term-spotter, ctakes-smoking-status
> Affects Versions: 2.6-incubating, 3.0-incubating
> Environment: Linux and Windows OS
> Reporter: Sean
> Labels: patch
> Fix For: 2.6-incubating
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The problem seems to have stemmed from the reorganization of the path structures with the latest cTAKES release. Due to time and resource constraints we were not able to test each project independently. This will be fixed in current and future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
Posted by "Pei Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510079#comment-13510079 ]
Pei Chen commented on CTAKES-101:
---------------------------------
In the project pom.xml (ctakes-pad-term-spotter?), it should list the dependencies it needs.
Try adding the below (and any other projects that it's dependent on) to the pom.xml:
<dependency>
<groupId>org.apache.ctakes</groupId>
<artifactId>ctakes-chunker</artifactId>
</dependency>
> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>
> Key: CTAKES-101
> URL: https://issues.apache.org/jira/browse/CTAKES-101
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-pad-term-spotter, ctakes-smoking-status
> Affects Versions: 2.6-incubating, 3.0-incubating
> Environment: Linux and Windows OS
> Reporter: Sean
> Labels: patch
> Fix For: 2.6-incubating
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The problem seems to have stemmed from the reorganization of the path structures with the latest cTAKES release. Due to time and resource constraints we were not able to test each project independently. This will be fixed in current and future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
Posted by "Sean (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510060#comment-13510060 ]
Sean commented on CTAKES-101:
-----------------------------
Thanks.
For your answer "startup the CVD/CPE directly from Eclipse IDE and load the Analsyis Engine(s)" I assume that is supposed to be a standalone step(?)
I get the following error when I load the analysis engine:
Caused by: org.apache.uima.resource.ResourceInitializationException: Could not access the resource data at file:org/apache/ctakes/chunker/models/chunk-model.claims-1.5.zip.
at org.apache.uima.resource.impl.DataResource_impl.initialize(DataResource_impl.java:127)
at org.apache.uima.util.SimpleResourceFactory.produceResource(SimpleResourceFactory.java:123)
Are the maven dependencies supposed to contain this resource?
~Sean
> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>
> Key: CTAKES-101
> URL: https://issues.apache.org/jira/browse/CTAKES-101
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-pad-term-spotter, ctakes-smoking-status
> Affects Versions: 2.6-incubating, 3.0-incubating
> Environment: Linux and Windows OS
> Reporter: Sean
> Labels: patch
> Fix For: 2.6-incubating
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The problem seems to have stemmed from the reorganization of the path structures with the latest cTAKES release. Due to time and resource constraints we were not able to test each project independently. This will be fixed in current and future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
Posted by "Sean (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510006#comment-13510006 ]
Sean commented on CTAKES-101:
-----------------------------
Hello Pei,
I'm trying to test the fixes at the unit level as well as when built via the maven package command. I'm new to maven so these are obviously newbie type questions.
Is it a manual step, the pear installer, or some other means you use to combined the project as they exist in the binary version you shipped (with the bin, desc and resources all at the root install)? I see that zips/gz in the ctakes-distribution project, but I wondering if you further process to ship.
Also, prior to bundling I would like to have the option to run at the individual project level. Since the resources and descriptor files dependencies are distributed do you leverage maven to consolidate them or should I use the old standby of just updating the classpath?
Thanks,
~Sean
> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>
> Key: CTAKES-101
> URL: https://issues.apache.org/jira/browse/CTAKES-101
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-pad-term-spotter, ctakes-smoking-status
> Affects Versions: 2.6-incubating, 3.0-incubating
> Environment: Linux and Windows OS
> Reporter: Sean
> Labels: patch
> Fix For: 2.6-incubating
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The problem seems to have stemmed from the reorganization of the path structures with the latest cTAKES release. Due to time and resource constraints we were not able to test each project independently. This will be fixed in current and future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CTAKES-101) Term spotting pipelines returning
'unknown' classifications
Posted by "Pei Chen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510013#comment-13510013 ]
Pei Chen commented on CTAKES-101:
---------------------------------
$mvn package will automatically create the zips/gz in the ctakes-distribution project. Those zips/gz will be what will be shipped out.
If you would like to test it directly from the source, you can
1) startup the CVD/CPE directly from Eclipse IDE and load the Analsyis Engine(s).
2) $MAVEN_OPTS="-Xmx1g" mvn -PrunCVD compile
To test it from the distribution,
unpack the bin from ctakes-distribution and run ./bin/startctakesCVD.sh and load the Analysis Engine(s).
> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>
> Key: CTAKES-101
> URL: https://issues.apache.org/jira/browse/CTAKES-101
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-pad-term-spotter, ctakes-smoking-status
> Affects Versions: 2.6-incubating, 3.0-incubating
> Environment: Linux and Windows OS
> Reporter: Sean
> Labels: patch
> Fix For: 2.6-incubating
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> The problem seems to have stemmed from the reorganization of the path structures with the latest cTAKES release. Due to time and resource constraints we were not able to test each project independently. This will be fixed in current and future releases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira