Why learner has hard-code about dataset, such as, different dataset uses different learning rate control policy. about pocketflow HOT 3 OPEN

We are planning to remove the dependency on data set's name in UniformQuantLearner and NonUniformQuantLearner.
For most scenarios, such hard code can be replaced by defining FLAGS variables for higher flexibility. Particularly, the setup_bnds_decay_rates function you listed can be removed by defining a decaying factor for learning rate, as we did in UniformQuantTFLearner.
For WeightSparseLearner, the skip_head_n_tail variable can also be changed into a FLAGS variable.

from pocketflow.

Enhancement required: remove the hard code related to data set's names in learners' implementation.

from pocketflow.

Got it. Thanks your kind reply.

from pocketflow.