alteryx / alteryx/evalml

Future-proof the location of unsupported decomposer frequencies

Abierto
#3,795 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
850
Forks
96
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

we might want to move [unsupported decomposer frequencies] either 1.) into the stl_decomposer module and/or 2.) make it returnable by the decomposer itself. Then we can dynamically know what decomposers support or do not. You could also build the parametrization list and parametrize across STL decomposers in your decomposer test that way.

Part of the motivation behind the move, in my mind, is the answer to "where should I go to find what frequencies are not supported by X Decomposer?"

_Originally posted by @chukarsten in https://github.com/alteryx/evalml/pull/3794#discussion_r1008425041_

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.