I could do it while the experience is fresh, although I only know the happy
path and not the deeper details in this area of the suite
If you want me to, let me know how to get editing privileges on the Wiki.

Peter

On Fri, Jul 31, 2020 at 4:28 AM Finan, Sean <
sean.fi...@childrens.harvard.edu> wrote:

> Obviously Jeff is correct in all of his answers.  Thank you Jeff!
>
> One comment: DictionaryDescriptor is a deprecated parameter name that is
> picked up by the piper creator when it inspects the code.  However, I am
> not sure why the deprecated parameter name isn't working ...
>
> The wiki needs additional and more thorough information.  If anybody can
> volunteer to work on it I (and future users) would really appreciate it!
>
> Thanks,
> Sean
>
>
> ________________________________________
> From: Peter Abramowitsch <pabramowit...@gmail.com>
> Sent: Thursday, July 30, 2020 9:02 PM
> To: dev@ctakes.apache.org
> Subject: Re: Problem trying to load a custom dictionary [EXTERNAL]
>
> * External Email - Caution *
>
>
> Thanks Jeff
>
> That worked!
>
> Seems like something that should get fixed in the PiperCreator and in the
> documentation.
>
> With a life of assuming that every mistake is my own error, the last thing
> I would have expected was
> a generator of incorrect params.
>
> Peter
>
> On Thu, Jul 30, 2020 at 4:59 PM Jeffrey Miller <jeff...@gmail.com> wrote:
>
> > Peter,
> >
> > 1) This is loaded by cTAKES, you don't need to manually create the
> > database.
> > 2) I can't see the highlights here, but I think that file should be okay
> as
> > created by the GUI.
> > 3) I think the parameter name to configure your dictionary location is
> > LookupXml instead of DictionaryDescriptor
> >
> > Jeff
> >
> > On Thu, Jul 30, 2020 at 6:49 PM Peter Abramowitsch <
> > pabramowit...@gmail.com>
> > wrote:
> >
> > > A couple of questions about installing a custom dictionary in lookup
> > fast.
> > > I hope I'm not too far off the track.
> > >
> > > I've used the dictionary creator with a UMLS install to create the
> > > dictionary script, prop file, and xml file in my ctakes resources tree
> > >
> > > 1.  Do I have to manually run this script to execute all its SQL
> > statements
> > > into hsqldb or is this executed by the cTakes program when it
> encounters
> > > the XML descriptor?
> > > If manual running is needed, are there instructions on how and where to
> > > load the script?
> > >
> > > 2.  The xml file generated by the dictionary creator contains lines
> with
> > > duplicate names-- see yellow highlight.  Is this  correct?
> > > <name>my_dict_v1Terms</name>
> > >          <property key="jdbcUrl"
> > >
> >
> value="jdbc:hsqldb:file:resources/org/apache/ctakes/dictionary/lookup/fast/
> > > my_dict_v1/my_dict_v1"/>
> > >
> > > 3.  Try as I might I cannot get ctakes to load anything other than
> > > sno_rx.   I'm using a piper file with an entry looking like
> > >       ....
> > >       add org.apache.ctakes.dictionary.lookup2.ae
> > .OverlapJCasTermAnnotator
> > >
> > >
> >
> DictionaryDescriptor=org/apache/ctakes/dictionary/lookup/fast/my_dict_v1.xml
> > >      ....
> > > Not sure if they're looked at any more but I also changed these xml
> files
> > > under desc as well.
> > >
> > >
> > >
> > >
> >
> desc/ctakes-dictionary-lookup-fast/desc/analysis_engine/UmlsOverlapLookupAnnotator.xml
> > >
> > >
> > >
> >
> desc/ctakes-dictionary-lookup-fast/desc/analysis_engine/UmlsLookupAnnotator.xml
> > >
> > > But I can't even get it to fail to try to load mine.
> > > my log looks like this
> > >
> > >       30 Jul 2020 15:43:37  INFO AbstractJCasTermAnnotator - Exclusion
> > > tagset loaded: CC CD DT EX IN LS MD PDT POS PP PP$ PRP PRP$ RP TO VB
> VBD
> > > VBG VBN VBP VBZ WDT WP WPS WRB
> > >       30 Jul 2020 15:43:37  INFO AbstractJCasTermAnnotator - Using
> > minimum
> > > term text span: 3
> > >       30 Jul 2020 15:43:37  INFO AbstractJCasTermAnnotator - Using
> > > Dictionary Descriptor: org/apache/ctakes/dictionary/lookup/fast/
> > > sno_rx_16ab.xml
> > >
> > >
> > > Any suggestions?
> > >
> > > Regards,  Peter
> > >
> >
>

Reply via email to