Hi Chad,
I have few questions about the intended usage of the variable record
length. Would SeedLink (assuming that it would be based on mseed3) send
variable length records (fixed maximum latency)? Dataselect? And would
slarchive create SDS with variable length records?
Random access (eg., binary search as used by dataselect working on top
of SDS) in files with variable record length would probably require
separate index files or some heuristics (incl. CRC check?) to determine
record start, or the 'MS3' record signature must be escaped if it
appears within binary data.
Is mseed3 at all envisioned to be a real-time format or an archive
format only?
Regards,
Andres.
On 08/12/2016 02:40 AM, Chad Trabant wrote:
Hi all,
Change proposal #24 to the 2016-3-30 straw man (iteration 1) is
attached: Change variable record length field to 16 bits.
Please use this thread to provide your feedback on this proposal by
*Wednesday August 24th*.
thanks,
Chad
----------------------
Posted to multiple topics:
FDSN Working Group II (http://www.fdsn.org/message-center/topic/fdsn-wg2-data/)
FDSN Working Group III (http://www.fdsn.org/message-center/topic/fdsn-wg3-products/)
Sent via IRIS Message Center (http://www.fdsn.org/message-center/)
Update subscription preferences at http://www.fdsn.org/account/profile/