I had an issue with the wiper script on h1ldasgw1 (it was not running) which meant that new /frames-1 eventually became 100% full having been running since 2nd November. I have started the wiper and h1fw1 is writing frame files again.
This means that the default NDS (h1nds1) has no full or second trend data during the data gap. These data can be obtained by changing your NDS to h1nds0, which has no data gap.
Minute trend data (acquired by h1tw1) was unaffected by this.
The data gap on h1fw1 is:
| GPS | UTC | PST | |
| start of gap | 1196988928 | Mon Dec 11 00:55 | Sun Dec 10 16:55 |
| end of gap | 1197052224 | Mon Dec 11 18:30 | Mon Dec 11 10:30 |