Los Angeles Airport Earthquake Prediction
Los Angeles Airport Earthquake Prediction
First, I want to congratulate and thank Dr. Courtney Brown for organizing this major remote viewing project. With the number of sessions produced by viewers in various schools of RV there will be plenty of data to examine, and I’m sure we’ll learn a lot from it.
I posted earlier about this and you can read more of my praise for Dr. Brown at this link:
(Remote Viewers Get Their Act Together)
www.hrvg.org/discussion/showthread.php?t=338
And you can see the project information at the Farsight website:
www.farsight.org/
Right now I want to talk about analysis. Glenn Wheaton has taught us so much more than just the process of sitting down with a target ID to work a target. He trained us how to organize into groups to manage the process, and he trained us in analysis. When Glenn first gave me instruction on the art and science of analyzing RV data I think it was at least an 8 hour course, maybe longer, on the basics of how to create a data extraction matrix, working notes, how to craft scenarios based only the low level reduction of corroborated consensus data. The first time I attempted analysis on an HRVG project I worked probably 4 or 5 hours. I turned in my work and Glenn said, “No, you didn’t do that right. Go back and start over.” He gave me a refresher on how to distill similar data and describe it in a manner that will pluck gold nuggets from a bucket of mud.
Analysis is important because every session produced by a remote viewer is a combination of good data, bad data, and contamination. (This is certainly true of the sessions Courtney Brown is using for the earthquake prediction.) You simply cannot take the raw product produced by remote viewers at face value. So how can you determine which data are correct? What can you safely and honestly say about the target based on the work of multiple viewers? You must put the data through analysis.
The analyst must be blind to the target. That means the analyst can’t work the target and the analyst can’t know what the target is. In the earthquake prediction Courtney didn’t follow this hard and fast rule. Analysis is not interpretation. In our system the analyst extracts consensus data (data corroborated by multiple viewers) and uses reduction to take that data down to its most basic, low-level description.
At the IRVA conference in 2004 I gave a presentation on analysis in which I showed how the process unfolds, using an actual project done at HRVG for a client. The viewers were blind to the target and the analyst was blind to the target. In my presentation we showed all of the work produced by 3 different viewers. No single viewer did an excellent session. Each session contained significant bad data and contamination. Yet everything that came through the filter of analysis was true and correct to the target.
In the work for our client one viewer drew and described a man being shot with a gun and killed. The scenario was murder. Another viewer drew and described a man on the ground, in pain and injured. A third viewer depicted a human form lying horizontally. Based on these three sessions could the analyst report that a person had been shot and killed at the target? Could the analyst call this murder? Absolutely not. The consensus data did not support this incorrect data produced by a single viewer. The analyst does not embellish the data; the analyst takes the most basic, low-level view of the corroborated data and reports that with the least amount of embellishment. So in the final report on this project the analyst was only able to report that there was a man in a prone position lying on the ground at the target, and that the man MAY have been injured. That is all the analyst could extract from the 3 different versions.
It turned out that those statements were exactly correct. The target was a man who had been found unconscious and injured lying on the ground. The statements extracted and reduced from the RV data were true to the target. The analyst was not permitted (by our analytic protocol) to look at the first session and conclude, “a man has been shot and killed” and then go look for data in other sessions that supported that conclusion. The analyst can’t assume anything.
In the Earthquake Prediction I believe Courtney looked at one session that he believed indicated an earthquake, assumed this was true and correct data, made a conclusion about the target, and then – because he did not find data about a working airport in the follow up work- allowed his bias and assumption to reinforce his conclusion. Whatever he did, I don’t believe it constituted valid analysis.
The analyst must be blind to the target. If the analyst knows the target –or worse yet is looking for a specific scenario- then the analyst’s own bias affects his perception of the raw data.
What can we say about the work produced on the LA airport target? I would not be permitted to conduct analysis on the sessions because I viewed the targets. My data is in the mix. I’m biased. I also know the target, so that precludes me from doing any analysis. But as a trained analyst I can look at the sessions and say this, and I’m going to state it emphatically:
There is no way any analyst under blind protocol could take the data produced on this target, and conduct proper low level consensus analysis using reduction, and conclude that the Los Angeles Airport will be destroyed by an earthquake. No possible way. I do not believe data in the sessions indicates the Los Angeles Airport is going to be destroyed by an earthquake, and I don’t believe such an event is going to take place.
It would be instructive to have a certified analyst take the data and run proper analysis and see what can be said about that target. Keep in mind reduction. Remember the viewers in my IRVA presentation that reported a man killed by gunfire, a man injured, and a man lying on the ground. All the analyst was allowed to say is a man is lying on the ground. It wasn’t much, but it was correct and accurate.
Look at the earthquake sessions for yourself. If you didn’t know what the target cue was, if you had never seen Courtney’s prediction, if all you had was the raw session work, could ever conclude that the work describes Los Angeles Airport destroyed by earthquake? Put through proper analysis the sessions may describe something else entirely. The data could just as easily describe a landslide.
I believe Courtney made several mistakes in this prediction. He selected the target pool, and also worked the targets. Even though the targets were randomized, I don’t feel anyone with any knowledge of the targets should be allowed to work them. This can be debated, and probably does not have any bearing on the failure of, or lack of analysis, which is the greater issue here. The bigger mistake, in my opinion, is that Courtney drew a conclusion from the work of one viewer, and then looked for data to support that conclusion. Rather than using reduction Courtney embellished the data, took the data to the farthest extreme. An analyst is not allowed to do that. This has been the downfall of many remote viewing efforts through the years. I won’t mention them by name, but there have been some spectacular failures.
We will learn a lot from this project. And I think one of the lessons will be the crucial need for competent analysis. On the other hand, if there is a big earthquake in Los Angeles in the near future, hey- I’ll tip my hat to Courtney and to Daz. I wouldn’t cancel my flight to Los Angeles based on what I see in these few sessions.
Aloha,
Dick