C2-Blueberry Data Downloads
C2 Blueberry Data Data Start - Data Stop Array IDs Present
C2JULY2000.CSV 1999,209,1400 - 2000,208,1600
C2OCT99.DAT 1999,209,1400 - 1999,275,1900
BLUE.DAT 2001,97,1400 - 2001,137,600
C20401.DAT 2001,9,500 - 2001,97,1300
C2102701.DAT 2000,229,1200 - 2000,301,1200
COUN2001.DAT 2000,256,1500 - 2000,301,1200
COUN2002.DAT JUST: 2000,301,1300
COUNT2003.DAT 2000,301,1400 - 2001,27,1400
BLUEBERR.DAT 2001,97,140 - 2001,281,1900
BLUEBR01.DAT 2001,192,1200 - 2001,229,1200
BBDATA1999.XLS 1999,209,1500 - 1999,365,2400
BBDATA2000.XLS 2000,1,300 - 2000,366,2400
BBDATA2001.XLS 2001,1,300 - 2001,281,900
bluedat.txt 2001,277,600 - 2001,297,1900
Blueberry_2005-06-05-a1.dat 2002,70,1700 - 2005,156,2100
Blueberry_2005-07-28-a1.dat 2005,156,2200 - 2005,209,2200 131,230
C2_final_storage_1.dat 2002,231,2400 - 2006,227,1100 130,131,230
C2_2006-10-06.dat 2006,227,1200 - 2006,279,1700 131,230
C2_2007-06-09.dat 2006,279,1800 - 2007,160,1800 131,230
C2_2007-07-26.dat 2007,160,1900 - 2007,207,1100 167,168,230
C2_2008-06-13.dat 2007,207,1200 - 2008,25,2400 168,230
C2_2008-08-26.dat 2008,165,1500 - 2008,239,1900 179,191,237 (still alpha thermistors for thermistor string)
c2_blueberry_2009_08_05.dat 2008,239,1900 - 2009,217,1200 179,191,237 (ysi thermistors for thermistor string)
c2_blueberry_2009_09_27.dat 2009,217,1300 - 2009,270,1000 179,196,237
C2_2010_06_26.dat 2009,217,1200 - 2010,177,2100 179,196,237
C2_2010_08_10.dat 2009,270,1100 - 2010,222,1900 179,196.237
c2_blueberry_2011_08_16.dat 2010,222,2100 - 2011,228,1800 179,182,196,238
c2_blueberry_2012_08_06.dat 2010,282,1500 - 2012,219,1700 179,182,238,196,250
c2_blueberry_2012_radio-only_gap.dat 2012,219,1800 - 2012,288,600 182,238,250
c2_blueberry_2014_07_24.dat 2012,288,600 - 2014,205,1200 182,238,250
c2_blueberry_2014_radio-only_gap.dat 2014,205,100 - 2014,269,2400 182,238,250
c2_blueberry_2016_08_18.dat 2014,249,400 - 2016,231,1000 182,238,250
SHAND RECORD 2001,365,2400 - PRESENT
Ralph now carries out the duties of Shand.
Legit Gaps: 2003 82 2100 to 2003 101 1500
2002 168 2100 to 2002 217 1800
2002 97 900 to 2002 97 1500
2008 26 0000 to 2008 165 1400 (dead battery)
2010 222 2000 (station maintenance)
2014 0124 0200 to 2014 0206 1200 (low battery voltage. There are a few data points in that period, but spotty)
2015 8/24 15:00 -- After shand.engr shut down there is some major funkyness going down with the clock (see note below)
I think this will only be resolved with a site visit.
Incomplete Array ID Identification:
130 = 23 elements, Met 131 = 24 elements, Met 168 = 30 elements, Met 179 = 29 elements, Met 182 = 29 elements, Met 191 = 5 elements, Snow 191 = 7 elements, Snow 196 = 4 elements, Snow 250 = 4 elements, Snow 230 - 22, Soil 230 - 23, Soil 237 - 24, Soil 238 = 25, Soil
==============================================================
Just generally, in the fall of 2009 the Incoming shortwave radiometer wires at the radiation stand become loose. There are some garbage values interspersed that fall that I got tired of cleaning up. Primarily mid October to Mid December. Maybe all of that data should just be zeroed out.
Fall 2015 to Spring 2016
In August 2015 shand.engr.uaf.edu was shut down. Shand had been the remote data retrieval computer from 2002 to 2015. Over the fall of 2015 we had a number of issues transitioning away from shand. It quickly became obvious that LoggerNet could not consistently retrieve data from the tenuous radio links on the SP. I moved the most recent version of Loggerdata.pl to host lognet so that we could take advantage of the older, more stable data retrieval software on the new computer. However, it turns out that there is a major bug specific to CentOS, the operating system running on LogNet. The time zone of the logger specified in the configuration files used by Loggerdata.pl was ignored on centOS so August 2015 to early January 2016 there was some fighting back and forth with the two competing data retrieval programs. I inadvertently fixed this by disabling loggerdata downloads for this site in late December / early January. However, due to poor performance I re-enabled again in March to try to get the sites caught up before our April trip. Around then I figured out the timezone bug present when running things on LogNet / CentOS. So, data retrievals were moved to host Ralph which is a debian OS based computer. Downloading became more consistent at that point and I'm not sure why we haven't heard from the Council sites since early May but could be a bear again. But, in light of this there is quite a bit of data in the Blueberry hill data stream with a mix of timezone (UTC vs Ak Standard at UTC-9hrs). It is only apparent which time zone the data is in if you look at the incoming shortwave radiation data and so I thought I would create this section to delineate as best I can tell. Definitely a bit of an own goal...
Station origination to
"2015-08-24 15:00:00" AKSTD
"2015-08-24 01:00:00" UTC
"2015-08-25 01:00:00" AKSTD
"2015-08-25 00:00:00" From here till the next several months, a low value @ 0:00 or 1:00 = AKSTD, a high value = UTC
If that makes any sense.
Like this sampler:
"2015-09-02 00:00:00",0.00 (AKSTD)
"2015-09-02 00:00:00",0.00 (AKSTD)
"2015-09-02 00:00:00",0.00 (AKSTD)
"2015-09-02 01:00:00",0.00 (AKSTD)
"2015-09-02 01:00:00",11.24 (AKSTD)
"2015-09-02 00:00:00",126.00 (UTC)
"2015-09-02 01:00:00",147.70 (UTC)
"2015-09-02 01:00:00",128.10 (UTC)
"2015-09-02 01:00:00",54.21 (UTC)
"2015-09-02 00:00:00",9.77 (AKSTD)
"2015-09-02 01:00:00",0.07 (AKSTD)
"2015-12-20 00:00:00" UTC
"2015-12-29 00:00:00" AKSTD
"2016-03-28 18:00:00" UTC
"2016-03-29 17:00:00" AKSTD
"2016-03-30 00:00:00" UTC
"2016-03-30 16:00:00" AKSTD
