40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Tue Apr 17 11:05:04 2012, Jamie, Update, CDS, CDS upgrade in progress 
    Reply  Tue Apr 17 19:03:09 2012, Jamie, Update, CDS, CDS upgrade in progress 
       Reply  Wed Apr 18 19:59:48 2012, Jamie, Update, CDS, CDS upgrade success 
          Reply  Fri Apr 20 19:54:57 2012, Jamie, Update, CDS, CDS upgrade problems 
             Reply  Sat Apr 21 17:38:19 2012, Jamie, Update, CDS, dtt, dataviewer working; problem with trend frames 
                Reply  Sat Apr 21 21:10:34 2012, Jamie, Update, CDS, trend frame issue partially resolved 
                   Reply  Tue Apr 24 14:35:37 2012, Jamie, Update, CDS, limited second trend lookback 
             Reply  Sat Apr 21 20:40:28 2012, Jamie, Update, CDS, framebuilder frame writing working again 
          Reply  Tue Apr 24 14:55:00 2012, Jamie, Update, CDS, cds code paths (rtscore, userapps) have moved 
Message ID: 6556     Entry time: Sat Apr 21 21:10:34 2012     In reply to: 6554     Reply to this: 6561
Author: Jamie 
Type: Update 
Category: CDS 
Subject: trend frame issue partially resolved 

Quote:

Unfortunately it looks like there may be a problem with trend data, though.  If I try to retrieve 1 minute of "full data" with dataviewer for channel C1:SUS-ITMX_SUSPOS_IN1_DQ around GPS 1019089138 everything works fine:

Connecting to NDS Server fb (TCP port 8088)
Connecting.... done
T0=12-04-01-00-17-45; Length=60 (s)
60 seconds of data displayed

but if I specify any trend data (second, minute, etc.) I get the following:

Connecting to NDS Server fb (TCP port 8088)
Connecting.... done
Server error 18: trend data is not available
datasrv: DataWriteTrend failed in daq_send().
T0=12-04-01-00-17-45; Length=60 (s)
No data output.

Alex warned me that this might have happened when I was trying to test the new daqd without first turning off frame writing.

Alex told me that the "trend data is not available" message comes from the "trender" functionality not being enabled in daqd.  After re-enabling it (see #6555) minute trend data was available again.  However, there still seems to be an issue with second trends.  When I try to retrieve second trend data from dataviewer for which minute trend data *is* available I get the following error message:

Connecting to NDS Server fb (TCP port 8088)
Connecting.... done
No data found

read(); errno=9
read(); errno=9
T0=12-04-04-02-14-29; Length=3600 (s)
No data output.

Awaiting more help from Alex...

ELOG V3.1.3-