Skip to content
Astera Technology

Keep repeat participation in separate exposure episodes

Use period-specific exposure identity without treating the same participant as a new person.

Define person and episode keys

Synthetic participant P25 has episode EP1 in period 1 with A and EP2 in period 2 with B. Event EV25 explicitly names EP1 even though it arrives in period 2. Local episode records preserve that link; arrival period does not change event subject. Two permitted episodes are not two unique participants or proof of scientific crossover validity.

Person/episode/event associations
RecordPerson/periodVariant/subject
EP1P25/1A
EP2P25/2B
EV25Arrives period 2Names EP1
Download editable CSV ↓

Create the supplied period episodes

  1. Keep P25 identity once
  2. Keep EP1/EP2 separately
  3. Read EV25 named episode
  4. Link EV25 to EP1/A

An event lacking episode evidence remains unresolved where multiple episodes are eligible.

How many participants, episodes and EV25 variant subjects are established?

Show the worked answer

One participant, two episodes, and EV25 belongs to A via EP1. Its arrival in period 2 does not make it a B event.

Match events to their named episode

Filled campaign-operation checks
CaseDecision or resultReason
Count P25 twice as peopleRejectSame participant key
Assign EV25 to current EP2Reject subject changeExplicit EP1 reference
Download editable CSV ↓

Exports include person, period, episode and event-subject columns. A single current-variant field cannot reproduce this history.

Related resources