... | ... | @@ -11,9 +11,11 @@ and general `netatmoqc` options. For info about specific subcommands and the |
|
|
options that apply to them only, **please run `netatmoqc SUBCOMMAND -h`** (note
|
|
|
that the `-h` goes after the subcommand in this case).
|
|
|
|
|
|
**N.B.:** A typical `netatmoqc` run with the (preferred) clustering method
|
|
|
[HDBSCAN](https://hdbscan.readthedocs.io/en/latest/index.html) seems to need ca.
|
|
|
**20 GB** of RAM and takes a couple of minutes to finish. Other implemented
|
|
|
**N.B.:** When using the (preferred and default) clustering method
|
|
|
[HDBSCAN](https://hdbscan.readthedocs.io/en/latest/index.html), a typical
|
|
|
`netatmoqc` run (~40000 unique station IDs per DTG) needs ca. **6 GB** RAM and
|
|
|
takes between 1 and 2 minutes to complete (on a machine equipped with Intel(R)
|
|
|
Xeon(R) CPU E5-2640 v3 @ 2.60GHz, 16 physical cores). Other implemented
|
|
|
clustering strategies have more modest RAM requirements, but:
|
|
|
* [DBSCAN](https://scikit-learn.org/stable/modules/generated/sklearn.cluster.DBSCAN.html)
|
|
|
results are not as good as HDBSCAN's in our context
|
... | ... | |