I did some brainstorming on package names. I was thinking words of interest were "pipeline", "ensemble", "machine learning", "parallel", or "classification". Of these I thought that "Ensemble Learning Models" was a nice name because it abbreviates to elm, which is kind of related to the topic of land cover (e.g. a tree icon for the package later). Also from elm.pipeline import * is easier to remember and more easily pronounced than from iampl.pipeline import *. I think "ensemble" is a word with a lot of good recognition in the satellite and weather data communities as a robust approach to deterministic weather models or data analysis, and it usually implies parallelism in that context. I think we should make a decision on the package name soon before the iamlp name becomes too engrained.
From flowdock:
I did some brainstorming on package names. I was thinking words of interest were "pipeline", "ensemble", "machine learning", "parallel", or "classification". Of these I thought that
"Ensemble Learning Models"
was a nice name because it abbreviates toelm
, which is kind of related to the topic of land cover (e.g. a tree icon for the package later). Alsofrom elm.pipeline import *
is easier to remember and more easily pronounced thanfrom iampl.pipeline import *
. I think "ensemble" is a word with a lot of good recognition in the satellite and weather data communities as a robust approach to deterministic weather models or data analysis, and it usually implies parallelism in that context. I think we should make a decision on the package name soon before theiamlp
name becomes too engrained.