Add example with hyperparameters for Kubeflow about tfx HOT 7 CLOSED

Hi @ianhellstrom

Am I correct in assuming that what you want is not hyperparameters, but that input parameters to a pipeline should be exposed in the Pipelines UI? If so, I definitely agree, and it's on my plate of things to do. Let's keep this as a feature request to track the work.

from tfx.

Pipeline parameters, yes. Hyperparameters, maybe. What is the suggested approach for hyperparameters if not through the UI?

from tfx.

I'm also looking for a way to define a value once and have it available in every piece of code. This is especially difficult because the *_utils file is completely separated from the pipeline definition. For now the easiest way is to hard-code your values at the top of the *_utils file, and also do the same in the pipeline definition.

In my case I have a one_hot_encoding that influences the query in the pipeline definition and that same number is needed in the transform in the utils file where I actually encode them. The value i'm trying to pass is the vocabulary size

from tfx.

@DurivetMatthias Ah interesting! Just so I understand correctly, you want an input parameter to a KFP pipeline to be accessible to both the query (which is defined in the pipeline definition file), as well as to some functions defined in the module file that's used as input to Transform?

from tfx.

Exactly

from tfx.

\cc @krazyhaas

We are internally discussing to establish a design pattern to define and pass around intra-component parameter (such as num_steps for Trainer), inter-component parameter applicable to more than one component that needed to be kept in sync (such as @DurivetMatthias case) and pipeline-level global parameter.

from tfx.

Duplicate of #362

from tfx.