Quick TODO by Dec 18 (?)

[aunarang]

@Ashley1014

Hey Ashley!

I decided to put the pads questions back in after some pre-testing. I was wondering if you could do the following. I think these tasks should be quick. If you could have them done by December 18 that would be great, but if not, let me know and we can figure it out.

• [x] Pads: adapt code for going back and forth (clearing selections if mpl revised, etc.)
• [x] Pads: see what else needs to be adapted. I don't exactly remember at what point I told you to stop adapting for pads because I moved fmpl and mpl_full out.
• [x] See where in code condition_no or assignment are used, as I might add some conditions that should not require new questions, but I want to make sure the use of condition_no in your code can account for new conditions. Maybe we can replace them with embedded data variables
• [x] delete code for disabling back button on mpl_full. I decided to let respondents go back. I did do this already but I think you should change this in your local copy as well.
• [x] Delete debugger statements

Anjali

• [ ] create necessary embedded data variables once we know how condition_no is used in your code. Maybe you can post excerpts as comments to this issue

Thank you!

[aunarang]

@Ashley1014

Any update?

Can we add one more task?

• [x] Adapt code for R1/R2 to R3_mpl_yes_new, R3_fmpl_yes_new after it is a created. In effect this means, I want to try not running code for prepopulating R3_keep to be based on revised WTP such that R3 becomes like R2 for those who decide to revise.
• [x] R3_mpl_yes_new_disc

Also as a headsup, I may change the size of the discount.

Anjali

• [x] create R3_mpl_keep_new, R3_mpl_disc_keep_new and R3_fmpl_keep_new

[aunarang]

@Ashley1014

Can you put the following code files into a folder called "older code"?

• [x] r1_certain_switch
• [x] r1_fmpl_disc
• [x] r2_certain_switch
• [x] r3_certain_switch
• [x] r3_fmpl_delib
• [x] r3_fmpl_yes_keep
• [x] r3_fmpl_yes_revise
• [x] r3_mpl_delib
• [x] r3_mpl_yes
• [x] r3_mpl_yes_disc

Thank you!

[Ashley1014]

usage of condition_no: