Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add new UNC survey and labels #119

Merged
merged 3 commits into from
Sep 7, 2024
Merged

Conversation

mattwigway
Copy link
Contributor

This adds trip label configs for the unc-ebike OpenPATH deploy, as well as a custom onboarding survey.

We would ideally like to display the replaced mode choice only when the selected mode is e-bike, but I wasn't sure how to specify that in the config. Our onboarding survey is trivial because we have a much more extensive survey where participants can choose at the end whether to participate in OpenPATH data collection, so we'll be generating opcodes within that survey so we can link OpenPATH to external survey responses, to avoid having people re-enter the same information. My understanding is that it is not possible to remove the onboarding survey completely, so we added a trivial survey.

I haven't tested any of this, I wasn't sure how to test configs locally, but if that's possible I'd be happy to do local testing.

@shankari
Copy link
Contributor

shankari commented Sep 7, 2024

@mattwigway

We would ideally like to display the replaced mode choice only when the selected mode is e-bike, but I wasn't sure how to specify that in the config.

It is already specified here
https://github.com/e-mission/nrel-openpath-deploy-configs/pull/119/files#diff-60c020caa0849b84d7f3fa41a419accb60b2fac560e1d7af3582c230188fe0b8L20

My understanding is that it is not possible to remove the onboarding survey completely, so we added a trivial survey.

Sure, makes sense

I haven't tested any of this, I wasn't sure how to test configs locally, but if that's possible I'd be happy to do local testing.

Your environment is specific to your program, so feel free to edit and test as many iterations as needed.
Just make sure to test with an opcode from the "test" subgroup - e.g. generated using
https://unc-ebike-openpath.stratus.nrel.gov/join/?sub_group=test

In the admin dashboard, you can filter by subgroup. So you can filter out all the test data before your analysis.
So you can have multiple test phones, label trips as e-bike when they were not, change surveys and labels multiple times,...

@mattwigway
Copy link
Contributor Author

@shankari Thanks! I have updated mode_studied to match the way it is spelled in our labels file, and switched to pre-generated opcodes in the config per our email discussion. I think this is ready for merge.

Comment on lines +73 to +85
"car": "Car",
"walk": "Walk",
"bike": "Regular bike",
"ebike": "E-bike",
"bus": "Bus",
"taxi": "Taxi",
"ridehail": "Uber / Lyft",
"train": "Train / Amtrak",
"air": "Airplane",
"not_a_trip": "Not a trip",
"other": "Other",
"home": "Home",
"work": "Work",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be in Spanish?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we are in the process of hiring a translator so this is just a placeholder for now

Copy link
Contributor

@shankari shankari Sep 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you can see from the admin dashboard, we detect the phoneOS automatically. I understand that you have a placeholder survey, but maybe you could have an interesting question here like "what do you expect to get out of this data collection" with potential answers like "understand my carbon footprint" or "contribute to better understanding of the program" or ....

I personally hate getting asked questions that can be inferred automatically

@shankari shankari merged commit c1dd0e2 into e-mission:main Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants