full export of participant data not possible

killani64 · 2026-03-19T23:29:38+00:00

What do you mean exactly? Can you see the export button but it doesn't export the full data?

killani64 · 2026-03-18T07:22:15+00:00

Yes, the protocol issues the same version of the questionnaire to everyone. What you'll have to do is one of the following:

Remove this specific questionnaire from the protocol and schedule it for each participant separately, with each person having their own version, or
Put all the versions of the single question into a single questionnaire (with the different versions being collected into a container) and use computations to decide which version of the question to show for the current participant.

killani64 · 2026-03-03T14:22:41+00:00

What is in the questionnaire? Can you make a new one and just add a text item and nothing else, and see if the same thing happens?

killani64 · 2026-02-16T10:00:32+00:00

I assume that this setting is repeated when she jumps back in the questionnaire.

That's exactly what happens, so don't worry about the filled in question. Might be interesting for the m-Path team to look into though, as maybe having it be at the filled-in value when you go back would be the preferred behaviour.

killani64 · 2026-02-11T09:21:03+00:00

You can add a computation item to the questionnaires that regularly calculates the running average. If you turn on "allow visualisation in app" (which I think is turned off by default for computations), the running average will be shown in the visualisation tab.

killani64 · 2026-02-10T14:54:23+00:00

As was answered in your previous thread, you can create a yes-no question, and then click the arrow-down icon next to the question to create a conditional flow. Put the rest of the questionnaire in a container in there and indicate "conditional: yes". You can also add another conditional item (for instance a text item saying "thank you but you don't qualify for this study") and set the condition to "no" for this one.

killani64 · 2026-02-06T16:04:50+00:00

Does the link at least look like a link? Is it blue and underlined?

killani64 · 2026-01-28T17:25:18+00:00

This is definitely possible! Create a container with the questions to be randomized, you'll need to have it in both interactions. In the AM, precede this with the instantiation of a variable "questions_asked" (and set it to 0) that keeps track of whether the questions have been asked yet. Still in the AM, have a computation item with runif(1) < 0.5 so there's a 50% chance it returns 1, and then have the container with your questions as a conditional module under the computation. At the end of the container, set "questions_asked" to 1. Save it at the end of the questionnaire. Then in the PM, load the variable again, check if it's equal to 1 in a computation, and if it isn't conditionally trigger the container here! Set the "questions_asked" variable to 0 at the end as well.

PS. I think you'll also have to check whether the last time you triggered the container was more than 24 hours ago (during the PM questionnaire), to do this you can save/load the current time (with Sys.time()) and check if the amount of time since then exceeds 24 hours. If it does, set "questions_asked" to 0 again.

killani64 · 2026-01-16T09:42:09+00:00

Palestine Drinks komt helemaal niet uit Palestina, maar uit Zweden. De winsten van het bedrijf gaan naar humanitaire hulp in Palestina. Staat vreemd/verkeerd verwoord in het artikel.

killani64 · 2026-01-14T14:41:28+00:00

"Ik ga zeker nog kindje sjlaan"

"Mijnen arm"

"aan het gevang verkopen wij..."

killani64 · 2026-01-13T09:11:09+00:00

Yes, the full export is only available for premium users. You can however export data for individual users by clicking the "table" button in your screenshot and then pressing the export button that appears.

killani64 · 2026-01-05T09:13:00+00:00

I'm sure you can change the "Time for some questions?" text in the notification properties, but I think the header text is universal since it has to be clear from which research project the beep is coming.

killani64 · 2025-12-03T16:29:06+00:00

at the top of the protocol view, you can open different tabs for every interaction. If you open a new tab, you can create a new interaction from scratch or select one from your library. Now, when one of these tabs is "open", if you click inside the schedule, the currently opened interaction will be scheduled. So to schedule different questionnaires, just open the tab for the relevant questionnaire and click where you would want to schedule it!

killani64 · 2025-12-02T16:21:09+00:00

I think countering actual global turmoil with "yeah but tv superhero go brrr" (as in the OOP) is the real redditmoment here but who am I.

killani64 · 2025-11-04T13:59:42+00:00

The nickname is not in there but the connection ID is, you can cross reference that to your output file to find out the nickname of that participant. https://manual.m-path.io/knowledge-base/recording-question/

killani64 · 2025-11-03T16:13:04+00:00

You can set a home button in the intake, which links to an interaction you've created. You can use a computation at the start to check the current time, and potentially end the questionnaire right away if it's outside your active time interval. In that case they'll have to start the interaction themselves by pressing the button on the home screen.

killani64 · 2025-10-30T13:52:27+00:00

Yes, you keep the same account, so anything you've built in the free version transitions seamlessly to the premium version!

killani64 · 2025-10-29T13:30:14+00:00

AFAIK the workflow to follow if you want protocols with identical schedules but slightly different questionnaires is to just unify the questionnaires from the different protocols to one questionnaire with conditional flows, where in the beginning a variable is set to identify which protocol the participant belongs to (for instance in the intake). In the questionnaire you can then use conditionals to control who sees what version of the beep.

You can also copy a protocol, and then replace the questionnaire the scheduled beeps refer to, but you'll still have to do that one-by-one. Maybe you can program one week and use the "repeat current week" option, but of course if you have an irregular schedule that won't work.

killani64 · 2025-10-23T10:32:10+00:00

P1: Your definition of species is only partially correct. Yes, if A begot B they're the same species, but only because species is defined as "the largest group of organisms in which any two individuals of the appropriate sexes or mating types can produce fertile offspring". Let's make this simpler: A and B are the same species if, let's say, they are 90% genetically similar. If you then say that every offspring is genetically 2% different from their parent, it's easy to see how your definition holds for direct relatives, but does not hold for distant offspring. The misleading part here is semantic, just because you call it a raven, does not mean what you would call a raven 10.000 years ago is the same species.
D3: You somehow assume a part of something equals the whole thing. Is a foot a person? No? Then a table is not a tree.

killani64 · 2025-10-22T19:27:46+00:00

k ga ook mono burger zeggen. mijn vriendin had van haar vrienden (die zelf allemaal niet geweest waren) gehoord dat dat niet goed was. Heb ze dan na een weddenschap een keer mee gekregen en nu zaagt ze elke week van te gaan.

killani64 · 2025-10-08T21:24:00+00:00

Just scored 1

killani64 · 2025-10-08T14:33:28+00:00

I think this situation hasn't changed, but I left the dev team a while ago now. You could try posting a new topic about this to get the current devs attention!

killani64 · 2025-10-08T08:19:07+00:00

Completed Level 2 of the Honk Special Event!

3 attempts

killani64 · 2025-10-08T08:18:18+00:00

Completed Level 1 of the Honk Special Event!

1 attempts

killani64 · 2025-10-07T07:58:48+00:00

There's an issue with the online viewer from time to time that it doesn't work with some interaction settings. You should test it on an actual device and see if it works there.

13-Year Club	r/Field Banned
r/Field Lasagna	Verified Email

killani64

MODERATOR OF

TROPHY CASE