Not much activity since snow has stopped tower and station work.

flux: Okay

tower: se sonics, TRHs, and DSMs fine.  50m nw sonic dead (need to check connector and possibly replace), 100m nw sonic is good, other nw sonics not mounted yet.

bao: Okay except EC150 which sends intermittently bad data.  Suspect that the terminal block screws inside EC100 box need to be tightened.  Other possibilities are the bulgin cable or the EC100 box itself, but the box was tested in the lab.

ehs: Have verbal permission for a site, but may need written permission.  Waiting for this decision (and snow) before deploying.  Kurt spent today preparing (which involves a few physical and cable changes to make a "cleaner" installation).

www: Created dat.Theta and dat.P on EOL servers.  List of www plots to generate is on Rudy's office marker board.  Julie is desperate for wind direction plots!

 

 

  • No labels

5 Comments

  1. Will PIs want all quantities (u,v,w,tc,dir,spd, covars) from an artificial 3d sonic at each level on the tower, where values from the nw or se sonic are used depending which has the best orientation w.r.t. the current wind direction?  Or is that their responsibility?

    As of 2/28, derived Dir and dir are being created in near real-time by R on flab systems.  statsproc is no longer averaging Dir.

  2. Steve Oncley AUTHOR

    Good question.  Certainly, this is needed.  I would say that it is their responsibility (and they'll have to do this with their own sonics eventually), but if you thought it would be trivial for us to do...

    Thanks for dir/Dir...Steve

     

  3. I agree that, once the nw sonics are up, it is our (Julie and Jim's) responsibility to decide which sonic to be used based on the wind direction.

    And thank you so much for adding dir to the list of available data. I'll use it in class on Tuesday.

    Cheers, Julie

  4. Also, noticed that 50m T/RH disappeared for several hours this weekend (starting 1600 UTC 28 Feb). Any ideas why?

  5. Steve Oncley AUTHOR

    The 50m TRH fan is reporting current consumption that is low.  Although the sensor is running and data are being saved, our software (correctly) flags these low currents by deleting the temperature data.  We haven't seen this type of failure before, but I am guessing that the fan blade has broken off of the motor shaft.  I have confirmed that the fan is not working properly by comparing T and tc and see daytime differences of more than 5C (100m has a constant offset of ~1C).  This sensor has been this way since it was deployed – the very first Ifan reading was 9mA.

    This sensor needs to be replaced as well.  NOAA should have a spare.