@@ -39,7 +39,10 @@ where `[MetaCLADE2_DIR]` is MetaCLADE2 installation directory.
...
@@ -39,7 +39,10 @@ where `[MetaCLADE2_DIR]` is MetaCLADE2 installation directory.
MetaCLADE2 is no more compatible with the Pfam27-based library built for MetaCLADE v1.
MetaCLADE2 is no more compatible with the Pfam27-based library built for MetaCLADE v1.
An improved version of the model library (currently based on Pfam32) can be downloaded here: [metaclade\_pfam32.tar.gz](http://gitlab.lcqb.upmc.fr/vicedomini/metaclade2)
An improved version of the model library (currently based on Pfam32) can be downloaded here: [metaclade\_pfam32.tar.gz](http://gitlab.lcqb.upmc.fr/vicedomini/metaclade2)
The gzipped tar archive has to be extracted with the command `tar -xf metaclade_pfam32.tar.gz`.
The gzipped tar archive has to be extracted with the command
```
tar -xf metaclade_pfam32.tar.gz
```
By default the `CCMs` and `HMMs` directories are expected to be found in the `data/models/` path relative to the main MetaCLADE directory.
By default the `CCMs` and `HMMs` directories are expected to be found in the `data/models/` path relative to the main MetaCLADE directory.
It is however possible to put MetaCLADE's model library in a custom location, and set the absolute paths of both the `CCMs` and `HMMs` directories
It is however possible to put MetaCLADE's model library in a custom location, and set the absolute paths of both the `CCMs` and `HMMs` directories
with a user configuration file (see the section below).
with a user configuration file (see the section below).
