Our current implementation is based on POC work, which returns the evaluated score based on the ratio between current usage versus the estimated usage.
However, the estimated usage could be difficult to derive. For example, tags could impact expected usage.
In order to address these corner cases, we need to revisit all the soft constraint definition.
The requirement is basically:
- Continous distribution.
- Normalized to a [0.0 ~1.0] number.
- Any two estimated scores should be comparable and different if the two potential assignment will cause different usages.
Our current implementation is based on POC work, which returns the evaluated score based on the ratio between current usage versus the estimated usage.
However, the estimated usage could be difficult to derive. For example, tags could impact expected usage.
In order to address these corner cases, we need to revisit all the soft constraint definition.
The requirement is basically: