[IGSREPORT-23957] Something is not right with gfz18646 Final clock file

[Kevin Choi - NOAA Federal]

Dear GFZ AC colleagues,

During the IGS Final combination for wk1864, the orbit combination was completed but the clock combination was failed with somewhat bogus message as below.

BRDC-ALIGNMENT
--------------

 CEN |    OFFSET     DRIFT     CLKRMS
     |     (ns)      (ns/d)     (ns) 
 ----+-------------------------------
 cod |    -0.819    -0.206     3.277
 emr |     4.147     0.135     3.267
 esa |    -0.718    -0.058     3.223
 gfz |   -10.060    30.044     3.321
 grg |     0.419    -0.533     3.285
 mit |     3.073     0.605     3.367



 *** PG CCLOCK: MAXEPO EXCEEDED 
                FILE        :                         COMBINED
                EXPECTED MAX:   2880 
                DETECTED MAX:   2881 

It was really puzzling so I had to spend a good amount of hours to track it down.  I still don’t know the exact spot but it must come from gfz clock file.  The BRDC-ALIGNMENT for the day 5 (below) was very small for gfz but for day 6 (above) the numbers are quite big.  


BRDC-ALIGNMENT
--------------

 CEN |    OFFSET     DRIFT     CLKRMS
     |     (ns)      (ns/d)     (ns)
 ----+-------------------------------
 cod |    -0.760    -0.327     3.279
 emr |     3.149     1.001     3.277
 esa |    -0.279     1.503     3.240
 gfz |     0.084    -0.019     3.302
 grg |     0.223     0.069     3.324
 mit |     1.237     1.704     3.367


When I exclude gfz clocks, the clock combination finished without any issue.  If you can track it down and provide the new clock file with identical station coordinates (SINEX submission), I can use your new clock file, but if the station coordinate has to be changed, then we need to discuss how to handle this case.

It would be great if you can reply me with your plan since we can’t delay the Final product too long.

Thanks,

Kevin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.igs.org/pipermail/igsreport/attachments/20151018/4e7b2a8a/attachment.html>