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

BSA attempt rate is lower than specified in the simulation setting file (ini file) #562

Open
Naphann opened this issue Jul 25, 2024 · 1 comment
Assignees
Labels
bug Something isn't working physical error models, simulation of new hardware elements

Comments

@Naphann
Copy link
Contributor

Naphann commented Jul 25, 2024

When a QNIC has more than one quantum memory, the photons are generated in batch (photon train) and the BSA would send the results back in batch. The rate at which a BSA can detect photons is specified by a parameter photon_detection_per_second in the BellStateAnalyzer.ned file, which in turns, dictates the temporal separation of the photons (wavepacket) in the train.

When the value is set to 1GHz, the actual attempt rate in the simulation is much much lower, (around 250 MHz), and is probably due to the conversion from detection per second parameter to time interval between photon (line 43).

if (is_active) {
time_interval_between_photons = SimTime(1, SIMTIME_S) / SimTime(getParentModule()->getSubmodule("bsa")->par("photon_detection_per_second").intValue(), SIMTIME_S);
simtime_t first_notification_timer = SimTime(par("initial_notification_timing_buffer").doubleValue());
right_qnic = getExternalQNICInfoFromPort(1);
offset_time_for_first_photon = calculateOffsetTimeFromDistance();
scheduleAt(first_notification_timer, time_out_message);

@Naphann Naphann added bug Something isn't working physical error models, simulation of new hardware elements labels Jul 25, 2024
@Naphann Naphann self-assigned this Jul 25, 2024
@Naphann
Copy link
Contributor Author

Naphann commented Jul 25, 2024

Upon further testing, the cause is line 43, and the time interval from setting 1GHz is

0.00000025801

instead of the expected value of

0.000000001

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working physical error models, simulation of new hardware elements
Projects
None yet
Development

No branches or pull requests

1 participant