The reference stated in the documentation, Draper and Smith 1981, pp. 225–226, is where I got the method from. Consult that source if you want to reproduce TRANREG's results. ... View more

I wrote that code decades ago and have since retired. I can't say I recall details beyond those in the documentation. https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.4/statug/statug_transreg_details02.htm   ... View more

You are welcome! If I helped you, please mark my answer as a solution. Also, please feel free to tag me in the future if you have other questions about designing choice experiments in SAS. Warren ... View more

You are first creating a design with the choiceff macro then using the choiceff macro to evaluate it. The first (design creation step) works. Your error was in the evaluation. The problem was you were evaluating a design that has an index variable created in the first step. That index variable refers back to the original candidate set of 68 alternatives. But your design that you use as a candidate set has only 50 observations. So as soon as the macro encounters an index greater than 50, you have an error. The fix is to create a new index, shown before the RUN below, that corresponds to desres2 (your new candidate set) and not to randomized (your first set of candidates).   data desres2; set desres2; format x1 price. x2 location. x3 financial. x4 health. x5 browsinghistory. ; label x1 = "Price" x2 = "Location" x3 = "Financial" x4 = "Health" x5= "Browsinghistory"; rename x1 = Price x2 = Location x3 = Financial x4 = Health x5 = Browsinghistory ; index = _n_; run; As a macro writer, I tried really hard to anticipate and check for every error so it would not result in an IML error, but I missed that one. I retired 4.5 years ago, so it is too late to go back and tweak it. If you have other choiceff or mktex problems, tag me, and I will take a look.     ... View more

I'll look at it.  ... View more

Perhaps you are asking about automatic variables?  https://documentation.sas.com/doc/en/lrcon/9.4/p0e0mk25gs9binn1s9jiu4otau29.htm ... View more

In the KM chapter I mentioned, find the section "Adding a Custom Header above the At-Risk Table". It provides a basic illustration of annotation. The text mentions annotation statements.  In SG plotting procedures (not relevant here but mentioned to provide context), you provide an annotation data set. In a graph template and SGRENDER, you provide annotation statements. ... View more

I'll try to look over what you are doing tomorrow. In the mean time, you should know that this is the latest version of the KM plot modification examples.  https://support.sas.com/documentation/onlinedoc/stat/151/kaplan.pdf ... View more

Don't write code like that. Just because you can, does not mean you should. When I worked as a SAS developer, I wrote macros that were thousands of lines long and were callable by other macros that were even longer. There were many macro statements, macro functions, and macro variables.  Still, my first rule of macro writing was NEVER use the macro language where you don't have to, and equivalently, ALWAYS use ordinary SAS instead when you can. In a DATA step, that means access the macro variables when you can via SYMGET, process their values in ordinary DATA step variables by using ordinary DATA step statements and functions, and if necessary, send the results into macro variables via SYMPUTX. ... View more

It is fine as is. If you want the value to be printed as "1.00" then assign a 5.2 format to that column. ... View more

https://blogs.sas.com/content/sastraining/2017/06/27/how-to-perform-an-operation-on-all-numeric-or-all-character-variables-in-a-sas-data-set/ ... View more

If member in ("A", "B) and code = "T" and payer in ("V") then do; thisfield = "CCC"; output; end; If you are asking to conditionally output only after setting thisfield, you would do it as above.  ... View more

Your where clause is a data set option. So delete the semicolon in front of it.   ... View more

If you are looking for a randomized block design (I'm not sure from your question) use this macro. https://support.sas.com/rnd/app/macros/MktBlock/MktBlock.htm ... View more

Interactive procedures preceded ODS by decades. Interactive procedures do not end until they hit a QUIT statement. If you put ODS OUTPUT statements after the PROC statement and appropriately end interactive procedures, everything will work as you expect.   https://documentation.sas.com/doc/en/statug/15.3/statug_ods_examples06.htm ... View more