proport marks combinations as young when we have zero shipment history in buckets but correctly when

Hi All,

7.3.0.2

Background:-

We are seeing that the engine is not providing baseline forecast for some combinations when we have zero qty in the history. we are observing that when we have null values in the history the proport procedure is behaving correctly. This is very glaring to the users and we are unable to explain why.

Question:-

1) Does the proport treat a zero differently from null? Which parameter dictates this ? In our instance  init_params_0.proport_missing has value_float=0

In the attached file..the green combinations are active but the others are shown as young.