On Aug 16, 2014, at 4:04 PM, Steven Bethard beth...@cis.uab.edu [umls-similarity] <umls-similarity@yahoogroups.com> wrote: > On Jul 30, 2014, at 9:55 AM, Bridget McInnes btmcin...@gmail.com > [umls-similarity] <umls-similarity@yahoogroups.com> wrote: >> The icpropagation files need to go into the: >> /var/www/umls_similarity/icpropagation/ > [snip] >> create-icfrequency.pl ICFREQUENCY_FILE INPUTFILE > [snip] >> create-icpropagation.pl ICPROPAGATION_FILE ICFREQUENCY_FILE > > Thanks, this solved the problem. Some notes for anyone else who has to do > this: > > * The create-icfrequency.pl script took about 20 minutes on a text file of > about 160M words. > * The create-icpropagation.pl script took about 10 minutes > * The icpropagation file has to be named > /var/www/umls_similarity/icpropagation/icprop.msh.par.chd for the sever to run
Ok, it looks like this didn’t completely solve the problem because when I try sources other than MSH, I get errors like: "Could not open file /var/www/umls_similarity/icpropagation/icprop.fma.par.chd” How do I run the create-ic* scripts so that they generate all the different icprop.* files that the server might search for? It seemed like maybe I needed to use the --config option, but I couldn’t find the documentation on what a config file looks like. And, assuming someone can point me to the config file documentation, do I need to run the script once for each combination of MSH/FMA/OMIM/SNOWMEDCT/UMLS_ALL, CUI/PAR/CHD/RB/RN? Is there a way to make sure I have all the possible combinations? Steve
signature.asc
Description: Message signed with OpenPGP using GPGMail
