Hi Team (with special thanks going to Bryan for his ongoing help here),
But something struck me as I was looking to collapse two price functions into one for one concept in an Alternative specific design I am creating, and will be relevant, I believe, for other applications.
I followed Bryan's advice in combining two prices into one (a toll road charge and a daily parking fee for the alternative specified for car) and after reading the instructions listed in the help from the stand alone LC Help Appendix C where it describes the process for creating a continuous price function by exporting the csv file and then altering the levels to be continuously coded and "User-specified" in the LC options for a single run estimation, rather than part-worth estimated and I can see how this is achieved by collapsing two columns together (by using the actual price values and subtract from each value the mean of the values, which will differ between car with parking with toll and car parking without toll).
However how do I treat the price functions for the other Alternative Specific Concepts in the design? Such as Bus and Tram...
A look at this simple design should make clear what I'm trying to achieve.
What I mean by this is that each alternative specific concept has its price variable in a different column in the design matrix and hence the response file. Should I make all the price functions in the ALT-Spec design continuous (for consistency) or can I just have the car concept estimated as continuous and the other concepts as partworths?
The transformation of one price variable to continuous but I don't know what to do with the others, what would be best practice?