Experimental Procedures
1.) Hardware Set Up:
a. Obtain the following:
Sample of Uranium Ore Purchase Link, Geiger Counter Amazon Purchase Link, Arduino Board Amazon Purchase Link,
Wires Amazon Purchase Link
b. Set up the apparatus.
Connect the GND on Arduino to the GND on the Geiger counter. Connect the 5V on Arduino to the 5V on the Geiger counter. Connect the VIN on the Geiger counter to the D2 on Arduino. Attached this circuitry to a base board so that it can be safely moved as a single unit. When you are ready to run a trial, connect the Arduino board to the laptop. Place the Geiger counter, Arduino board, and lap top into a sound insulated container such as a suitcase or a plastic storage bin lined with blankets. Put the uranium ore next to, or on top of, the Geiger counter.
2.) Program the Geiger Counter Interface.
The Geiger counter interface program is Arduino. It is available for free download here: https://www.arduino.cc/en/software
The code below is what transforms the series of Geiger counter clicks into a series of one-digit numbers that will be later used in the priming software code (Inquisit 6). Simply cut from below and paste it into the Arduino software as a new file. This will produce a series of one-digit digital values from the Geiger counter in the serial monitor. Once you hit upload, open the serial monitor and expand the screen. The numbers will fill in on the left side.
// This Sketch counts the number of pulses a minute.
// Connect the GND on Arduino to the GND on the Geiger counter.
// Connect the 5V on Arduino to the 5V on the Geiger counter.
// Connect the VIN on the Geiger counter to the D2 on Arduino.
unsigned long counts; //variable for GM Tube events
unsigned long previousMillis; //variable for measuring time
void impulse() { // dipanggil setiap ada sinyal FALLING di pin 2
counts++;
}
#define LOG_PERIOD 4000 // count rate
void setup() { //setup
counts = 0;
Serial.begin(9600);
pinMode(2, INPUT);
attachInterrupt(digitalPinToInterrupt(2), impulse, FALLING); //define external interrupts
Serial.println(",start");
}
void loop() { //main cycle
unsigned long currentMillis = millis();
if (currentMillis - previousMillis > LOG_PERIOD) {
previousMillis = currentMillis;
Serial.println(counts);
counts = 0;
}
}
3.) Program the Response Time Software
The response time software is Inquisit 6. It is available for download here: https://www.millisecond.com/download
The programing code used in the first replication (key stroke response modality) can be obtained here. This is the code that is recommended for use in future replications because it uses the keystroke, rather than the verbal, response modality.
The code used in the original study (verbal response modality) can found directly below. Simply cut from below and paste it into a new file in the Inquisit software.
<defaults>
/fontstyle = ("Ariel", 65pt)
/screencolor = black
/txcolor = white
/txbgcolor = black
</defaults>
<item stimulusnumber>
/1 = " 4 "
/2 = " 5 "
/3 = " 6 "
/4 = " 7 "
/5 = " 8 "
/6 = " 9 "
/7 = " 3 "
/8 = " 2 "
/9 = " 1 "
</item>
<item prime0>
/1=" 5 "
/8=" 7 "
/5=" 4 "
/2=" 2 "
/9=" 6 "
/4=" 9 "
/7=" 3 "
/6=" 8 "
/3=" 1 "
/10=" 4 "
</item>
<item prime1>
/1=" 5 "
/2=" 6 "
/3=" 4 "
/4=" 2 "
/5=" 7 "
/6=" 8 "
/7=" 3 "
/8=" 9 "
/9=" 1 "
/10=" 4 "
</item>
<item prime2>
/2=" 5 "
/1=" 6 "
/3=" 4 "
/5=" 2 "
/4=" 7 "
/8=" 8 "
/9=" 3 "
/7=" 9 "
/6=" 1 "
/10=" 4 "
</item>
<item prime3>
/2=" 5 "
/1=" 7 "
/3=" 4 "
/5=" 2 "
/4=" 6 "
/8=" 9 "
/9=" 3 "
/7=" 8 "
/6=" 1 "
/10=" 4 "
</item>
<item prime4>
/1=" 5 "
/9=" 7 "
/2=" 4 "
/5=" 2 "
/4=" 6 "
/8=" 9 "
/3=" 3 "
/7=" 8 "
/6=" 1 "
/10=" 4 "
</item>
<item prime5>
/1=" 1 "
/9=" 7 "
/3=" 4 "
/5=" 2 "
/4=" 6 "
/8=" 9 "
/6=" 3 "
/7=" 8 "
/2=" 5 "
/10=" 1 "
</item>
<item prime6>
/1=" 1 "
/3=" 7 "
/9=" 4 "
/5=" 2 "
/4=" 6 "
/6=" 9 "
/8=" 3 "
/2=" 8 "
/7=" 5 "
/10=" 3 "
</item>
<item prime7>
/1=" 1 "
/3=" 7 "
/9=" 4 "
/5=" 2 "
/4=" 6 "
/6=" 9 "
/8=" 3 "
/2=" 8 "
/7=" 5 "
/10=" 9 "
</item>
<item prime8>
/1=" 1 "
/3=" 7 "
/9=" 4 "
/5=" 9 "
/4=" 2 "
/6=" 6 "
/8=" 3 "
/2=" 8 "
/7=" 5 "
/10=" 3 "
</item>
<item prime9>
/1=" 5 "
/9=" 7 "
/5=" 4 "
/2=" 2 "
/8=" 6 "
/4=" 9 "
/7=" 3 "
/3=" 8 "
/6=" 1 "
/10=" 4 "
</item>
<item prime10>
/1=" 5 "
/8=" 7 "
/5=" 4 "
/2=" 3 "
/9=" 6 "
/4=" 9 "
/7=" 2 "
/6=" 8 "
/3=" 4 "
/10=" 1 "
</item>
*********************************************************************************************
STEP #1
Paste the Geiger Counter Data below for the unobserved condition. The sequence for the unobserved condition goes first and below that is where you would need to insert the sequence for the observed condition in Step #2.
For the unobserved condition:
Scroll down 30 or more lines below and then paste in the Geiger counter data with the screen covered as you do so. Then, with the screen still covered, scroll back up to the top of the code. Remove the cover and then slowly and carefully scroll back down to this point again. Cover the screen. With your curser on the left margin you should be able to blindly scroll down to where you just placed your, yet unseen, Geiger counter data. By clicking the mouse and holding the button while moving it slightly to the right you should be able to select one numeral from your Geiger counter data. You will know that you have this by looking at the column number at the bottom right of your screen, which you should still be able to see while keeping the other 4/5th of the screen covered. Then use control x to cut. You will know it worked because the column number will go back to "0". Then scroll up to the top. You can remove the cover and carefully scroll down to this section again. Then place your cursor between the word "prime" and the "/" in the code below. Cover the screen up again. Hit paste. Then again scroll all the way to the bottom of the code. When at the bottom you can remove the cover. Scroll very slowly up until you get to Step #2.
*************************************************
<text unobservedprime>/items = prime/select = sequence (
)
</text>
****************************************************************************************************************************
this large number of empty lines was put in to help prevent any accidental scrolling up to the unobserved primes during the placement of the observed primes.
****************************************************************************************************************************
<text observedprime>/items = prime/select = sequence (
)</text>
****************************************************************************************************************************
STEP # 2.
Obtain a new group of Geiger counter data for the observed condition and paste it immediately above the ")</text>". Then, briefly look at all of the numbers. After that randomly select one of the digits for the correspondence and insert it between the word "prime" and the "/" in the code just as you did in the unobserved condition. Be careful the whole time not to accidentally scroll too high or you will come into contact with the sequence for the unobserved condition, which needs to remain unobserved. Once this is done, scroll again to the bottom and hit run. Then the lap top will be ready to be brought to the participant. You must also ensure that your item blocks are being rotated every administration. Directions on how to do this can be found in the next instructions section labeled Step # 3 below.
***************************************************************************************************************************
<text mask>
/items = (" #@GX& ")
/fontstyle = ("impact", 65pt)
/txcolor = white
/txbgcolor = black
/position = (50%, 50%)
</text>
<text mask2>
/items = (" @X&#G ")
/fontstyle = ("impact", 70pt)
/txcolor = white
/txbgcolor = black
/position = (50%, 50%)
</text>
<text target>
/items = Stimulusnumber
/select = random
/txcolor = white
/txbgcolor = black
/position = (50%, 50%)
</text>
<trial Observed>
/ pretrialpause = 500
/ inputdevice = voicerecord
/ stimulusframes = [1=mask; 11=observedprime; 14=mask2; 16=target]
/ response = timeout(1200)
/ posttrialpause = 1000
</trial>
<trial Unobserved >
/ pretrialpause = 500
/ inputdevice = voicerecord
/ stimulusframes = [1=mask; 11=unobservedprime; 14=mask2; 16=target]
/ response = timeout(1200)
/ posttrialpause = 1000
</trial>
*************************************************
STEP # 3
Creating Blocks. This is the creation of the number of items and the order that they go in.
As it is set up now the first 40 items will be in the unobserved condition and the following
40 will be in observed condition. These need to be rotated in between administrations to
ensure that the observed and the unobserved conditions have an equal number of administrations
going first and second. This is done to prevent any order effects that may emerge. You can
simply switch them around by cutting and pasting.
*************************************************
<block Unobserved>
/trials = [1-40 = sequence(unobserved);
]
</block>
<block Observed>
/trials = [1-40 = sequence(observed);
]
</block>
4.) Running of Trials
a. Obtaining usable values from the Geiger counter.
The Arduino code as it is currently written transforms the number of Geiger counter clicks occurring within every four second interval into digital values. This may need to be adjusted. Double- or triple-digit numbers will not work in the code and long strings of zeros will not give you enough variability in the superposition. Ideally you want to have a frequency range from 0-10. To get this consistently you may need to “tune” the apparatus. This can be done by either adjusting the interval length in the Arduino code or by adjusting the distance between your uranium ore and the Geiger counter.
b. Protect against inadvertent collapse
The unobserved primes are, for lack of a better term, “delicate”. Any link to consciousness, even if it is at the end of a chain of events, has the potential to cause an unwanted collapse. Researchers should be able to avoid these with reasonable diligence, as it was able to be avoided in the original study. However, odds are that some items in the unobserved condition may have suffered an inadvertent collapse (but there is no way to know for certain). If the number of items in which this occurs is small compared to the total, then it should not significantly affect the outcome over a small to medium number of trials. However, depending on the relative frequency of inadvertent collapses it could possibly be expected for the results in the unobserved condition to trend significant as the number of trials in the unobserved condition increases.
In the original study the Geiger counter data was captured and pasted in the code one trial at a time. Once we pasted in the observed and the unobserved primes over two consecutive gathering windows, we immediately presented the laptop to the participants and started the response time task. Each trial was prepared and completed one at a time. This was done to safeguard against inadvertent collapse. It may have been necessary to do it this way, or maybe it was not necessary. The most efficient way may be to gather all of the Geiger counter data at once and then prepare separate program files in Inquisit for trial #1, trial #2 etc.
c. Script
This is the script that was read to each of the participants at the start,
“you are going to see a series of numbers flashed on this screen one at a time. For each number say out loud “odd” or “even” depending on the number you see. Go as fast as you can without making mistakes. Click the mouse when you are ready to start.”
After the first trial ask,
“did you see any other numbers on the screen very briefly before the one that you responded to?”
The purpose of asking this question is that at 50.1 milliseconds most people cannot see the primes, although it is not uncommon for some individuals to be able to see them. If one of the participants you are using happens to be a person who can discern the primes at 50.1 milliseconds then you would not actually be able to have an unobserved condition with that participant and they should therefore be removed.