Recommendations for EPR-type simulations
Simulation programs for EPR-type experiments have the problem that the simulated model is not obvious. In particular, it is not obvious whether locality is violated. Also the separation of laws of "nature" (i.e., of model), experimenter's choices and analysis of results. The latter two should be independently modifiable in order to allow comprehensive analysis of the simulation program.
In order to separate analysis of the simulation model from the model itself, the simulation program should be separated from the analysis program. In addition, the settings of the detectors should be read from input files. The simulation should produce output files that can be read to an analysis program.
The following recommendations enforce factual definiteness and locality. In addition, they separate laws of "nature" from analysis. In addition, the recommended file formats permit integrity checks.
The simulation model shall consist of two or three distinct programs: one that simulates the source that produces pairs of particles; and one or two that simulate detection of particles - the two detectors shall be simulated separately but the same program may be used.
The emission simulation program shall input the number of particle pairs to be emitted (e.g., from command line) and produce two files, below called particle files.
The mesurement simulation program shall input one of the particle files produced by the emission programs and a settings file, and output a result file.
In addition an analysis program is needed. It is not part of the simulation model and need not be created by the author of the simulation program. Any number of analysis programs may be used. An analysis program shall read two settings files and two result files and output the results of the analysis (to a file or stdout or display or whatever).
All files mentioned above shall be ASCII files that contain header lines, data lines, and a footer line in this order. The header and footer lines begin with the '#' charcter followed by one or more spaces. The data lines begin with one or more spaces followed by the number of particle pair (starting from 1) followed by one or more spaces. The rest of the line depends on the file type. Files may also contain blank lines but they mean nothing and shall be ignored. Any lines after the footer shall also be ignored.
The first header line shall contain the name of the file. The footer line shall contain the same name.
A particle file shall have three other header lines. The second one identifies the simulation model (e.g., the name of author, the name of model). The third lines contain date and time for indentification of the run. These two lines must be identical in the two particle files produced at the same time. The fourth header line be different in the two files and contain the letter 'A' or 'B'.
Each data line shall end with "hidden" variables of the particle, which shall be encoded with visible ASCII characters and spaces.
A settings file shall have one additional header line that contain the letter 'A' or 'B'. Each data line shall end with a setting value in degrees (as an integer or real number).
The resul file shall have second, third, and fourth header lines that are exact copies of the second, third, and fourth header lines of the particle file. The fifth header line shall be an exact copy of the second header line of the settings file. Each data line shall end with result of the detection as a '+' or '-' character except if the particle is not detected at all, which shall be encoded with a '?' character.
These recommendations can be followed if the simulation model satisfies locality, factual definiteness and counterfactual definiteness. Other simulations should follow as many of these recommendations as the model allows.
In order to separate analysis of the simulation model from the model itself, the simulation program should be separated from the analysis program. In addition, the settings of the detectors should be read from input files. The simulation should produce output files that can be read to an analysis program.
The following recommendations enforce factual definiteness and locality. In addition, they separate laws of "nature" from analysis. In addition, the recommended file formats permit integrity checks.
The simulation model shall consist of two or three distinct programs: one that simulates the source that produces pairs of particles; and one or two that simulate detection of particles - the two detectors shall be simulated separately but the same program may be used.
The emission simulation program shall input the number of particle pairs to be emitted (e.g., from command line) and produce two files, below called particle files.
The mesurement simulation program shall input one of the particle files produced by the emission programs and a settings file, and output a result file.
In addition an analysis program is needed. It is not part of the simulation model and need not be created by the author of the simulation program. Any number of analysis programs may be used. An analysis program shall read two settings files and two result files and output the results of the analysis (to a file or stdout or display or whatever).
All files mentioned above shall be ASCII files that contain header lines, data lines, and a footer line in this order. The header and footer lines begin with the '#' charcter followed by one or more spaces. The data lines begin with one or more spaces followed by the number of particle pair (starting from 1) followed by one or more spaces. The rest of the line depends on the file type. Files may also contain blank lines but they mean nothing and shall be ignored. Any lines after the footer shall also be ignored.
The first header line shall contain the name of the file. The footer line shall contain the same name.
A particle file shall have three other header lines. The second one identifies the simulation model (e.g., the name of author, the name of model). The third lines contain date and time for indentification of the run. These two lines must be identical in the two particle files produced at the same time. The fourth header line be different in the two files and contain the letter 'A' or 'B'.
Each data line shall end with "hidden" variables of the particle, which shall be encoded with visible ASCII characters and spaces.
A settings file shall have one additional header line that contain the letter 'A' or 'B'. Each data line shall end with a setting value in degrees (as an integer or real number).
The resul file shall have second, third, and fourth header lines that are exact copies of the second, third, and fourth header lines of the particle file. The fifth header line shall be an exact copy of the second header line of the settings file. Each data line shall end with result of the detection as a '+' or '-' character except if the particle is not detected at all, which shall be encoded with a '?' character.
These recommendations can be followed if the simulation model satisfies locality, factual definiteness and counterfactual definiteness. Other simulations should follow as many of these recommendations as the model allows.