Showing posts with label Google Analytics. Show all posts
Showing posts with label Google Analytics. Show all posts

Saturday, September 3, 2011

Cambridge Fan?

So apparently I have a very regular reader in Cambridge, England. I was checking out my Google Analytics statistics for this blog and my personal web page yesterday (I was wondering how many people had looked at my likelihood post/paper). To my surprise, I discovered that between last March and today, and single individual in Cambridge has looked at my blog 238 times, and my personal web page 267 times. That is an average of 2.8 visits per day!

Who are you Cambridge, England? And why do you find my blog/web page so interesting?

Perhaps it is Stephen Hawking looking for inspiration? The strange thing is that I don't actually know anyone in Cambridge.

The only other city with anywhere near this many visits is Berkeley (44 on my web page, and 181 on my blog). However these visits are from 31/64 different people in Berkeley, whereas the Cambridge visitor is ONE person.

Thank you Google for providing me with such detailed information about my followers. Who else is out there reading this? Roll Call people.


My Blog

My Web Page

Wednesday, May 12, 2010

ALL the Quasars

Recently Dinosaur Comics has been emphasizing ALL of everything. ALL the secrets, ALL the balls, ALL the burgers. So today we are going to creating the QSO catalog with ALL the Quasars.

Before we had a brightness limit and some other cuts, but Hennawi wanted me to see what it looked like with all of them.

I did this by modifying: qso_fake_jess.pro with the following call to qso_photosamp:
qsos = qso_photosamp(Z_MIN = Z_MIN, Z_MAX = Z_MAX, NOCUTS = NOCUTS, ILIM = 23.0)

Here is what these QSOs look like in color-color space:


And re-running hiz_kde_numerator_jess.pro:
.run hiz_kde_numerator_jess.pro

To create a new QSO Catalog:
../likelihood/qsocatalog/QSOCatalog-Wed-May-12-14:03:41-2010.fits

Here is what the QSO Catalog looks like in color-color space:



Change likelihood_compute to read in this catalog:
; Read in the QSO file
file2 = '/home/jessica/repository/ccpzcalib/Jessica/likelihood/qsocatalog/QSOCatalog-Wed-May-12-14:03:41-2010.fits'

This run is in the directory:
../likelihood/likev1all

The log file is here:
../logs/100512log.pro

~~~~~~~~

On a side note, I looked at Google Analytics for this blog today. It turns out that over it's lifetime 355 Absolute Unique vistors have viewed my blog! These visitors are from 10 countries and 28 different states. Pretty cool! Yet very few people leave comments on my blog. Everyone reading
this, leave a comment so I know you are out there!

~~~~~~~~

Is anyone else having problem's editing their blogspot blog using Google Chrome? It totally messes up the fonts and when I look at the html it is all funky. Seem strange considering google owns both Chrome and blogsplot! Maybe it is their way of punishing Mac users for the iPhone being better than the Google phone.

Thursday, August 13, 2009

I am HUGE in Berkeley (and NY)

Blogger.com was down last Thursday and not allowing me to post. Sorry for all of you who were eagerly awaiting my blog postings and disappointed by me not fulfilling my quota last week. Apparently my not posting (combined with not returning phone calls) made my father think I had died. Sorry Dad!

Below is the belated post for Thursday:
I re-ran the 3D auto-correlation function code with courser binning as suggested by Alexia. My result is not that different, although I did figure out how to put axes labels and a legend on my plots, so all was not lost!



The numbers in the legend represent the lower edge of the line-of-sight bin of the spectroscopic data in the 3D auto-correlation function in Mpc. So for instance the yellow line is a bin from 0-200 Mpc, the redline is from 600-800 Mpc etc.

I installed Google Analytics on this blog. Apparently my fan base is mostly Berkeley (5 visits -- probably mostly myself?) followed by New York (3 visits -- Demetri? Kathryn?). Unfortunately no visits from Princeton which means Alexia isn't reading this. Ha ha, busted!

Next step is to try calculating the 3D correlation function on a fake data set and comparing it to the known answer to make sure this isn't a bug in my code.