# Meta file time stamp

**URL:** <https://www.ruby-forum.com/t/meta-file-time-stamp/243231>\
**Category:** GNU Radio\
**Created:** [September 2, 2015, 9:52pm UTC](https://www.ruby-forum.com/t/meta-file-time-stamp/243231 "2015-09-02T21:52:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sadaf\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/858c86/32.png) [@Sadaf\_N](https://www.ruby-forum.com/u/Sadaf_N)\
**Post date:** [September 2, 2015, 9:52pm UTC](https://www.ruby-forum.com/t/meta-file-time-stamp/243231/1 "2015-09-02T21:52:35Z")

</div>

Dear All,

We are experiencing unexpected behavior with the time stamps in the  
meta file headers. It  
appears that in cases where the flowgraph experiences data drops, the  
timestamp is properly  
updated. However, in cases, where the flowgraph hits the maximum  
segment size (4 MB in our case),  
the calculation of timestamp is done in such a way that appears to  
neglect a decimation factor  
in one of our blocks (keep\_1\_in\_n). Details can be found below.  
Any suggestions as to what’s  
going on or what to do about it would be most appreciated.

Sincerely,  
Dan Marlow

Details:

OS: Ubuntu 15.04 (GNU/Linux 3.19.0-26-generic x86\_64)

H/W: Ettus B210 with GPSDO,  
Intel® Core™ i5-4430 CPU @ 3.00GHz 8GB memory USB3

gnuradio: 3.7.8

Flowgraph: This is provided to give an idea of what we are doing. It  
is close to what we  
are using, but not exact, since we edited the  
output generated by GRC.