text:
Time travel2
[ UFOs ] [ Chemtrails ] [ Why hemp is suppressed ] [ Ether ] [ Radionics ] [ Time Travel ] [ Hollow earth ] [ Breatharianism ] [ Coverups uncovered ] [ Crop circles ] [ Mars & Moon ]
[ Time travel ] [ Time travel2 ]
Notes on the Philadelphia Experiment
The Philadelphia Experiment, otherwise known as Project Rainbow, has been a subject of long controversy and debate. It was an attempt by the Navy to create a ship that could not be detected by magnetic mines and/or radar. There was also talk of invisibility projects and mind control experiments. The truth behind this project will never be known to the public. It is just one those triggers that we encounter that propels into awareness as who we are on a soul level.
However, results of these experiments became far different and much more dangerous than the Navy ever expected. Although the story itself seems too bizarre to be true, far too many coincidences have occurred for it to not be based upon some small iota of truth. The technical data that has also been presented upon the subject hold far too much credence to be ignored. Many of the stories associated with this infamous experiment are wild: whispers of men 'freezing' in time for months, rumors of men traveling through time, and horror stories of men becoming stuck in bulkheads or even the floor of the ship itself. (In the movie of the same name - the visual of the men being part above the deck - and part buried in the deck - is amazing. This sort of things has been done on 'X-Files' as well when they did a storyline about temporal anomalies.
In the 1930's Nikola Tesla got involved with a group which was experimenting with moving through the Time / Space continuum. In the early 1930's, the University of Chicago investigated the possibility of invisibility through the use of electricity.
In 1939 this project was moved to Princeton's Institute of Advanced Studies - this is not far from Philadelphia. There they were able to make small objects invisible. They presented this technology to the government. The military, because we were at war, wanted to pursue it in their direction. Tesla had come to the same conclusion that Einstein did that this technology if developed, would not be used for the benefit of mankind.
In 1943 the government conducted a test using domestic animals on a ship. The ship that was eventually used for the experiment, the USS Eldridge, was commissioned at the New York Navy Yard on August 27,1943 (Department of the Navy). The animals were placed in metal cages on the USS Eldridge. The ship became invisible but when it materialized many of the animals were missing on had radiation and other burn marks on them. Humans were not to be tested.
Yet on August 12, 1943 the USS Eldridge with a full crew aboard reportedly underwent the Philadelphia Experiment. The men did not know what was to happen. The generators were fired up. The switches were thrown. The ship disappeared and all seemed well.
However, others claim that the experiment took place on October 28, 1943. Substantial evidence points to the October date as being more accurate. The Navy has released the Eldridge's deck log and war diary and at no time was the Eldridge in Philadelphia. However, the records could have easily been changed.
The Eldridge's war diary reads as such: The Eldridge remained in New York and the Long Island Sound until September 16, when it left for Bermuda. From September 18 to October 15, it underwent training and sea trials. On October 18, it left in a convoy for New York and remained there until November 1. From November 1 to the 2, it went on a convoy to Norfolk and on November 3 left in a convoy for Casablanca. The Eldridge arrived in Casablanca on November 22 and stayed there until November 29, when it left for New York again in another convoy. The Eldridge arrived in New York on December 17.
From December 17 to December 31, it traveled to Norfolk with four other ships (Department of the Navy). Although this is not the entire war log, it is the log of the ship during the suspected time the experiment took place (October 28, as mentioned above).
It would seem that the Navy never did experiments on the Eldridge at any time, but the government has been known to cover up because of national security before. An example of such a situation would be the Manhattan project. This secret project was the building of the atomic bomb and no word was ever said about it until it was obvious that we had an atomic bomb.
The Navy, in a search for a plausible answer, has suggested that perhaps the Philadelphia Experiment was confused with experiments done attempting invisibility to magnetic mines. This was a process known as degaussing.
But the ship was gone from the harbor for about 4 hours, not just a few minutes. Legend has it that the ship was transported through space and time. It arced through Space / Time.
Four hours later it returned to its original place. There was a greenish haze on deck. Some of the sailors were on fire. Some seemed insane. All were sick. Some had heart attacks. Some were dead. Some were part of the super structure of the ship, buried in the deck or walls of the ship. Some reports said that men just seemed to disappear and were never seen again.
But where had the ship gone for 4 hours? Some witnesses placed it in Norfolk Harbor. Others say it voyaged 40 years into the future and wound up at Montauk, New York.
The Navy denied everything and said the men were lost at sea. Perhaps one day the truth will be known.
The Montauk Experiment purported links several of these sailors to Montauk, New York with a time loop to 1983.
The Navy performed another experiment on the USS Timmerman's generating plant in the 1950's. The experiment tried to obtain 1,000 Hz instead of the standard 400 Hz from the generator (Department of the Navy). It resulted in light discharges. These light discharges may have been witnessed by Carlos Miguel Allende and caused him to start writing letters to prominent men in the scientific community. The Navy believes that Allende mistook the experiment on the Timmerman for the Philadelphia Experiment.
Carlos Miguel Allende, also known as Carl Allen, was an odd man. He was born on May 31, 1925 in a small town outside of Pennsylvania. On July 14, 1942, Allende joined the Marine Corps and was discharged on May 21, 1943 (Taken from the book titled The Philadelphia Experiment, pg 99). He then joined the Merchant Marine and was assigned to the SS Andrew Furuseth. It was upon this ship that he claimed to see the Eldridge in action.
Allende's story was bizarre; he stated that he had witnessed the Eldridge being transported instantaneously to Norfolk from Philadelphia and back again in a matter of minutes. Upon researching the matter further, he learned of extremely odd occurrences associated with the project and wrote a basic summation of his newly learned knowledge in a letter to Dr. Morris K. Jessup. Dr. Jessup was an astronomer and Allende had been in the audience of one of Dr. Jessup's lectures. Apparently having some respect for the man, he decided to entrust Dr. Jessup with his knowledge. The letters were written oddly: with capitalization, punctuation, and underlines located in various places.
The letters were also written in several colors. In his letters, Allende revealed horrifying details of the Philadelphia Experiment to Dr. Jessup. Because Dr. Jessup was something of a believer in odd phenomenon he did not entirely dismiss the ideas presented to him. He wrote back to Allende and requested new information. The return address upon the letter never existed according to the mail service, yet Allende still received Dr. Jessup's reply. Allende responded with more detailed letters but the correspondence eventually discontinued because Dr. Jessup dismissed it as a hoax.
During the time of Dr. Jessup's and Allende's correspondence, Dr. Jessup had just recently published his book titled The Case for UFO's. After Allende had written to Dr. Jessup, this book was sent to the Navy and had hand-written notes inside the book. The notes were in the same writing as in the letters sent to Dr. Jessup and eventually Dr. Jessup was asked by the Navy to view the notes.
Dr. Jessup recognized the writing immediately, but he was somewhat astonished, as he had concluded earlier that it was merely a hoax to trick him. The notes in the book were more detailed than in the letters and were highly insightful, so Dr. Jessup eventually believed them and researched the matter. Unfortunately, Dr. Jessup could not find any new leads. Only one tantalizing clue had shown up.
Two crewmen had been walking in a park when a haggard looking man approached them. The man told them a fantastic story about an experiment done in which most of the crew died or suffered terrible side effects. He said that the government then claimed the entire crew was insane so that when they came forward, they would merely be dismissed as a group of crazy people who had merely concocted some fantastic story. After the conversation, one crew member was convinced while the other was not. Eventually, the member that had been convinced contacted Dr. Jessup and told him the story. Although this was a substantial lead, Dr. Jessup was not getting very far and he found that his reputation in the scientific community was worsening. Faced with overwhelming odds, Dr. Jessup eventually committed suicide on April 20, 1959, believing "another existence of universe being better than this miserable world." (The Philadelphia Experiment, 79). Some believe that his suicide was actually an assassination by government agencies to keep the experiment quiet.
Unfortunately for Dr. Jessup, a major clue in the puzzle turned up shortly after his death. This clue was a man by the name of Alfred D. Bielek.
Bielek's story is even more bizarre than Allende's. He claims that he was transported in time to the future and that here in the future he was brainwashed by the Navy. This brainwashing led him to believe that his name was Alfred Bielek, rather than his true name, Edward Cameron. Upon discovering his true identity, he tracked down his brother who had also participated in the experiment. Bielek claims that his brother time traveled to 1983 and lost his 'time-lock'. As a result, his brother aged one year every hour and eventually died. Bielek then claims that his brother was reborn. Needless to say, only a small group of people believe Bielek and nearly everyone thinks that his stories are based on some truth, but he's exaggerating the truth for personal reasons. This popular opinion seems to be reinforced when Bielek starts remembering things only after having seen the movie "The Philadelphia Experiment". Bielek has a Ph.D. in Physics, so he does have some technical experience. He is also a retired electrical engineer with thirty years of experience. Because of his obvious intelligence and skill, he cannot be discounted entirely. Bielek stated that the technology used in the Philadelphia Experiment was given to us by aliens. However, the germanium transistor, which was what Bielek said had been used, was invented by Thomas Henry Moray.
Bielek also stated that Dr. Albert Einstein, Dr. John von Neumann, and Dr. Nikola Tesla were involved in the project. Some controversy has arisen as to the participation of Tesla because he died in New York
city on January 7, 1943, which was only a two month period of time after the project took place. Einstein, on the other hand, suggested such a project as this to the Navy on several occasions. Because of this, he was probably involved in the project. As for von Neumann, there is no evidence to refute or promote his active participation in the matter. There is evidence that supports the fact that he later continued on the experiment at a different time.
The principle that lay behind the Philadelphia Experiment was the Unified Field Theory. This theory states that gravity and magnetism are connected, just as mass and energy are connected through the formula E=mc2. Einstein never solved the Unified Field Theory, but the very nature of the Philadelphia Experiment suggests otherwise. It is probably that this theory has become a government secret because it is capable of doing many things, possibly even space travel without the assistance of rockets.
In a search for actual technical data on the experiment, not much information can be found that isn't tainted with doubt and speculation. The basic design has two large Tesla coils (electromagnets) placed on each hull of the ship. The coils are turned on in a special sequence and their magnetic force is so powerful that they warp gravity itself. Bielek also says that on August 12 every twenty years, the magnetic field of the Earth reaches a peak and allows the synchronization between the Tesla coils. The oscillator which Bielek claims to have run the coils in a special pattern looks more like an Army field kitchen refrigeration unit than anything else. Many believe that's exactly what it is and Bielek's story is just a hoax. Bielek gave it a technical name however: the "Zero Time Reference Generator". The oscillators would synchronize with the adjustable phase angle and created a scalar type wave (Anderson). Several scientists today have attacked Bielek's testimony on this, as they believe a vector wave would have been more efficient and probable. Bielek also does not make clear if the power used is AC or DC, pulsed or rotating, and what the Microwave and Radar frequencies are. In other words, Bielek provides almost no accurate technical information that can be used.
Rick Anderson however, may be able to shed some light upon the subject. He states that four RF transmitters were phased to produce a rotating field. This field was pulsed at a 10% duty cycle. Instead of two coils, he says that four coils would have been set upon the deck of the ship and would be run by two generators that were pulsed in a counter-clockwise motion. Anderson states that the Tesla coils use a total of 7,500 feet, or 1.42 miles of #16 magnet wire. Because of this enormous quantity, no one has privately undertaken the experiment; the wire would be too expensive and also must to be wound in a special way (Anderson). Other scientists believe that Nuclear Magnetic Resonance and the science of the Philadelphia Experiment are connected.
Nuclear Magnetic Resonance is also known as Magnetic Resonance Imaging, or MRI. Yet another scientist named Alexander S. Fraser believes that everyone is wrong about the electromagnetic qualities of the experiment. He believes that it was never done with electromagnetism, but with thermal fields. This thermal field could have caused the optical mirage effect which several witnesses reported. Fraser says that Allende had spoken of a 'scorch' field, fire, and optical wavering, all of which are products of a thermal field. As for the part about the Eldridge disappearing in front of their very eyes, certain weather conditions have been known in the ocean to cause islands to disappear as well. These weather conditions were taking place the day of the experiment. Yet another scientist believes that sonic and ultrasonic waves were used.
The sonic waves could have been used to create an 'air blanket' around the ship, which is consistent with reports. There were many experiments done in the 1940's with high power ultrasonic waves, which indicates a high probability of the Philadelphia Experiment being one of them. Strong sonic fields are known for having bad side effects upon humans, which is also consistent with reports. The green haze which was presumably around the ship was caused by "exciting the surrounding sea water with powerful ultrasonics - 'sonoluminescense' and related phenomena." (Anderson) The ultrasonic field would have caused the crew to pass out and make the journey from Philadelphia to Norfolk seem to last only a couple minutes. Needless to say, the technicalities of the Philadelphia Experiment are a matter of hot debate among scientists and no one seems to be able to provide any solid evidence. As Rick Anderson aptly puts it: "An electronics person knows that, without a DETAILED, comprehensive THEORY behind bench set-up, he is not going to know how to set up voltages and currents, power levels, frequencies, wave forms, pulse widths or duty cycles. If there's a chance a circuit won't work, Murphy's Law dictates that it WON'T more often than not."
If the technicalities of the experiment are vague and a matter of controversy, the results of the experiment are just as foggy. One fact which everyone seem to agree on is that a field was extended many yards, up to perhaps one hundred, outside of the ship and into the water (Anonymous). Everything inside of this sphere was vague in form and the only visible shape was the hull of the Eldridge in the water. This field seemed to have a greenish color and was misty. Another fact everyone agrees was that the Eldridge did not function properly after the experiment and became a source of trouble.
The last item everyone believes is that terrible side effects were manifested upon the crew members. However, when one delves deeper into that particular subject, no one agrees on what the specific details are. Some witnesses, Allende and Bielek in particular, state that matter itself was changed and that men were able to walk through physical objects. When the field was shut off, some crew members were
found stuck in bulkheads, others in the floor. Some were found with the railings of the ship stuck through their bodies. It was a horrendous sight. The sailors supposedly went crazy after this and raided a bar.
They told the bar maid their story and completely terrified her. According to Allende, a newspaper article was written upon the raid, but no specific date was named, so the article cannot be found. Most crew members went insane, but a few retained their sanity, only to be thrust into worse situations. One man sat down to dinner with his wife and child, but then got up from the table, walked through the wall, and was never seen again. Two others simply disappeared into thin air and were also never seen again. Another crew member vanished in the middle of a fight, much to his opponent's astonishment. All three incidents had several witnesses.
Yet the worse side effects were when men got 'stuck'. Getting stuck consisted of becoming invisible and being unable to move, speak, or interact with other people for a period of time. This was told of by Allende in his letters to Dr. Jessup. Getting stuck by the crew members was known as "Hell Incorporated". (The Philadelphia Experiment, 42). It was also known as the Freeze. A common freeze would last minutes to hours and was damaging psychologically, but did not cause madness. A man would only come out of the Freeze if other crew members laid their hands upon him to give him strength. Unfortunately, in one instance of the "Laying of Hands," two men who attempted to lay hands upon the man burst into flames and burned for eighteen days (The Philadelphia Experiment, 44). The fires could not be stopped, despite multiple attempts to quench the flames. Needless to say, the Laying of Hands was discontinued from that point on. Then, men started going into the Deep Freeze, when a man would be frozen for several days to several months.
During this time, the man is completely aware of others and their actions but was unable to communicate to them or interact with them. Men in the Deep Freeze can only be seen by other crew members. It only
takes two days for a man to go completely crazy in the Deep Freeze. The first deep freeze took six months and five million dollars worth of research and equipment to correct (The Philadelphia Experiment, 43).
The man who was stuck for six went completely insane by the time he got out. Carlos Allende wrote: "Usually a A Deep Freeze Man goes Mad, Stark raving, Gibbering, Running MAD, if His freeze is far More than a Day in our time." (The Philadelphia Experiment, 42) Rick Anderson uncovered research that states this disappearance or freezing of people is the Zeeman Effect. "Zeemanising - the Zeeman Effect is defined as spreading out of the spectral lines of atoms under the influence of a strong magnetic field." (Anderson) The few remaining sailors have a high PSI factor which is intensified by fear or hypnosis. Unfortunately, they have all been discharged from the Navy as mentally unfit.
The Philadelphia Experiment has become a saga of strange occurrences and peculiar coincidences. It should be noted that Allende firmly believes the Navy was completely unaware of the side effects the Philadelphia Experiment would produce on the crew members. Allende is also quoted as saying: "I believe that further experiments would naturally have produced controlled transport of great tonnages at ultra-fast speeds to a desired point the instant it is desired. "(Allende). A full report of the Experiment was given to Congress and the members were so horrified that they disbanded the project immediately. However, research continued at the Montauk Project, a.k.a. the Phoenix Project, which was headed by Dr. John von Neumann, who also directed the Philadelphia Experiment. The Montauk Project centered mostly on how the mind reacts to inter-dimensional travel. It took place at the Brookhaven National Laboratories. Von Neumann attempted to link computers with minds and was apparently successful beyond his wildest dreams. Using this computer-human link, Von Neumann could affect others minds and was eventually able to open a time vortex back to 1943 to the Philadelphia Experiment. He even made claims that the mind could created matter at any point in time. He also claimed to have sent a man named Preston B. Nichols through two times lines, a fact which was actually confirmed by Duncan Cameron in 1985 (Montauk). Cameron was trained by the National Security Agency, so his testimony is valid. Many people believe that the Montauk Project is continuing to this day, although much of the information available about it is only rumor.
This entire scenario is filled with questions that will never be answered as the people involved have their own version on the events.
As for government conspiracy - it has always been part of the game in which we are all players. It is all a game - experience - experiment in which we are the players. We all move through time - time-grid programs as we are all multidimensional based on our conscious awareness in different frequency programs.
My soul is linked - and always seems to come back to - WW II Germany - an escape from an underground lab at which time I stole papers about time travel and related projects - fleeing by ship to Philadelphia and working with others in a lab - papers hidden in a canister in Philadelphia - dying in the lab when it blew up.
My soul is linked to the Philadelphia experiences in some way - that doesn't have to do with the basic players involved. In this lifetime I have met many of the souls with whom I interacted in that timeline and with who I share a 'mission' linked to the future evolution of humanity. My friends and I are not part of conspiracy theories nor game playing. My agenda is different. It is why I am here. It is my personal
mission. Do you feel you have a mission?
THE ELDRIDGE SINCE THE EXPERIMENT
Some people report that the ship was dismantled. Others report that it was taken to Greece and renamed the "Leon".
A man named George N. Pantoulas maintains that the [Eldridge] was given as military aid from US to Greece sometime between the late 40's and early 50's where it served in the Greek navy until 1990 and is sea worthy today. It is purported located in the Suda Bay Naval Station in Crete. George says he has visited the ship. He has seen strange wires that go nowhere. He says that men who serve on the ship feel strange energies and have strange illusions. George has interviewed men who served on the ship.
Mr. Jorge "George" Anthony Paniagua
615-A Jefferson Street
Stayton, Oregon 97383-1929
Montauk Experiment
Interview From "The Metaphysical Experience"
Preston, Ellie, Duncan
The Philadelphia experiment originally began back in the 1930's in Chicago with three people. Dr. John Hutchinson Sr., who was the Dean of the University of Chicago, Nickola Tesla, and Dr. Kurtenaur, who was an Austrian physicist who was on staff at the University.
They decided to do something with the speculation regarding the concept of things and people being invisible. This subject had been discussed for several year. They got together and did some research at the University of Chicago around 1931 or 1932. In 1933 the Institute of Advanced Studies at Princeton was formed and the project was transferred there in 1934. One of the people on staff at the Institute was Dr. John Erich Von Neumann, who was from Budapest Hungary. He got his degree in chemistry in 1925 and his Ph.D. in mathematics in 1926. He taught in Europe for about four years and transferred to the United States. He taught at the graduate level for three years and was invited to join the Institute.
Other people at the Institute included Albert Einstein, who left Germany in 1930. He went to the California Institute of Technology for three years and taught there and then went to the Institute upon their invitation and acceptance. A lot of other people showed up there as time went on. The project expanded about 1936. In the meantime, Tesla was named director of the project. He was a friend of president Franklin Roosevelt, whom Tesla met in 1917 when FDR was secretary of the Navy.
Tesla was asked at that time to do some work for the government for the war effort, which he did. He accepted and became director of the invisibility project until he resigned in 1942. In 1936, after intensive study, they decided to have an initial test of their work. They achieved some partial invisibility. The Navy and everyone else was encouraged to continue the work, and the Navy supplied money for research.
Scientists were coming to the United States from Germany until 1939, when the war with Germany was started.
In 1940, after research using Tesla's approach, they decided they were ready for a full test at the Brooklyn Navy Yard. They had a small ship and a tender ship at each side. One ship provided the power and the other supplied the drive for the coils. They were tendered to the test ship by cables. The idea was that if anything went wrong they could cut the cables or sink the test ship. Everything worked and the project was declared a success.
The important point about the 1940 test is that there was no one on board the test vehicle. It was strictly a dry run with no people. This is important because of what happened later. Other people came on board. Thomas T. Brown joined the project because of his expertise in electrogravity effects. He had the task of solving the problem of the German magnetic mines that were affecting allied shipping and Naval efforts. This led into a parallel project which involved the use of deguising coils and cables to explode the mines at a distance from the ship.
The Navy wanted several people to keep an eye on the tests. That is how I got involved. Keeping technical commentaries. Let's look at Nickola Tesla.
In 1879 his father died and his first year at college ended. He came to the United States in1884. He had enormously intuitive insight. He had a perfect track record. Before coming to the US he had known Robert Oppenheimer, who later worked with the development of the atomic bomb, and Dr. David Hilbert, the mathematician who devised equations for Hilbert Space, which described multiple space or multiple realities mathematically.
These equations for multiple space became very important in the project. Dr. von Neumann met Hilbert in 1927 and retained a lot of what he had learned. With that, Von Neumann developed other new systems of mathematics. Von Neumann was considered to be one of the most outstanding mathematicians in this century. Some think he was better than Einstein. Another mathematician involved was Dr. John Levinson, who was born in 1912. He died in 1976. He published three books on mathematics. Levinson developed the so-called Levinson Time Equations. with all this behind them, the group had all they needed to proceed with the project.
After the successful 1940 test, the Navy decided to give the project unlimited funds and to classify the project. In 1942 Tesla was given a ship and a crew for a full sized test. Tesla got a battleship. Tesla and Von Neumann didn't agree on some things. Tesla insisted that they were going to have a very severe problem with personnel. Tesla wanted more time but the NAVY wouldn't agree. Tesla made periodic announcements in the late 1930's and early 1940's about his contact with off planet species. He was in contact with the outside, who agreed that there was a problem with the people. He decided to sabotage the 1942 test in an attempt to stop the project. He de-tuned the equipment so nothing would work. The test failed. Tesla then turned the project over to Von Neumann in March 1942 and left the project.
Von Neumann went to the Navy and requested time to study the problem to determine what had gone wrong. Von Neumann decided to make changes in some of the equipment. He decided he would need a special ship that was designed from the ground up. The Eldridge was selected. The equipment was built into the ship. They put all the equipment on the ship. October 1942 arrived. They selected 33 volunteers for the crew, who arrived after graduation in December 1942. We still have a picture of
the class.
After the ship was out of drydock work began. In May of 1943 von Neumann installed a third generator. It would never synchronize with the other two. It went out of control one day and zapped one of the men. Von Neumann pulled out the third generator (installed because Tesla had convinced Von Neumann of the potential problem with people) and went back to the original design. In mid June, the ship had sea trials. On July 22, 1943, they had the test. The ship between radar and optically invisible. They discovered people very disoriented. The Navy pulled the crew off and consulted Von Neumann, who requested more time again from the Navy. The Navy, after consultation with higher-ups, announced that the drop dead date was on the 12th of August, 1943. Von Neumann voiced his concern that it wasn't enough time.
The Navy decided that it just wanted radar invisibility and not optical invisibility. The equipment was again modified by Von Neumann. August 12th arrived. We knew things were not right. The test began, and for about a minute everything was all right. The ships outline could be seen in the water. There was suddenly a blue flash and the ship disappeared entirely. No radio communication was possible. It was gone. In about three hours it came back. One of the masts was broken.
Some personnel were partially embedded in the steel deck. Others were fading in and out. Some disappeared entirely. Many were insane. The Navy extracted the crew and proceeded with four days of meetings to decided what to do about the problem. They decided there would be one more test with another dry run without personnel. They conducted the dry run using about 1000 feet of cable attached to another ship. In late October 1943 the test occurred. The ship disappeared for about 20 minutes. When it returned, they found equipment missing. Two transmitter cabinets and one generator was missing. The cabinet with the zero-time reference generator was intact. At that point, the Navy stripped the ship and stopped the project. The Eldridge served in the war and was turned over to Greece at the end of the war.
The important thing is that there were two tests that were exactly 40 years apart to the day. It was a 40 year separation in hyperspace. Now, the Earth itself has a biorhythm that peaks on a 20 year cycle on August 12th. It "just happened" to peak and provided the connecting link through the fields of the Earth for the two experiments to lock up in hyperspace. Walk-in efforts are aided if they occur during this
peak.
The ship was pulled into hyperspace. We were inside the ship and knew something was drastically wrong with the test. We tried to shut it off but it wouldn't shut off. We ran out on deck and jumped over the side of the ship. We jumped overboard but ended up in a time tunnel which ended at Montauk, Long Island on August 12th, 1983. At night.
We were found very quickly and taken down stairs, where Von Neumann greeted us. He expected us. It was a bit of a shock. We had just been in 1943 and now we were in 1983 looking at Von Neumann as an old man. He said that there was a hyperspace lockup and that we had to go back and shut off the generators on the ship or the hyperspace rift would keep increasing and possibly engulf the planet. He had been waiting 40 years for us to arrive.
Montauk sent us back and we smashed the equipment with axes. The ship returned to its original point in space and about three hours later in time. From 1943 on, Von Neumann didn't know what happened. He had modified earlier equipment in 1943 to where he had a full blown time machine. The Germans also were working on time travel, and had it working in 1945 just before the end of the war. This is all a matter of record.
After the Navy decided to shut down the project in 1943, Von Neumann was sent to work on the atomic bomb project at Los Alamos until that was over. In 1947 there were major changes in the Department of Defense. Someone in the new structure decided to dig up the Philadelphia project to see if they could find out what went wrong. They asked Von Neumann to "take another look" at the project. He agreed.
There is another matter. Starting about August 6th, 1943, UFOs appeared over the Eldridge for about six days. They were there during the test. One of the UFOs was sucked up into hyperspace with the Eldridge and it ended up in an underground facility in Montauk in 1983. It contained a charging device which some aliens made us go back and get for them, as they didn't want humans to have it. We don't know who they were. Pruett was concerned about an alien invasion.
Also, Von Neumann was called by the government to come and assist in the examination of a crashed UFO in 1947 at Aztec. Another crash occurred at Aztec about a year later. The first crash had greys on it and none survived. At least one occupant survived the second crash. The radar systems unintentionally brought down the craft. Radar was used intentionally after that until the aliens got wise to it.
The occupant of the second crash was not a grey, and Von Neumann got to talk with it. Von Neumann asked it what the answer to the invisibility problems could be. He learned that he had to go back and do his homework in metaphysics. The nature of the problem was that the personnel on the ship were not locked to the zero-time reference of the ship. Humans are normally locked to the point of conception as a time reference, not a zero-time reference. The time stream lock allows the person to flow in synch with the system so interaction is possible.
Time locks are fragile. All the power of the project disrupted the time-locks of the people on the deck on the ship. When the ship came back in time, the people didn't come back to the same reference.
Von Neumann realized that he needed a computer, as well as some knowledge of metaphysics in order to be able to lock the time reference of the people to the time reference of the ship. He built a computer in 1950 for the purpose. It was ready to be installed in 1952 and a test was performed in 1953 that was successful. They didn't go floating off into space when it was over. At this point, the Navy canceled Project Rainbow and changed the name to project Phoenix.
A lot came out of the negative effects of the Rainbow project. Some of it led to mind control research programs in the Phoenix project. The invisibility research produced some Stealth technology as well as other highly classified projects.
In 1983, they decided to apply mind control to all participants in these projects in an effort to cover them up. They had also been working on another project: age regression. Now, Tesla had sought back in the 1940's to develop equipment that could help the members of the crew after they lost time-lock . The government developed it into the age regression program. It was physical age regression. A person
retained the memory they had from the older age.
Tesla's theory was that if you took the individual's time-lock and moved it forward in time than you would remove aging. That's what happened. It took between 30 and 60 days for the body to complete the change to the new time reference.
When our astronauts first landed on the moon in 1969 they were greeted by a fleet of disks sitting on the rim of a crater. The astronauts asked their superiors if they knew about these disks. They were told "yes", that they were American disks. The astronauts were angry at being used as public relations men by the government.
Well, the aircraft combines two aspects for invisibility. One of the aspects relates to the construction and coating applied to the surface. The other aspect relates to an electronic type of invisibility package which is a result of work done on the Philadelphia experiment years ago. Also, the stealth has a secondary drive system which is very advanced and allows it to fly in space. The assistant director of NASA admitted that this came straight out of alien technology. He admitted this to the public.
There are breaks in the government secrecy programs that are starting to show up. More and more people are getting totally disgusted with government activities and attitudes and they are beginning to talk.
The Phoenix Project was a project that evolved out of the Philadelphia Project. It was a project that the Navy did in the 1930's and 1940's in an attempt to make ships invisible. They threw the switch one eventful day and the ship went into hyperspace. They had all sorts of problems with the people on the boat. It was a huge success as well as a huge failure - then they shelved it. Around 1947 it was decided to re-activate the project and it was moved to Brookhaven National Laboratories with Dr. John Von Neumann and his associates. Out of Phoenix I came Stealth technology. It also produced all sorts of energetic little toys like the radiosonde.
The radiosonde was a little white box that they attached to a balloon and sent up into the atmosphere. The government told people that it involved gathering weather data. It used a very unusual type of pulse modulation. In most cases they used a CW (continuous wave) oscillator and pulsed the signal. This turned out to be a very efficient conversion of electrical energy to etheric energy. They were designed up at Brookhaven National Labs. I started to talk to people at Brookhaven and ran into a retired gentleman who used to work there. He told me that the design was originally done by Wilhelm Reich.
The story goes that in about 1947 Wilhelm Reich handed the US Government a weather control device, a device that would do DOR-busting. Reich thought that if he could decrease the amount of DOR that storms would not be so violent. (DOR is the result of orgone energy coming into contact with an enclosed radioactive source). Deadly Orgone Energy is DOR. The government sent the device up into a storm and it did reduce the intensity of the storm. They worked.
The Montauk Project was a combination of Wilhelm Reich's work and the Philadelphia Experiment. There were two separate projects going on in Phoenix One. You had the invisibility aspect and you had the development of Wilhelm Reich's weather control. Toward the end of the Phoenix project, by using some of Wilhelm Reich's concepts and some of the transmission schemes used from the "radiosonde" project, they found that you could combine the two factors and use them for 'Mind Control'.
The people who were running it went to the military and proposed that they could use it to "influence the minds of the enemy". The military loved the idea, and let them use the old Montauk Air Force Base. Among the equipment requested was an old SAGE radar unit, which was on the base. The base was shut down and everything was auctioned off. The group then moved in from the Brookhaven Labs. That began what we call Phoenix Two. They spent the first ten years from about 1969 to about 1979, researching pure mind control.
The first part of the mind control project was to take an individual and stand them about 250 feet away from the antenna. The SAGE radar had a peak pulse power of .5 MW. The antenna had a gain of 30db. That means an effective radiated power of at least a gigawatt. It was nominally a gigawatt. Can you imagine what that would do to people? I think its amazing these people are still here. It does things like burn out brain functions, create neurological damage, scar lungs from heat, etc. They tried this with a number of people and there were few survivors. The subjects were often indigent people they grabbed off the streets.
The project was controlled by Dr. John Von Neumann and Jack Pruett. About 30 people worked there. It was a joint project...Air Force & Navy. Original funding came from the Nazi government funds. In 1944 there was an American troop train that went through a French railroad tunnel carrying $10 billion in Nazi gold which they had found.
It was $10 billion at the 1944 price of $20 per ounce. The train was blown up in the tunnel. It killed 51 American soldiers. The gold turned up ten years later at Montauk. This has been verified. That money was used to finance the project for many years as the value of gold went up.
They spent all of it and ran out of money. That's when they tapped on ITT, who funded it. ITT was owned by Krupp in Germany. In terms of personnel, many of the civilians and scientists there were all ex-Nazi's who came from Germany both before and after the war ended.
The project was under US Government surveillance. The intelligence community knew what was going on and the CIA monitored everything, as did other government intelligence agencies. The field of players who actually operated on the base was small, between 30 and 50.
The funding was entirely private. After 1983, Senator Goldwater found out about it and started an investigation. He couldn't find any trace of government funding. Pruett was the metaphysical director of the project. He was Air Force. After he left Dr. Herman C. Untermann took over. They had an electronics expert, Dr. Mathew E. Zerrett, who came over from Germany in 1946 with Werhner von Braun. Probably the reason that they ran out of money is that they had a total of 25 bases around the United States to support. The last of the bases shut down August 12, 1983. The base at Montauk, where all the stations got their zero-time reference from, shut down and the other two remaining bases went down with it.
Other experiments included time travel. No one has picked up a tangible future beyond 2012 AD. There is a very abrupt wall there with nothing on the other side. A working time vortex was created to the future.
At one point a creature came through and everyone went into a panic. They shut the transmitter off. The creature ate people and equipment. They had to go back and shut down the unit in Philadelphia in order to shut off the unit in the future so they could stop this creature in 1983. This was on August 12,1983. The vortex locked on to the 12 August 1943 test and formed a loop.


text:
Blog, Cultural Heritage, Cultural Heritage Preservation
Must-See TV: 'The Sit-In'
May 31, 2020 Faye Anderson
For one week in February 1968, Harry Belafonte hosted "The Tonight Show," then the highest-rated late night television show. Belafonte's guests included Robert F. Kennedy, Bill Cosby, Lena Horne, Nipsey Russell, Paul Newman, Wilt Chamberlain, Buffy Sainte-Marie, Dionne Warwick, Aretha Franklin, Sidney Poitier and Dr. Martin Luther King Jr.
A documentary about that magical week of interviews and performances, "The Sit-In: Harry Belafonte Hosts the Tonight Show," was scheduled to be screened at the 2020 Tribeca Film Festival. But along came the coronavirus. Variety reports:
It was 1968, war was raging and racial tensions in America were at a boiling point, dividing the nation. In February, Harry Belafonte stepped in for Johnny Carson to host "The Tonight Show." It was a monumental moment in which an African American would be the frontman of the most dominant program in late night — and perhaps all of TV — for an entire week. Guests included Lena Horne, Paul Newman, Aretha Franklin, Martin Luther King Jr. and Robert F. Kennedy.
The doc was scheduled to screen in April at the Tribeca Film Festival, not far from where "The Tonight Show" was filmed in the '60s, with an after-film discussion that was to have included Belafonte's daughter, Gina. "We were so excited," says Richen. "It's a New York story, and I'm a New Yorker."
But as with many eagerly anticipated independent films this year, the movie's launchpad disappeared when the festival was canceled due to the coronavirus, making it a work about the events of yesterday informing today — trumped by the health crisis of the moment.
ActivismArtCivil RightsCoronavirus LockdownCoronavirus PandemicHarry BelafonteMartin Luther King Jr.Social Change
Previous PostWHYY House Concert SeriesNext PostFrank Rizzo (1999-2020)

redpajama_set_name: RedPajamaCommonCrawl


As we discussed in the previous article, one of the major scale challenges for Git is dealing with the linear costs associated with having too many refs. Let's look a little more closely at the problem, and how we've solved it. And of course, since there's no such thing as a free lunch, we'll discuss the tradeoffs created by our solution.
We often refer to this scale challenge as "too many branches" because it's easier to talk about, but in reality the challenge is "too many refs".
To summarize, Git history is a Directed Acyclic Graph (DAG) of commits, and a ref is a pointer to one of those commits. Branches and tags are special types of refs, but there are other kinds of refs as well. Refs are used to give convenient names to commits. They are also used in negotiations between the Git client and server to figure out how much contents to fetch and push. And in both cases, having lots and lots of refs can cause problems.
Git looks up the URL of the repo. By default, this is the URL configured for the origin remote.
Git takes that list of refs and compares it with the list that it currently has locally. For each of these tip commits, Git checks to see if it already has that commit id, and if not, it will have to request it from the server.
The Git client then sends a request to /upload-pack with information about which commit ids it has and which commit ids it wants. The client and server go back and forth a few times until they whittle the list of haves and wants down as much as they can.
The main point to take away from all of that is that the client and server have to do a lot of calculations to figure out what to fetch, and the number of calculations grows linearly with the number of refs. So the more refs there are, the longer it takes to even figure out what to send, before the client can start downloading the new contents. Before we did anything to fix this, devs in the Azure DevOps repo had a pretty frustrating experience when they fetched. After typing "git fetch" or "git pull", they would see the first acknowledgement from the server ("remote: Microsoft (R) Visual Studio (R) Team Services") fairly quickly, and then… nothing… sometimes lasing 5 minutes or longer, before a message like "remote: Found X objects to send". Only then would the download of new contents actually begin. The Azure DevOps repo typically has as many as 20K refs in it, and the negotiations for that many refs take a while.
There are also usability issues with having too many refs. Have you ever tried running "git branch -a" in a repo with 20K branches? Good luck finding the one you want.
While refs are technically unstructured and can have whatever names you want to give them, we learned early on that you really need a good naming structure to help organize all those branches. In the Azure DevOps repo, we like to use the pattern users// for topic branches, and similar patterns for release branches (releases/), team branches (teams/), and other "types" of branches that we commonly use. We'll talk more about those best practices in an upcoming article. We have also updated the tools that we build (like the Azure DevOps web UI and Visual Studio's Team Explorer) to render branches as a hierarchy, but not all Git tools do this. See the example above about listing branches using the Git command line.
But even with those improvements, having 20K refs in the Azure DevOps repo, or 100K+ refs in the Windows repo presents a serious usability challenge for a dev who needs to find one branch out of that huge list.
Our solution to this problem is to allow a repo to be configured such that it hides most of the refs from the client. We were able to do this with no changes at all to the Git client or to the protocol. Because the first step in the fetch protocol is that the client asks the server for the list of all refs, we simply changed our server to filter its response to that info/refs request, and the rest of the fetch protocol plus all of your existing Git tools continue to work as normal. The difficult part of this is: what refs should we include in that info/refs response? We spent a bit of time refining this, because there are various tradeoffs to consider. The fewer branches you respond with, the less time each person spends fetching, but then they might not get a branch that they care about. We also realized that there are cases where you really don't want the server to lie to you because you know you need every single branch.
To solve these issues, we've allowed for certain branches to be marked as "important" for all users of the repo, we've allowed users to mark additional branches that they know they care about, and we've also allowed you to bypass this feature entirely and specify that you really want all branches.
There are a set of branches in any repo that everyone will be very likely to interact with, like the master and release branches. These refs can be configured to be included in the info/refs response for everyone, so that all users will see them. As an aside, it's very helpful to have a well-organized hierarchical naming pattern for your branches so that you can configure a small number of ref "folders" and not have to keep updating this list all the time.
For the Azure DevOps repo, we know that every user needs the master branch. We also create a release branch at the end of each sprint, with the naming pattern of releases/, and we figure most people will need these branches as well. So we've configured Limited Refs to always return these refs to all of our users. As I write this, this configuration alone reduces the number of visible refs in the Azure DevOps repo from about 20K down to 100.
For the Windows repo, even all of the "important" branches would be too many, so we've taken a more extreme position there and just included the master branch by default. More on this in the tradeoffs section below.
Any branch that you personally created is one that you almost certainly care about. So in addition to returning all of the branches that are configured as important, we also return to you all branches that you have personally created.
And we know that no matter how much flexibility we provide in the configuration of important branches, we can never fine tune it perfectly for each individual person. Therefore in the Azure DevOps web UI (or via REST APIs) you can also mark any branch or branch "folder" as a favorite, and all of your favorite branches are also included in the responses to your info/refs requests.
As a result of that, a typical user in the Azure DevOps repo now sees around 100 branches at clone time instead of close to 20K, and the negotiations at the beginning of fetch now take a couple of seconds instead of minutes. And a typical user in the Windows repo sees a couple dozen branches instead of 100K or more.
When you turn on Limited Refs for a repo and make it the default behavior, all of the filtering rules described above will apply to anyone who uses the normal repo URL. For a typical repo, this URL looks like https://.visualstudio.com/Project/_git/Repo. However, sometimes you just need access to all the refs, and for those situations, we've added an alternative form of the repo URL: https://.visualstudio.com/Project/_git/_full/Repo. By adding that _full part to the URL, you can bypass Limited Refs and get an unfiltered list of refs when you clone or fetch. This is often useful for build servers and other automated tools that know how to manage their own list of refs.
The biggest issue with Limited Refs is that now users can't see all of the branches in the repo. This is of course the whole point – the fewer branches you have, the leaner your repo is. But there are plenty of times when you need to work with a branch that might not be included in the limited set that you're working with locally. The most common example is that someone posted a pull request for their topic branch, and you want to checkout that branch and run some local tests on it. The simplest answer to this is that you can just go mark that branch as a favorite and then fetch again. But this isn't a great answer on its own, because it would require you to have to remember a bunch of steps (go to the web, find the branch, favorite it, go to your repo, fetch) every time you want to work with someone else's branch.
In the Azure DevOps repo, what we've done is adopt a naming pattern that allows people to very easily favorite all of their nearby teammates' topic branches. Across the broader team, there are 400+ people, but any given feature team has around 10 or so people in it. So the pattern we've adopted is that each team creates all of their topic branches using the naming pattern teams///. Each person on a team can then just go favorite the teams/ "branch folder" in the Azure DevOps web UI, and from then on they have access to all branches created by their nearby teammates.
The Windows team has taken a different approach. They've created a command line tool that will call the Azure DevOps REST APIs to favorite a branch.If a user wants to favorite a branch, they can just call that tooland pass in the name of the branch, and then run git fetch again.
This is perhaps the biggest issue with Limited Refs – it requires a fair bit of upfront work to get your branches under control using well-defined naming patterns. Otherwise, it becomes very difficult to manage the set of important branches, difficult to favorite "folders" of branches that you care about, etc.
In an upcoming article, we'll get into more detail about branch naming best practices.
Astute readers often notice that Limited Refs looks an awful lot like forks, so why not just use forks?
This is a bigger topic that we may expand on in a future article, but the short answer is that forks were designed to solve a trust boundary problem. In the open source world, you often accept changes from people with whom you have no trust relationship. In that model, it's very important to confine the changes that other people can make and to selectively decide which parts of their changes you will accept into your own repo.
Within a team in a typical enterprise environment, there is no trust issue, because you all work for the same company. Forks can still be useful in this environment, and many teams prefer to work using forks. However, forks do add some additional hurdles, and it's often more efficient to just have everyone work in a single repo. For example, consider the scenario we talked about earlier where someone else pushed a branch and you just want to check it out locally and run some tests on it. With forks, you have to manage multiple remotes, carefully manage where you're pulling from and pushing to, etc.
So forks are great, and Limited Refs are great, and you need to decide which one is right for your team. In the end, forks solve a trust boundary problem, and Limited Refs solves a scale problem.


text:
Labor Council Revamps Online
The Labor Council of NSW has launched its new website, which is the newest addition to the LaborNET family.
Labor Council Online located at http://council.labor.net.au will present all of the NSW Labor Council's work online for the information of affiliates and the general public.
The site features all of Council's circulars online, all Labor Council documents online, the Information Centre catalogue, Labour Review, Meetings, Events and much more.
Private areas (indicated by a yellow "lock") will only be assessable to affiliates who have been issues with usernames and passwords.
URL: http://workers.labor.net.au/110/news9_online.html


text:
Q: Visual Studio 2008 'find in files' reg-ex Really easy question for somebody, I know it's really simple but I just can't work out how to search for two matching strings using the regex 'find in files' search in Visual Studio 2008.
So for, if I have lines:
One twoo three four five
On tw three four five
One two thre fourr five
One two three fur five

I want to search for 'two' and 'four' (so returning only the first and third lines). Thanks.

A: How about just (?=.*two)(?=.*four)?

redpajama_set_name: RedPajamaStackExchange


The region of Madrid has just one province and of course the capital city, Madrid. The capital is in this location for no other reason than it is the centre of Spain, making it around 300Km from the sea in any direction and on a plateau approximately 650m above sea level. The location results in a climate that can be very cold in winter and very hot in the summer.
The city centre of Madrid does however have all the character, architecture, old alleyways and medieval buildings that you would expect in the capital of this country and has seen a lot of improvements in the last two decades.
Madrid can be accessed by Madrid Airport.


text:
<?php
/*************************************************************************************************************************
PHP GENERAL FUNCTIONS
- provides functions needed by all types of tests
*************************************************************************************************************************/

	function createNewTestGeneral($my_test_data) {
	//creates a new entry in the table 'tests', returns test ID on success
	//params: my_test_data = array(); (associative array with keys: test_type_string, test_name, test_level)
		if (isset($my_test_data['test_type_string']) && isset($my_test_data['test_name']) && isset($my_test_data['test_level'])) {
			$db_con = new Db_Connection();
			$test_type = $db_con->selectEntries(false, 'test_types', array("where" => "type_string = '" . $my_test_data['test_type_string'] . "'"));
			$test_id = $db_con->insertEntry(true, 'tests', array("test_name" => $my_test_data['test_name'],
																"test_type_ID" => $test_type[0]['type_ID'],
																"test_level_ID" => $my_test_data['test_level']));
			if ($db_con->getErrorMessage() !== '') { //some error occurred during database queries
				return $db_con->getErrorMessage();
			} //if
			else {
				return $test_id;
			} //else
		} //if
		else {
			return 'The function createNewTestGeneral has not been provided with the correct parameters!';
		} //else
	} //function createNewTestGeneral

/*************************************************************************************************************************/

	function dieIncorrectAccess() {
	//causes script to die, printing message about incorrect access
		die('This page has not been accessed in the correct way! Click here to go to the start page of the E-Test Editor.');
	} //function dieIncorrectAccess

/*************************************************************************************************************************/

	function printAttr($my_attr, $my_value) {
	//if value is set, prints HTML attribute with that value
		if (isset($my_value) && ($my_value != '')) {
			echo ' ' . $my_attr . '="' . $my_value . '"';
		} //if
	} //function printAttr

/*************************************************************************************************************************/

	function updateTestGeneral($my_test_data) {
	//updates entry in table 'tests', returns true on success
	//params: my_test_data = array(); (associative array with keys: test_type_string, test_name, test_level, test_ID)
		if (isset($my_test_data['test_type_string']) && isset($my_test_data['test_name']) && isset($my_test_data['test_level']) && isset($my_test_data['test_ID'])) {
			$db_con = new Db_Connection();
			$test_id = $db_con->updateEntry(true,
											'tests',
											array("test_name" => $my_test_data['test_name'],
												"test_level_ID" => $my_test_data['test_level']),
											array("where" => 'test_id = ' . $my_test_data['test_ID']));
			if ($db_con->getErrorMessage() !== '') { //some error occurred during database queries
				return false;
			} //if
			else {
				return true;
			} //else
		} //if
		else {
			return 'The function updateTestGeneral has not been provided with the correct parameters!';
		} //else
	} //function updateTestGeneral

?>

redpajama_set_name: RedPajamaGithub


text:
Apple iPhone 6 to feature NFC connectivity and wireless charging
iOS Apple
Published: Jun 06, 2014, 7:44 PM
Alan F.
A source close to the Apple iPhone 6 says that the device is going to have NFC connectivity when launched. In addition, the iPhone 6 will offer wireless charging, improved antennas and a larger screen. The NFC connectivity will allow the iPhone to be used for mobile payments. Apple could join the Isis mobile payments system co-owned by Verizon, T-Mobile and AT&T. In fact, a special case is already available for the Apple iPhone 4 and Apple iPhone 4s that adds NFC support and allows the phones to be used to make an Isis mobile payment.
The Apple iPhone 6 will also support faster data speeds. While the iPhone 5 range supports a Category 4 LTE radio with speeds as fast as 150Mbps, iPhone 6 is expected to have support for Category 6 LTE, or 300Mbps. And while the source says that wireless charging will be part of the iPhone 6, we are not informed about which standard Apple will use. The iPhone 6 will feature a surface underneath the shell, which will connect to an inductive charging surface for energy transfer.
The larger screen for the iPhone 6, rumored to be 4.7 inches, takes up more of the real estate on the front of the phone. The border that surrounds the iPhone screen is smaller on the next iteration of the smartphone. Speaking of the screen, the source says that it will have a new scratch-resistant glass. That could mean that a sapphire glass screen is coming.
As for the size of the screen, we could see an increase in the resolution from the current 640 x 1136 to 960 x 1704. This would allow the aspect ratio to remain the same 16:9 seen on the Apple iPhone 5, Apple iPhone 5c and Apple iPhone 5s. On a 4.7 inch screen, the pixel density would be 416ppi. On the rumored 5.5 inch phablet, the pixel density would work out to 356ppi.
With a story like this, you need to cast a cynical eye on the story and take it with the usual grain of salt. If you need two grains to keep you centered, that is okay too.
Thanks for the tip!
source: VentureBeat


The chloroplast protein CP12 has been shown to regulate the activity of two Calvin cycle enzymes, phosphoribulokinase (PRK) and glyceraldehyde-3-phosphate dehydrogenase (GAPDH), by the reversible formation of a multiprotein complex. In Arabidopsis there are three CP12 genes, CP12-1, CP12-2, and CP12-3, and expression analysis suggested that the function of these proteins may not be restricted to the Calvin cycle. Reverse transcription-PCR analysis was used here to investigate further the expression patterns of the three CP12 Arabidopsis genes together with the genes encoding plastid GAPDH (GAPA-1 and GAPB), PRK (PRK), and plastid NAD-dependent GAPDH (GAPCp1 and GAPCp2) during development, in response to changes in light, temperature, and anaerobic conditions. Expression of the CP12-2 gene was similar to that of the Calvin cycle enzymes PRK and GAPDH. However, this was not the case for CP12-1 and -3 which were both expressed in roots. Analysis of transgenic Arabidopsis lines expressing CP12::GUS fusion constructs revealed that the CP12 genes display different spatiotemporal expression patterns. The CP12-1 gene was expressed in root tips whilst CP12-3::GUS expression was evident throughout the root tissue. The most unexpected finding was that all three CP12 genes were expressed in floral tissues; CP12-1 and CP12-2 expression was detected in the sepals and the style of the flower, while in contrast CP12-3::GUS expression was restricted to the stigma and anthers. Taken together, the data suggest that the redox-sensitive CP12 proteins may have a wider role in non-photosynthetic plastids, throughout the plant life cycle. © 2008 The Author(s).


You are visiting the placeholder page for Wanda Bell. This page is here because someone used our placeholder utility to look for Wanda Bell. We created this page automatically in hopes Wanda Bell would find it. If you are not Wanda Bell, but are an alumni of Hobbs High School, register on this site for free now.


Bechtle acquires HanseVision, the experts in SharePoint.
About Bechtle Press Press Releases Bechtle acquires HanseVision, the experts in SharePoint.
Bechtle AG strengthens its position in the software solution market by acquiring HanseVision GmbH, Hamburg. The company, well-known for its expertise in Microsoft solutions, has a special focus on the increasingly relevant SharePoint technologies. HanseVision was founded in 1999 by Lorenz Goebel, the current CEO, and employs a staff of 22.
Neckarsulm, 29 July 2011 – Bechtle AG continues to follow its strategic course as an IT solutions provider and expand its business in the software and application solutions segment by acquiring HanseVision GmbH, an established company in this sector. Their range of services includes consulting, planning and implementation, as well as operations and coaching. Like Bechtle, the Microsoft Gold Partner HanseVision can count small and medium-sized businesses, large enterprises and the public sector among its customers.
HanseVision provides solutions for employee and enterprise portals, business intelligence and document management, among other things. HanseVision has an accredited development department, comprehensive industry and consulting expertise, and experience in SAP integrations. HanseVision's employees are also known throughout the industry as the authors of SharePoint books and moderators of one of the largest XING groups on the subject.
Bechtle expects significant synergies and cross-selling effects in its traditional system house business through HanseVision. "With this acquisition, we've taken another step towards positioning ourselves as a full-service provider in the market for application solutions. We've also further reinforced the quality of our long-standing partnership with Microsoft, which was important for us," says Norbert Franchi. HanseVision performs cloud consultations and other services on behalf of Microsoft, and implemented one of the first cloud computing projects based on Windows Azure, Microsoft's cloud services platform, in Germany.
Bechtle has already implemented a series of projects with HanseVision. HanseVision CEO Lorenz Goebel: "We've already worked in close co-operation in various customer situations in the past. This was a very comfortable starting point for the decision to incorporate the company into the Bechtle Group. I'm convinced that we're an excellent fit for Bechtle and that we can benefit considerably from one another. We see ourselves as a strong team in a strong community."
Lorenz Goebel will stay on board in his role as CEO and HanseVision will continue to operate under its own brand name. Both partners have agreed to keep the purchase price confidential. HanseVision's revenue amounted to 3.6 million euros in the fiscal year 2010.
SharePoint is a comprehensive portal technology used in solutions for managing documents, content, forms, workflows and processes. SharePoint can also be used to set up an Internet presence, or intranets and extranets. For example, HanseVision was instrumental in creating an Internet presence for www.dataport.de and www.apetito.de. With SharePoint, all applications are integrated into a shared user interface and linked to one another, making this an attractive solution for teams working at different times or in different locations. It was designed to significantly increase productivity and optimise business processes.


text:
Anti-Empire - Anti-Empire
Yemen's Resistance to Saudi Invasion Kills Leader, President of 40 Years, When He Tries to Switch Sides
Yemen's Saleh was ended by his own double-dealing when he tried to double-cross the Houthis
Olivia Alabaster	 5 Dec 17 399 0
Editor's note: Ali Abdullah Saleh was Yemen's president. He was not the "ex-president" as foreign media and foreign governments styled him. Hadi whom the media calls President lives in Saudi Arabia under the watchful eye of his Saudi backers who forbid him from relocating to Yemen. Saleh meanwhile sat in the capital Sanaa and continued to command large chunks of the military which had always remained loyal to him. Who then was the actual President?
Saleh ruled Yemen since 1978. In the post 9/11-era he postured as a loyal US ally in the war on terror. He played up the al-Qaeda threat in his nation to secure US backing and military aid, which he then used to mainly fight the Zaidi (Fiver Shia) Houthi rebels who were a much bigger pain in his side.
Trouble for Saleh was that once the Arab Spring protests broke out Washington decided it was time for some spring cleaning. Expendable long-serving dictators in the Middle East would be replaced with updated versions. Thus Saleh was forced out and his vice-president replaced him after an "election" in which he was the only candidate. Except Saleh had a masterstroke left to play. He did the unthinkable and reached out to his mortal enemies the Houthis recruiting them for a common march on Sanaa.
Once they took the capital, however, the Saudis intervened against him — but if anything that only shored up his political fortunes as the blatant inhumanity and criminality of the polyglot assault on Yemen orchestrated by Saudi Arabia to return Hadi to Sanaa transformed Saleh into a symbol of anti-Saudi resistance and granted him a newfound measure of legitimacy. — So then it was a grave mistake for Saleh indeed when he decided to cast all of that away and switch back to the Saudi side. His enemies-turned-allies made sure the "grave" part was true in the literal, as well as the political sense, when they killed him for it. (Apparently the switch was orchestrated by UAE which never cared much for Hadi, and the Saudis were presumably willing to let it unfold as a way to extract themselves from the Yemeni quagmire.)
Ali Abdullah Saleh spent almost 40 years on top in a country either on the brink or at war with itself, surviving assassination attempts, six wars with the Houthis, wars with southern secessionists and a humiliating ejection in the so-called "Arab Spring".
Ruling Yemen, he said, was like "dancing with snakes" – the secrets to such longevity were constant political twists and turns, and the knack to know when to double-cross.
But the snakes finally bit on Monday, when the Houthis, his latest enemy-turned-ally-turned-enemy, ambushed him, shot him dead, and paraded his body for the world to see.
It brought to a conclusion the life of a man that to the very end, seemed hell-bent on clinging to power at all costs.
Himself a graduate of political coups, Saleh spent his decades in power navigating rebellions from every angle, but was widely seen as the only man capable of maintaining a precarious balance of power. However Saleh's last-minute defection to Saudi Arabia on Saturday was to be a volte-face too far.
One of the Middle East's so-called "strongmen", Saleh had governed Yemen since its reunification in 1990, after 12 years ruling the north Yemen Arab Republic.
A Zaidi Shia, a branch of Islam adhered to by around a third of the country's population, Saleh was born in 1942, in Bayt al-Ahmar, in Sanaa province. His family came from the Hashid tribe, the largest in Yemen.
Saleh joined north Yemen's army at 16 in 1958 and within four years fought in support of an army-led coup of 1962 which replaced the Zaidi imamate with a Nasserist-inspired Arab republic.
He rose quickly through the ranks and within 15 years, at the age of 36, was elected president of the Yemen Arab Republic after predecessor Ahmad al-Ghashmi was assassinated by an exploding briefcase.
Ghashmi's predecessor was himself assassinated eight months before that, and Saleh soon came to represent a newfound stability amidst a chaotic political scene.
In 1990, Saleh oversaw the unification with Yemen's communist south, and was named president of the newly united country, and quickly quashed a southern secessionist bid in 1994.
Beside from southern flare-ups, as leader of Yemen for 33 years, Saleh also had to contend with sporadic northern rebellions, led by members of his own Zaidi community, and a growing al-Qaeda insurgency.
Personal fortune
But this "master tactician" ruled at a price, and had, since his ascendancy to power, kept his friends and relatives close, appointing his son Ahmad as Commander of the Republican Guard in 2000 and amassing a personal fortune, according to the UN, estimated at between $32bn and $60bn.
Under a law introduced in 1995, Saleh soon began distributing formerly public lands to allies and friends, according to documents seen by a UN panel, "to strengthen his alliances in the south and considerably multiply the wealth of his family."
His billions in assets, "are said to take the form of property, cash, shares, gold and other valuable commodities," the UN said in 2015, and are thought to be located across 20 different countries, hidden under false names or being held by others.
Unashamedly proud of his ability to maintain relative stability across his realm, and in a now emblematic quote, in a 2008 New York Times interview he compared ruling Yemen to "like dancing with snakes."
But asides from his often quirky persona – the Guardian noted in 2010 that "in contrast with the sober image cultivated by his counterparts in other Gulf states, he is pictured on his own website in full flow on a tenpin bowling lane, scuba-diving and smiling while wearing a cowboy hat – Saleh was an autocratic ruler.
His cousin Mohammed al-Qadhi, according to a Wikileaks cable published in 2009, said that "since 1994, he decided that he was the only man capable of making decisions in this country".
"I have tried to tell him that Yemen has serious problems, but he gets angry and shuts me out… He doesn't listen to anyone.
"Saleh was a giant – beloved and reviled by many across Yemen," says Jeb Boone, a former Yemen-based journalist.
"Depending on who you asked, his rule was marked by brutal political repression or visionary leadership."
By 2011, protests against his rule broke out across the country, inspired by revolutionary fervour gripping Tunisia and Egypt.
Dithering in his commitment over an initial promise to step down, Saleh was badly injured in the bombing of the presidential palace in June of that year, and he immediately sought medical treatment in Saudi Arabia, and later the US.
In February 2012, Saleh officially relinquished control, after more than three decades in power, with his vice-president Abd Rabbuh Mansour Hadi taking charge.
Out of the spotlight?
But for a man with an ego which once saw him pose for a campaign poster astride a white horse, bedecked in a Yemeni flag, and who spoke about himself in the third person in interviews, it soon became clear that Saleh missed life in the spotlight.
"From Saleh's perspective, he could never accept that he was taken out of power," Alma Abdul Hadi Jadallah, former regional expert on the UN Panel of Experts on Yemen, told PRI in 2015.
"He also looked around with the Arab Spring and saw that other presidents have not given up their seat in spite of local discontent. So he felt shortchanged by the 2011 agreement, even though he had negotiated immunity for himself."
In the few years he was out of power, Saleh was, ostensibly, penning his memoirs in his compound in Sanaa.
But behind the scenes he was meeting with various former enemies, from members of AQAP, al-Qaeda's Yemeni branch, to the Houthis, according to the UN, as well as foreign dignitaries.
By 2014, Saleh appeared to find hope of a political comeback in this latter grouping, and soon the strange bedfellows were to retake the capital, Sanaa.
Under house arrest by the Houthis, Hadi escaped to his hometown of Aden in January 2015, where he rescinded his own resignation, and fled to Saudi Arabia in search of support.
This soon came by way of Operation Decisive Storm, launched in March of that year, in support of Hadi's UN-recognised government.
Some 10,000 people have now lost their lives as a result of that war, with a cholera outbreak now the worst in recorded history killing thousands more.
In recent months, an ever-shaky coalition between the Houthis and Saleh appeared to be fracturing at the seams – as has the anti-Houthi coalition itself.
By the 35th anniversary of Saleh's party, the General People's Congress, in August, this febrile atmosphere was threatening to open up a new front in the war. Posters of Saleh were being torn down by Houthi supporters in Sanaa, amid rumours of clashes between the two sides.
Over the last week, the tension had turned into all-out fighting, with over 125 people killed.
Reneging once more on his latest allies, Saleh on Sunday formally denounced his partnership with former foe, the Houthis.
Immediately embraced as a victory by Saudi Arabia, the coalition took Saleh's abandonment of the Houthis as an opportunity to renew a push for the capital, launching air strikes. Saleh was no longer a "deposed president", according to Saudi media, but a "former" one.
But it was to be Saleh's last u-turn. Fleeing to his hometown of Sanhan on Monday, after the Houthis destroyed his Sanaa residence, Saleh was killed, his dead body dragged in a garish blanket of orange and lime green – footage likely to join the public consciousness alongside the final moments of Libyan leader Muammar Gaddafi and Saddam Hussein's spider hole discovery.
Adam Baron, a Yemen expert at the European Council on Foreign Relations, says he is at a loss for words.
"What a way to go. You get this reputation for being a meaty, masterful manipulator of the Middle East, and suddenly you're lying on the ground with a head wound in the middle of Yemen."
"Anyone who says they know what is coming next, is lying," he cautions. "But it's hard to see there not being more conflict."
"With Saleh's death, the Houthis have tightened their political grasp over northern Yemen, much to the chagrin of the Saudis," Boone says.
"For all his unpredictability, the Saudis were much happier to have the devil they knew back in power in Yemen.
"The Saudi response to Saleh's death, with the support of the US and GCC partners, will involve more wanton destruction, famine and pestilence inflicted on the people of Yemen."
Source: Middle East Eye
You may back the site at:
Anti-Empire — So Good It's Banned in Turkey Anti-Empire — Best on Syria
Thank you! Please check your inbox to verify.
Facebook Tasty Memes


Find here Chrome Ore suppliers, manufacturers, wholesalers, traders withUsing the crusher to broken it belowmm, chrome ore crusher machines manufacturer mexico.
chrome ore crusher machine for sale in mexico. chrome ore crusher machines manufacturer mexico Oct.th. Gold mining equipments for saleGold ore machinery .
Tantalite Crusher Supplier Mexico galaxynorthavenue. tantalite crusher supplier mexico ajitindia. chrome ore crusher machines manufacturer mexico.
Home > Products > Chrome Ore Crusher Machines Manufacturer Mexico Chrome Ore Crusher Machines Manufacturer Mexico. china mobile crusher .
tantalite crusher machine for sale in mexico tantalite crusher machine for sale in mexico. used tantalum Chrome Ore Crusher Machines Manufacturer Mexico. t.
chrome ore processing manufacturers india. chrome ore crusher machines . mining machinery for chrome ore mineral processing machines.


Compose more helpful bug reports and save time with automatically captured web page screenshot, environment details and application usage history.
From planning, to coding, to testing, to customer support, DoneDone is the straightforward, no-nonsense issue tracker. Start a free 30-day trial today!
Sifter is designed to be a simple bug and issue tracker for small teams and works especially great for teams with non-technical folks involved.


text:
Q: Correct way to calculate $\Pr \left[ {X > \frac{2}{Y},X > \frac{4}{Y}} \right]$ where $X,Y$ follow the exponential distribution? What would be the correct way to calculate $\Pr \left[ {X > \frac{2}{Y},X > \frac{4}{Y}} \right]$ where $X,Y$ are independent random variable that follow the exponential distribution. I end up with different results and a mind full ò doubt
1/ The first way $\Pr \left[ {X > \frac{2}{Y},X > \frac{4}{Y}} \right] = \Pr \left[ {X > \frac{2}{Y}} \right] \times \Pr \left[ {X > \frac{4}{Y}} \right]$
2/ The second way $\Pr \left[ {X > \frac{2}{Y},X > \frac{4}{Y}} \right] = \Pr \left[ {X > Max\left[ {\frac{2}{Y},\frac{4}{Y}} \right]} \right] = \Pr \left[ {X > \frac{4}{Y}} \right]$
3/ The third way: use order statistics to find the pdf of $Z = Max\left[ {\frac{2}{Y},\frac{4}{Y}} \right] = {F_{\frac{2}{Y}}}\left( z \right){F_{\frac{4}{Y}}}\left( z \right)$ and then invoking the law of total probability
$\Pr \left[ {X > \frac{2}{Y},X > \frac{4}{Y}} \right] = \Pr \left[ {X > Z} \right] = \int\limits_{x = 0}^{x = \infty } {\Pr \left( {X > x} \right){f_Z}\left( x \right)dx}$
I am thinking that I am having some misconception in my head since I am an engineer and not a mathematician.
P/S: As a though exercise and extension to the original problem:
In case their is a slight changes with the introduction of the variable $Z$ which is also an independent random variable follow the exponential distribution as $\Pr \left[ {X > \frac{2}{Y},X > \frac{4}{Z}} \right]$ what would be the best approach selected from 3 of the above way  ?
Please help me clear my doubt, thank you very much

A: Since $\mathbb P(Y>0)=1$, it is clear that $\mathbb P\left(\frac 4Y>\frac 2Y\right)=1$ so $\left\{X>\frac 2Y\right\}\cap\left\{X>\frac 4Y\right\} = \left\{X>\frac 4Y\right\}$. Now, for independent continuous random variables $X$ and $Y$ with densities $f_X$ and $f_Y$, the density of the product $Z=XY$ is
$$
f_Z(z) = \int_{\mathbb R} f_X(x) f_Y(z/x)\frac 1{|x|}\ \mathsf dx.
$$
Supposing $X\sim\mathsf{Expo}(\lambda)$ and $Y\sim\mathsf{Expo}(\mu)$, we find that
$$
f_Z(z) = \int_0^\infty \lambda e^{-\lambda x}\mu e^{-\mu\frac zx}\frac 1x\ \mathsf dx = 2\lambda\mu K_0(2\sqrt{\lambda z\mu}),
$$
where $K_0$ denotes the modified Bessel function of the second kind. We may then compute
$$
\mathbb P\left(X>\frac 4Y\right) = \mathbb P(Z>4) = \int_4^\infty f_Z(z)\ \mathsf dz = 4\sqrt{\lambda\mu}K_1(4\sqrt{\lambda\mu}).
$$
More specifically, $K_n(z)$ satisfies the differential equation
$$
z^2y'' +zy' -(z^2+n^2)y = 0.
$$

A: As said the second way is correct.
You cant do the first way since the events $\{X>\frac{2}{Y}\}$ and $\{X>\frac{4}{Y}\}$ are not $\textit{Independent}$.