fixed_new_capacity sets CAP_NEW but not CAP

If we set fixed_new_capacity to a certain value, the model reacts by setting the CAP_NEW parameter to the desired value. The CAP however seems to be unaffected by this, thus, remains zero. Any ideas on why this is happening / is this the desired behaviour?

Start by tracing how fixed_new_capacity is translated into CAP_NEW and CAP in the model, then compare the resulting parameter values. Done means determining whether CAP remaining zero is intended behavior and documenting or correcting the behavior.

Written by the indexing model from the issue text.