Skip to content

QubitWire / Self-directed portfolio project

Perceval pathway: trace postselection through a photonic experiment model

Show how a photonic result changes when the denominator includes every attempt.

Reviewed

Starting skills
Python, probability and basic linear algebra
Portfolio output
Photonic outcome and postselection audit
A useful completion check
Conditional and unconditional denominators both reported
Hardware needed
No
Model boundary
Simulation; any loss or detector parameters explicitly illustrative unless sourced

Quandela’s Perceval resources provide a route into modelling optical quantum circuits and examining their outputs. This pathway focuses on a specific skill: explaining how a selected set of measurement outcomes changes the meaning of a reported success rate. The official documentation and technical note on simulation are starting points, while the portfolio work is an original analysis of a small circuit with clearly stated input states, losses and acceptance rules. It is not a claim of access to Quandela hardware or an open vacancy.

Begin with a circuit small enough that the allowed output patterns can be enumerated and understood. State the input photon occupation, the optical transformation and the detector model. Before running anything, define which outcomes count as accepted and why. Then report both the conditional quality of accepted outcomes and the fraction of all attempts that survives selection. These quantities answer different questions. A clean conditional distribution can coexist with a low overall success probability, and a reviewer should be able to see both without reconstructing the notebook.

The next step is to vary one model assumption at a time. A simple loss parameter or a change in the detector assumption can show how the selected sample changes. Do not label the model as a measured device unless the parameters come from an identified experiment. Use the exercise to distinguish a simulator’s mathematical output from the evidence needed to describe real equipment. The useful question is what the model teaches about the workflow and which physical assumptions remain untested.

Add a deliberately misleading summary and then correct it. For instance, write a sentence that reports only success among accepted runs, then rewrite it with the attempt denominator and selection rule included. This is a communication exercise with technical content: the reviewer should be able to trace every number to a defined set of outcomes. Include a table of raw counts or probabilities, accepted outcomes and rejected outcomes. If the simulated state space becomes too large, state the truncation or resource limit instead of silently changing the experiment.

Questions to take with you

Why report rejected outcomes?

They determine how often the selected result is obtained. Omitting them can make conditional performance look like performance per attempt.

Can a simulator result be called an experiment?

It can be called a numerical experiment if clearly labelled. It should not be presented as a physical-device measurement or a verified hardware service result.

Self-directed project; no vacancy, completed execution, certification or employer endorsement is implied. Pin the software environment before presenting runnable code.

Sources and what they show (2)
Explore other portfolio projects