gem install pgI googled:
install postgresql rails windows "no such file to load -- pg"and Peter Mac helped me out. In your Rails 3 Gemfile, make the following change:
# gem 'mysql'
gem 'pg', :require => 'pg'
gem install pgI googled:
install postgresql rails windows "no such file to load -- pg"and Peter Mac helped me out. In your Rails 3 Gemfile, make the following change:
# gem 'mysql'
gem 'pg', :require => 'pg'
http://www.calacademy.org/visit/
Photos are courtesy of SharpShooters.

...the basic principle of sociopaths viewing others as tools instead of people is entirely correct. Sociopathy is more than just a lack of emotion, they literally don’t connect to people the way human beings are supposed to.Reference: http://www.fearfulsymmetry.net/?p=179
All this talk of sociopathy (psychopathy is the outdated term) makes me wonder whether sociopath is the latest incarnation of witch, Communist, racist, or even terrorist. Who in their right mind, when accused of such a despicable thing, even labeled as such by an expert or authority, can figure out what to do or say to disprove it ?


[Alicia] was the subject of a published photograph herself recently, when a Chronicle photographer captured her examining a puddle at Crissy Field after a rainstorm in January.Reference:
The photo, which she adopted as her Facebook profile picture, shows her traipsing ankle-deep through the water, studying the ripples, camera around her neck.
Much like the virus it names, the word influenza comes to us by way of a mutation. The word itself was first used in Italian and originally referred to the influence of the stars - that is, astral or occult influences that would have been felt by many people at once. By the 16th century, though, the word has begun mixing and blending with the meanings of other words and come to refer to epidemic and pandemic flues that simultaneously strike multiple communities (as if the result of some malevolent will).Reference: page 13 in Eating Animals.
In field after field, computing and the Web are creating new realms of data to explore - sensor signals, surveillance tapes, social network chatter, public records and more. We're rapidly entering a world where everything can be monitored and measured, but the big problem is going to be the ability of humans to use, analyze and make sense of the data. Strong correlations of data do not necessarily prove a cause-and-effect link. For example, in the late 1940s, before there was a polio vaccine, public health experts in America noted that polio cases increased in step with the consumption of ice cream and soft drinks. Eliminating such treats was even recommended as part of an anti-polio diet. It turned out that polio outbreaks were most common in the hot months of summer, when people naturally ate more ice cream, showing only an association. Computers do what they are good at, which is trawling these massive data sets for something that is mathematically odd, and humans do what they are good at and explain these anomalies.To analyze statistical data, we use computer programs as tools to work with such information as biological data. Yet another recent article in the New York Times compares and contrasts two of these computer programs, R and SAS (and again I paraphrase):
SAS Institute (the privately held business software company that specializes in data analysis)'s namesake SAS has been the preferred tool of scholars and corporate managers. But the R Project has also quickly found a following because statisticians, engineers and scientists without computer programming skills find it easy to use.Reference:
18AUG2009 6 12.815 37.66Note that on the tail end of the second line, in the last figure, 11.8, I omitted a zero ('0') when I was typing the data in. We'll come back to that later. I decided to record the following four fields for each time I filled the gas tank (all took place at Costco in San Leandro):
14JUL2009 12 4.340 11.8
28MAY2009 6 9.532 24.39
22APR2009 4 7.348 16.01
25MAR2009 2 5.509 11.12
15MAR2009 7 4.230 8.62
04MAR2009 3 11.989 25.16
21FEB2009 7 13.298 27.91
29JAN2009 15 13.989 27.68
03JAN2009 6 12.620 22.70
29NOV2008 16 11.239 20.78
25SEP2008 8 13.929 51.80
G:\tpc247\petrol.txtif you're on Windows, the convention is to delimit or separate folders with a backslash, but this poses a problem for software that is trained to recognize tabs and carriage returns and newlines as '\t', '\r' and '\n' respectively. For reasons of cross-platform compatibility, if there are backslashes in your Windows path, add another one right next to it:
G:\\tpc247\\petrol.txtor replace the backslash with a forward slash:
G:/tpc247/petrol.txt
petrol_01 = read.table("G:/tpc247/petrol.txt", header=FALSE, col.names=c('date', 'pump', 'quantity', 'cost'))
petrol_01$per_gallon <- petrol_01$cost / petrol_01$quantity
petrol_01data petrol_01;
infile "G:/tpc247/petrol.txt";
input date_of_sale$ 5-13 pump_number$ 16-17 quantity 20-25 cost 28-32;
per_gallon = cost / quantity;
proc print data=petrol_01;
title 'Unleaded gasoline purchase history for 1 year, San Leandro, California Costco';
run;
petrol_01 = read.table("clipboard", col.names=c('date', 'pump', 'quantity', 'cost'))petrol_01$price_per_gallon <- petrol_01$cost / petrol_01$quantity
petrol_01
data petrol_01;
input date_of_sale$ 5-13 pump_number$ 15-16 quantity 18-23 cost 25-29;
per_gallon = cost / quantity;
datalines;
18AUG2009 6 12.815 37.66
14JUL2009 12 4.340 11.8
28MAY2009 6 9.532 24.39
22APR2009 4 7.348 16.01
25MAR2009 2 5.509 11.12
15MAR2009 7 4.230 8.62
04MAR2009 3 11.989 25.16
21FEB2009 7 13.298 27.91
29JAN2009 15 13.989 27.68
03JAN2009 6 12.620 22.70
29NOV2008 16 11.239 20.78
25SEP2008 8 13.929 51.80
proc print data=petrol_01;
title 'Unleaded gasoline purchase history for 1 year, Costco in San Leandro, California';
run;
header = FALSEI would find the first record in my dataset on file would be missing from my dataset in R
14JUL2009 12 4.340 11.8did not pose a problem, as long as I ran a previous incarnation of my SAS script:
data petrol_01;However, I didn't like the resulting output in SAS. I have developed a preference for a specific way of representing dates that is 9 characters long and in a format that, to my eyes, is more easy to read. However, when I ran the aforementioned script on my data set, my dates were truncated:
infile "G:/tpc247/petrol.txt";
input date_of_sale$ pump_number$ quantity cost;
per_gallon = cost / quantity;
proc print data=petrol_01;
run;


14JUL2009 12 4.340 11.8has been replaced in SAS with
14JUL2009 12 4.340 2.00 0.46083I imagine SAS would read 11.8 and then be confused because there were no more numbers and I had told it to expect one more, but I can't explain how SAS computed a cost of 2.00. However, I can explain that the price_per_gallon of around 46 cents is simply derived from dividing 2.00 dollars by 4.34 gallons. The fact that the record for May 28, 2009 is missing leads me to conclude that when reading data from file, and your SAS statement specifies columns, SAS seems to expect values for the entire range of columns you specify. I've confirmed this phenomenon, of a missing record when you specify in your SAS statement the columns where values can be found, manifests itself in SAS only when reading data from file, and not from the copy and paste of data.
18AUG2009, 6, 12.815, 37.66In:
14JUL2009, 12, 4.340, 11.8
28MAY2009, 6, 9.532, 24.39
22APR2009, 4, 7.348, 16.01
25MAR2009, 2, 5.509, 11.12
15MAR2009, 7, 4.230, 8.62
04MAR2009, 3, 11.989, 25.16
21FEB2009, 7, 13.298, 27.91
29JAN2009, 15, 13.989, 27.68
03JAN2009, 6, 12.620, 22.70
29NOV2008, 16, 11.239, 20.78
25SEP2008, 8, 13.929, 51.80