To use, extract the
archive
public_mm_lite_3.6.2rc8_binaryonly.zip
and dataset archive
public_mm_data_lite_usabase_2022aa.zip in the same
directory:
$ unzip public_mm_lite_3.6.2rc8_binaryonly.zip
$ unzip public_mm_data_lite_usabase_2022aa.zip
To use, extract the
archive
public_mm_lite_3.6.2rc8_binaryonly.zip
and dataset archive
public_mm_data_lite_base_2022aa.zip in the same
directory:
$ unzip public_mm_lite_3.6.2rc8_binaryonly.zip
$ unzip public_mm_data_lite_base_2022aa.zip
- MetaMapLite 3.6.2rc6 binaryonly
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
-
2020AB UMLS Level 0+4+9 Dataset
(WinZip - 1g),
[sha1sum],
[md5sum]
-
2020AA UMLS Level 0+4+9 Dataset
(WinZip - 1g),
[sha1sum],
[md5sum]
Note: users who have downloaded the 2020AA USAbase
data set distribution before May 15th: The 2020AA
USAbase data set that was published on this website
was missing the SNOMEDCT_US vocabulary. The affected
archives have the following checksums:
md5sum: aacca5e1e3a3791a5ecd8f4d91473cd2 public_mm_data_lite_usabase_2020aa.7z
sha1sum: 675ec4545373b156a04712b3ca72fcdeab90fc6d public_mm_data_lite_usabase_2020aa.7z
md5sum: 000fac4b1be197f86386e4e5e1dabb49 public_mm_data_lite_usabase_2020aa.zip
sha1sum: 1c0a16bdeb5560ce40d7a8be5333aeb0a8cfa2a5 public_mm_data_lite_usabase_2020aa.zip
The archives have been replaced with ones containing the SNOMEDCT_US vocabulary.
-
2020AA UMLS Level 0 Dataset
(WinZip - 877m),
[sha1sum],
[md5sum]
To use extract the
archive
public_mm_lite_3.6.2rc6_binaryonly.zip
and dataset archive
(
public_mm_data_lite_base_2020aa.zip or
public_mm_data_lite_usabase_2020aa.zip) in the same
directory:
$ unzip public_mm_lite_3.6.2rc6_binaryonly.zip
$ unzip public_mm_data_lite_base_2020aa.zip
Change to the
'public_mm_lite' directory and use the
"--indexdir" option to specify the location of the
dataset(shown using a relative path):
$ cd public_mm_lite
$ ./metamaplite.sh --indexdir=data/ivf/2020AA/Base file
The path for the level 0+4+9 dataset is
data/ivf/2020AA/USAbase.
- MetaMapLite 3.6.2rc5 binary only
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
-
2020AA UMLS Level 0+4+9 Dataset
(WinZip - 1g),
[sha1sum],
[md5sum]
Note: users who have downloaded the 2020AA USAbase
data set distribution before May 15th: The 2020AA
USAbase data set that was published on this website
was missing the SNOMEDCT_US vocabulary. The affected
archives have the following checksums:
md5sum: aacca5e1e3a3791a5ecd8f4d91473cd2 public_mm_data_lite_usabase_2020aa.7z
sha1sum: 675ec4545373b156a04712b3ca72fcdeab90fc6d public_mm_data_lite_usabase_2020aa.7z
md5sum: 000fac4b1be197f86386e4e5e1dabb49 public_mm_data_lite_usabase_2020aa.zip
sha1sum: 1c0a16bdeb5560ce40d7a8be5333aeb0a8cfa2a5 public_mm_data_lite_usabase_2020aa.zip
The archives have been replaced with ones containing the SNOMEDCT_US vocabulary.
-
2020AA UMLS Level 0 Dataset
(WinZip - 877m),
[sha1sum],
[md5sum]
To use extract the
archive
public_mm_lite_3.6.2rc5_binaryonly.zip
and dataset archive
(
public_mm_data_lite_base_2020aa.zip or
public_mm_data_lite_usabase_2020aa.zip) in the same
directory:
$ unzip public_mm_lite_3.6.2rc5_binaryonly.zip
$ unzip public_mm_data_lite_base_2020aa.zip
Change to the
'public_mm_lite' directory and use the
"--indexdir" option to specify the location of the
dataset(shown using a relative path):
$ cd public_mm_lite
$ ./metamaplite.sh --indexdir=data/ivf/2020AA/Base file
The path for the level 0+4+9 dataset is
data/ivf/2020AA/USAbase.
To use extract the
archive
public_mm_lite_3.6.2rc3_binaryonly.zip
and dataset archive
(
public_mm_data_lite_base_2018ab_ascii.zip or
public_mm_data_lite_usabase_2018ab_ascii.zip) in the same
directory:
$ unzip public_mm_lite_3.6.2rc3_binaryonly.zip
$ unzip public_mm_data_lite_base_2018ab_ascii.zip
Change to the
'public_mm_lite' directory and use the
"--indexdir" option to specify the location of the
dataset(shown using a relative path):
$ cd public_mm_lite
$ ./metamaplite.sh --indexdir=data/ivf/2018ABascii/Base file
The path for the level 0+4+9 dataset is
data/ivf/2018ABascii/USAbase.
The 3.6.2rc2 version of MetaMapLite is a release candidate for version 3.6.2
- Fixed error in tokenization when calling OpenNLP's Part-of-Speech tagger
- Merged UTF-8 handling code from UTF branch into master
- MetaMapLite 2018 3.6.2rc3 with Category 0 (Base) 2018AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2018 3.6.2rc3 with Category 0+4+9 (USAbase) 2018AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2018 3.6.2rc3 binaryonly
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
- MetaMapLite 2018 3.6.2rc3
USABase (Category 0+4+9) data
Version (WinZip - 1.2GB),
[sha1sum],
[md5sum]
The 3.6.2rc2 version of MetaMapLite is a release candidate for version 3.6.2 that fixes the following issues:
- When using EntityLookup4 (i.e., setting metamaplite.enable.scoring
= false), disabling postagging (i.e., setting
metamaplite.enable.postagging = false) significantly reduces the
number of entities found. On the same collection, I go from a median
of 50 entities per document (with postagging = true) to a median of 0
entities per document (with postagging = false).
- When using MetaMapLite, EntityLookup4 is initialized every time
processDocumentList list is called and again each time processDocument
is called, while EntityLookUp5 is only re-initialized when needed.
- When using a non-standard data directory, the property:
opennlp.en-pos.bin.path: $DATA_DIR/ models/en-pos-maxent.bin must be
set. This property is not supplied in the template config file and MML
falls back to using the hardcoded default value which results in a
crash. It may be helpful to add this property to the generated config
file so if a user is customizing their data directory they will know
to adjust the properties accordingly.
- When using a non-standard data directory, the following properties
must be set for MMI file output or null pointer exceptions are thrown:
- metamaplite.index.directory: $DATA_DIR/ivf/2017AA/Base/strict/indices/
- metamaplite.ivf.meshtcrelaxedindex: $DATA_DIR/ivf/2017AA/Base/strict/indices/meshtcrelaxed
These properties are not supplied in the template config file, and
result in null pointer exceptions. I think that it might be helpful to
add these properties to the generated config file.
- MetaMapLite 2018 3.6.2rc2 with Category 0 (Base) 2018AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2018 3.6.2rc2 with Category 0+4+9 (USAbase) 2018AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2018 3.6.2rc2 binaryonly
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
- MetaMapLite 2018 3.6.2rc2
USABase (Category 0+4+9) data
Version (WinZip - 1.2GB),
[sha1sum],
[md5sum]
The 3.6.1p1 version of MetaMapLite is a bugfix release that fixes the following issue:
- Fixes an error where docid is not propagated to Entity records in output result.
- MetaMapLite 2017 3.6.1p1 with Category 0 (Base) 2017AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6.1p1 with Category 0+4+9 (USAbase) 2017AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6.1p1 binaryonly
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6.1p1
USABase (Category 0+4+9) data
Version (WinZip - 1.2GB),
[sha1sum],
[md5sum]
The 3.6.1 version of MetaMapLite is a bugfix release that fixes the following issue:
- Fixes an error in the method which removes entities
which are subsumed by a larger entity in which some
entities that were not subsumed were removed.
- MetaMapLite 2017 3.6.1 with Category 0 (Base) 2017AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6.1 with Category 0+4+9 (USAbase) 2017AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6.1 binaryonly
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6.1
USABase (Category 0+4+9) data
Version (WinZip - 1.2GB),
[sha1sum],
[md5sum]
The 3.6 version of MetaMapLite is a bugfix release that fixes the following issues:
- Fixes an error in the longest match algorithm in
which entities which were subsumed by a longer enitity
were not removed.
- Includes an example of creating a result formatter.
- Readme documentation has been updated.
- MetaMapLite 2017 3.6 with Category 0 (Base) 2017AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6 with Category 0+4+9 (USAbase) 2017AA UMLS dataset (WinZip - 1g),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6 binaryonly
Version Contains MetaMapLite sources, jar
files, and configuration, but no UMLS dataset.
(WinZip - 250m),
[sha1sum],
[md5sum]
- MetaMapLite 2017 3.6
USABase (Category 0+4+9) data
Version (WinZip - 1.2GB),
[sha1sum],
[md5sum]
The 3.5 version of MetaMapLite is a bugfix release that fixes the following issues:
- The negation status of a concept was not refected in the MMI fielded output.
- The location of chunker model file was not user modifiable.
- The default properties file was missing a reference to the treecodes file used for MMI fielded output.
- Readme documentation has been updated.
The 3.4 version of MetaMapLite now optionally adds scoring
similar to the original MetaMap of concept mapping results
for BRAT output and ranked indexing results for MMI Output
using MetaMap's Ranked Indexing algorithm. MMI Results may
be somewhat different from MetaMap's due to differences in
MetaMapLite's mapping scores which are supplied as input to
the MMI Ranked Indexing algorithm.