if you have a chance, could you have a look at my follow-up comment on the post regarding the coding of missing prices in the MBC design matrix?
I was futzing with an exported simulator tool and experienced the same phenomenon that I expected / described in my comment:
With the linear and loglinear specification there is always a point/value (input for simulator) where the transformed coding (model tab) results in a 0 (reflecting that no utility is assigned at that value). When I set that input value to n/a the resulting shares are the same as before.
(btw: What is (or can be) expressed by "n/a" in the simulator?)
Now with regard to the question in my earlier post:
What is the reasoning behind the following?:
The absence (i.e. non-availability) of an item or price level (reflected by the 0 coding of the respective price level in the design matrix) results in the same utility level of the choice option (containing the non-available item) as when the item is available at that particular price level described above.