To Do by Sept 23 - Githubissues

aunarang commented 1 year ago

@Ashley1014

For Anjali (will finish today, Sept 20)

[x] split apart Intro and choices in all rounds and make sure they show up in Survey Flow correctly
[x] change statements in all rounds
[x] change statements in cost/emissions mpl
[x] change statements in pads mpls
[x] create embedded data variables for decision no labels for three rounds
[x] create embedded data variables for decision no labels for pads
[x] add Rx_mpl_full for all rounds
[x] add mpl_full for pads
[x] embed round number
[x] fix display logic for confirm
[x] fix display logic for FMPL
[x] check headers for pads_mpl, R1_mpl
[x] determine final prices and products for pads - in Prices_Sept21 in task spreadsheet
[x] determine final prices for three rounds - in Prices_Sept21 in task spreadsheet
[x] determine final prices for cost/emissions mpl - in Prices_Sept21 in task spreadsheet
[x] change embedded data for prices for pads
[x] change embedded data for prices for three rounds
[x] change embedded data for prices for costs/emissions mpl
[x] make sure all MPL questions are NOT mobile-friendly
[x] create image of twelve-pack writing pads
[x] create embedded data variables for randomizing mpl and pads_mpl headers
[ ] randomize text/images in pads_intro

For Ashley

Sept 20, 2022 Update: I have made it so that there is still a main MPL and then a FMPL, but then after that a "mpl_full" where we show respondents what their decisions imply for the full price list -- this is kind of like R3 in terms of the auto-populated but respondents will not be allowed to go back. We need to disable choice selection for mpl_full -- it is just for display. Then for the lottery we will randomly select one decision from mpl_full in all the rounds.

I also have set it up so I control the randomization of the headers using embedded data, so once you create that you can just copy paste the existing header.

[x] Create timetable for tasks (task and expected completion data for each task) for this week
[x] Update Anjali on progress for each task by expected completion date for each task

1. Prices in MPLs See _PricesSept21 in task spreadsheet

[ ] Can you make prices, auto-populating, calculating and storing wtp, your code generally, works no matter the number of choices? You can use the number of choices embedded data variables. Apply to pads, 3R, emissions, cost, timepref
[x] Three Rounds: make sure prices in MPL, FMPL, full MPL work with the new price list.
[ ] Pads: make sure prices in MPL, FMPL, full MPL work with the new price list.
[x] Cost/Emissions: make sure prices in MPL, FMPL, full MPL work with the new price list.
[x] remember to change the To Do in your code - something to do with FMPL prices
[ ] Three Rounds: make sure wtp is stored with and without dollar sign in embedded data variables
[ ] Pads: make sure wtp is stored without dollar sign in embedded data variables
[ ] Cost/Emissions: make sure wtp is stored without dollar sign in embedded data variables
[x] Three Rounds: make sure auto-populating works in each of these
[x] Pads: make sure auto-populating works in each of these
[ ] Cost/Emissions: make sure auto-populating works in each of these
[x] R1(2,3)_mpl_full: this should work like R3 in that it auto-populates based on wtp from R1_fmpl BUT respondents are not able to make selections. Need to disable choice selection
- See https://community.qualtrics.com/XMcommunity/discussion/10590/how-to-disable-answer-choices-with-js
- See https://community.qualtrics.com/XMcommunity/discussion/14072/disable-one-option-for-multiple-choice
[x] set with Javascript the value for "lower_bound_main_decno_r1" (_r2, _r3) variables already created in Survey Flow. They indicate the decision number for lower_bound_main and upper_bound_main. I am putting this as the decision number in FMPL.
[x] set with Javascript the value for "lower_bound_main_decno_pads" already created in Survey Flow.
[ ] clear respondent selections for FMPL when respondent goes from MPL to FMPL to MPL and then to FMPL if a change is made to MPL selections when going back
[x] disable back button from mpl_full in all three rounds and practice pads round code:
$('PreviousButton').hide(); $('PreviousButton').disable();
[ ] replace QIDs with embedded data
- replace qid for wtp_revise questions with ${e://Field/qid_wtp_revise}
[ ] can you move any console logs in FMPL to mpl_full. They should be in a screen that everyone sees. For cost and emissions mpl, please put it cost and emissions wtp intro_attributes_other in Stage 2.Remaining as everybody sees that q ANd in intro_crt in the "Survey: Part II (Intro)" block
[x] Check what the upper bound is when all A or all B is selected

2. Headers

[x] make sure all MPL questions are NOT mobile-friendly
[x] put headers for pads mpl - correct ones in choice label (names changed, bolded). Now doing a 12-pack (lg) vs. 1-pack instead of white vs. yellow or legal-sized vs. small
[x] put headers for power strip mpl - correct formatting in R1_mpl. Headers should be the same across MPL, FMPL, mpl_full and rounds
[x] put headers for cost mpl - correct formating in cost_mpl, emissions_mpl
[x] time prefs - - correct formating in timepref_1, timepref_2
[x] change names of pads variables - white-->lg, yellow-->sm

No longer need to see if we can make sure rows do not resize to be larger - see other Issue and comments on it (Adding Headers to Matrix)

3. Comment Code

[ ] comment code
[ ] read.me file

No longer needed: 3. Power Strip Lottery Now just randomly select one decision from all decisions across rounds. finish programming power strip lottery for conditions with three rounds finish programming power strip lottery for conditions with one round (Deliberation Only)

To Discuss Later

[ ] does changing the order of A and B in MPL affect code?

Resources https://rpubs.com/john-henry/js_4_ss

aunarang commented 1 year ago

@Ashley1014

I have just updated this issue and my survey with a quite few changes. Thanks for your patience with them. Please let me know if you have any questions, and post your timetable here.

Ashley1014 commented 1 year ago

@aunarang Check out this timetable:	Date	Task
9.26 11:59 PM	Create a timetable and start working on headers
9.27 11:59 PM	Cowork with Anjali and finish headers part, start working on prices
9.30 11:59 PM	Finish Prices part
10.2 11:59 PM	Finish Lottery part

aunarang commented 1 year ago

@Ashley1014

Can you please check this again after working on Prices and mark off what you are done?

Thank you!

aunarang commented 1 year ago

@Ashley1014

Can you put a console log for pads_wtp?

Also, pads_mpl_full when there is a switchpoint does not seem to be pre-populated correctly.

Ashley1014 commented 1 year ago

@Ashley1014

Can you put a console log for pads_wtp?

Also, pads_mpl_full when there is a switchpoint does not seem to be pre-populated correctly.

I think there was already a console log for pads_wtp, and I just fixed the pre-populating issue.

aunarang commented 1 year ago

@Ashley1014

is it possible to clear the selections for fmpl if the respondent changes their answers for mpl? if they were to go back and forth? This would apply to all fmpls - pads, three rounds, cost, emissions

aunarang commented 1 year ago

@Ashley1014

I think I fixed the row resizing problem!! I think it had to do with having multiple lines of text as placeholders for the choice label, although Qualtrics carried those over from the headers.

aunarang commented 1 year ago

@Ashley1014

I think you have not worked on the new prices for cost and emissions. We can consider one condition done if everything in that condition is done.

aunarang commented 1 year ago

@Ashley1014

Conditions needed for now:

Both Info
Cost Info
Emissions Info
Both x Discount
No Info x Discount
No Info

Don't need Deliberation Only

aunarang commented 1 year ago

@Ashley1014

To do for 10/19 in order of priority:

[x] Check off what you have completed above. From what I can tell this is what would be priority for pre-testing:
[x] Three Rounds: make sure wtp is stored with and without dollar sign in embedded data variables
[x] Pads: make sure wtp is stored without dollar sign in embedded data variables (don't need it with)
[x] Cost/Emissions: make sure wtp is stored without dollar sign in embedded data variables (don't need it with)
[x] Can you move any console logs in FMPL to mpl_full. They should be in a screen that everyone sees.
[x] Cost and emissions mpl, please put it cost and emissions wtp attributes_other in Stage 2.Remaining as everybody sees that q
[ ] clear respondent selections for FMPL when respondent goes from MPL to FMPL to MPL and then to FMPL if a change is made to MPL selections when going back

Not as much of a priority but if there is time tomorrow:

[x] making sure auto-populating works no matter the number of statements for time preferences

aunarang commented 1 year ago

@Ashley1014

Clear respondent selection resources:

aunarang commented 1 year ago

@Ashley1014

Please check if you have moved all the console logs and code with embedded data variables from FMPL

[ ] This means you have to check the bound and wtp variables for each version of the MPL for pads, the three rounds, and cost and emissions

It does not seem like R2 and R3 is working, at least when I choose all A or B

aunarang commented 1 year ago

@Ashley1014

I think you coded lower_bound_main_decno_r1 incorrectly for all A and all B. Right now it seems like all A is 73 and all B is 71.

We should use the new def of a switchpoint for this

[ ] - All A--> let the lower_bound_main_decno_r1 of switch be 74 (num_totaldecisions_1r) (only lower bound strictly speaking but I will make lower and upper equal to each other)
[ ] - All B--> let the lower_bound_main_decno_r1 of switch be 0 (num_totaldecisions_1r) (only upper bound strictly speaking but I will make lower and upper equal to each other)
[ ] - Switch--> lower_bound_main_decno_r1 is between 1 and 72
[ ] - And then I will calculate wtp as a function of lower_bound_main_decno_r1, the decision number (and more).

I need the decision number of the switchpoint, and then I can calculate wtp in survey flow. Your switch row variables are a little confusing to me. Not clear what existing variables to use (If I know switch row in main MPL and switch row in main FMPL I can also calculate WTP).

What would also work is the row number in the MPL and then I can calculate the decision number.

aunarang commented 1 year ago

@Ashley1014

To Do for 10/19

[x] fix and check decision_number of switchpoint for MPL in three rounds so that all A is 74 and all B is 1
[ ] store and check decision_number of switchpoint for FMPL in three rounds so that all A is 74 and all B is 1 in e.g. lower_bound_fmpl_decno_r1
[ ] store and check switch_row and switchpoint variables for cost MPL
[ ] store and check switch_row and switchpoint variables for cost FMPL
[ ] store and check switch_row and switchpoint variables for emissions MPL
[ ] store and check switch_row and switchpoint variables for emissions FMPL
[ ] move and check all the console logs and code with embedded data variables (bound and wtp) from FMPL for pads
[ ] move and check all the console logs and code with embedded data variables (bound and wtp) from FMPL for three rounds
[ ] move and check all the console logs and code with embedded data variables (bound and wtp) from FMPL for cost
[ ] move and check all the console logs and code with embedded data variables (bound and wtp) from FMPL for emissions

If possible today or tomorrow:

[ ] clear respondent selections for FMPL when respondent goes from MPL to FMPL to MPL and then to FMPL if a change is made to MPL selections when going back

aunarang commented 1 year ago

Note to self:

switchpoint 1 = all effective is selected 2 = all traditional is selected 3 = means there exists a switchpoint

aunarang commented 1 year ago

@Ashley1014

To Do for 10/20

Notes

Please check all cases when you are checking.

For MPL questions (pads, cost, emissions, 3R), please check wtp variables and stored variables related to decision numbers

switch in MPL and switch in FMPL
switch and all A
switch and all B
all A
all B

In general, please have console logs for all embedded data variables in which you store values, as ultimately this are the ones I will be using.
I think it would also be helpful you post checklists for yourself on Github for checking, as opposed to me. I think much back and forth can be avoided and errors I catch can be prevented this way. This is what a lot of programming is.

Thanks!

FOR ONE OF THE FOUR NON-DISCOUNT TREATMENTS

To check: For R2, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For R3, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For cost, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For emissions, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For pads, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To Discuss Later

Can we set lower and upper bound equal to each other

aunarang commented 1 year ago

@Ashley1014

To Do for 10/20/22

FOR ONE OR BOTH OF THE TWO DISCOUNT TREATMENTS: No Info x Discount, Both x Discount

To check: For R2, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For R3, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For cost, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For emissions, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

To check: For pads, please check wtp variables AND stored variables related to decision numbers for both display orders

[ ] 1. switch in MPL and switch in FMPL
[ ] 2. switch and all A
[ ] 3. switch and all B
[ ] 4. all A
[ ] 5. all B

aunarang commented 1 year ago

@Ashley1014

To Do for 10/24

[x] can you move any console logs and calculating wtp code for cost

I need two copies of these code -- in two questions. For cost and emissions mpl, please put it cost and emissions wtp

intro_attributes_other in "Stage 2.Remaining" block as everybody sees that q AND in
intro_crt in the "Survey: Part II (Intro)" block.
[x] can you move any console logs and calculating wtp code for emissions

I need two copies of these code -- in two questions. For cost and emissions mpl, please put it cost and emissions wtp

intro_attributes_other in "Stage 2.Remaining" block as everybody sees that q AND in
intro_crt in the "Survey: Part II (Intro)" block.
[x] can you check off the tasks in the github comments above to make sure you cover everything PLEASE!

Thank you!

aunarang commented 1 year ago

@Ashley1014

To Do for Weekend of the 29th

I think we should work on these things for _nokeep and _no_revise:_

[x] set embedded data variable for revised
[x] Anjali will try out the display logic for that
[x] fix the back and forth bug related to checked revised function not being applied correctly (embedded data not set?)
[ ] delete code for display logic and then copy code from working copy to real copy

Adapt the above to the _yesquestions in R3

[ ] set embedded data variable for revised
[ ] Anjali will try out the display logic for that
[x] fix the back and forth bug related to checked revised function not being applied correctly (embedded data not set?)
[ ] change how R3 mpl_yes and R3_fmpl_yes_keep are pre-populated such that the text entry WTP is the lower bound instead of the upper bound and ensuring that the max and min WTP are represented appropriately (as all A or all B)

For pads fmpl, and all FMPL qs in R1 and R2

if not revised: do nothing
if revised: apply notrevised or checkedrevised function
[ ] pads fmpl: apply the notrevised or checkedrevisedfunction to have the effect of clearing respondent selections if MPL is revised
[ ] R1 fmpls: apply the notrevised or checkedrevisedfunction to have the effect of clearing respondent selections if MPL is revised
[ ] R2 fmpls: apply the notrevised or checkedrevisedfunction to have the effect of clearing respondent selections if MPL is revised

Ashley1014 / qualtrics

To Do by Sept 23 #22