Re: Best practices for documenting NLP versions [EXTERNAL]

what collection reader you are using then you are probably using FileTreeReader - which is an extension. I hope that this is useful to somebody. Sean From: Greg Silverman Sent: Friday, October 21, 2022 6:23 PM To: dev@ctakes.apache.org Subject: Re: Bes

Re: Best practices for documenting NLP versions

It was an off-the-cuff suggestion. Devil is obviously in the details. On Fri, Oct 21, 2022 at 3:33 PM Peter Abramowitsch wrote: > Interesting, but it would depend on how the docker is set up. Our docker > for instance, encapsulates all the code and imported jars, as you imply, > but the piper a

Re: Best practices for documenting NLP versions

Interesting, but it would depend on how the docker is set up. Our docker for instance, encapsulates all the code and imported jars, as you imply, but the piper and other runtime configuration such as section regex, negex, bsvs, etc are imported on a mounted FS during the container's runtime. Havin

Re: Best practices for documenting NLP versions

Why not use Docker and versioning by tags? See "C. Boettiger, An introduction to Docker for reproducible research, SIGOPS Oper. Syst. Rev. 49 (2015) 71–79. doi:10.1145/2723872.2723882. " On Fri, Oct 21, 2022 at 3:15 PM Peter Abramowitsch wrote: > Wel

Re: Best practices for documenting NLP versions

Well, obviously, the full range of permutations of all source files and all annotators and pre and post ctakes code would require a huge amount of commit information on thousands of files... and not only ctakes files...recently I made some pretty significant changes to the ZonerCli library which i

Best practices for documenting NLP versions

We’ve recently been using cTAKES for some internal projects where we make modifications, often using the REST server, combined with an open-source python client that makes the output of the REST server easy to post-process: https://github.com/Machine-Learning-for-Medical-Language/ctakes-client-py

RE: best practices

Best Practices page created: https://cwiki.apache.org/confluence/display/CTAKES/Best+Practices Link called "Best Practices" created on the left pane of: http://ctakes.apache.org/index.html -Original Message- From: ksa...@gmail.com [mailto:ksa...@gmail.com] On Behalf Of Kar

Re: best practices

+1 -- Karthik Sarma UCLA Medical Scientist Training Program Class of 20?? Member, UCLA Medical Imaging & Informatics Lab Member, CA Delegation to the House of Delegates of the American Medical Association ksa...@ksarma.com gchat: ksa...@gmail.com linkedin: www.linkedin.com/in/ksarma On Fri,

RE: best practices

+1 for BP -Original Message- From: Chen, Pei [mailto:pei.c...@childrens.harvard.edu] Sent: Friday, June 14, 2013 2:59 PM To: dev@ctakes.apache.org Subject: RE: best practices +1 for a BP reference page. Note: I'll try and update the other projects for consistency's sake next w

RE: best practices

--Original Message- > From: Masanz, James J. [mailto:masanz.ja...@mayo.edu] > Sent: Friday, June 14, 2013 2:51 PM > To: dev@ctakes.apache.org > Subject: best practices > > Seems like this (telling people to use FileLocator.java), together with some > of > the reminders you

best practices

Seems like this (telling people to use FileLocator.java), together with some of the reminders you've sent in the last month to dev@, would make good additions to a Best (cTAKES) Practices page. Next week I'll go ahead and create such a page on our Wiki [1], and link it into the left nav bar on