how to make a dataless seed file?

[Heinz-Bernd Eggenstein]

I understand that for some software, e.g. WinQuake, it's useful to have  a "dataless" SEED file that contains some metadata about my station that is not included in miniseed files.

I also think that the necessary info is included in the file you can download from your station's popup window in the stationview GUI. But that file is in XML and understood by the seiscomp software.

Ok, fair enough, I downloaded SeisComP (to another Raspberry Pi), found a program inv2dlsv there, and used it to produce a new file:

inv2dlsv file-from-stationview.xml mystation.dataless 

But when I'm trying to import the resulting file into WinQuake (File->MINISEED Control->Add Header Information) , it still complains about a SEED parsing error (no details given). 
So obviously I'm missing something.

Any ideas?

THX
HB

[Branden Christensen]

HB:

Seriously NICE progress. That is independence at its best. 

Let's see what Larry says about WinQuake not reading the dlsv produced by the inv2dlsv routine. Can you send it along with a miniSEED snippet so Larry can try it himself?

Yours, 

Branden Christensen

Director, OSOP & Gempa GeoServices

USA: +1-206-414-1288; Panamá: +507-6747-1427

Get yours now! Visit shop.raspberryshake.org

--
Some useful links:
 
Manual: http://manual.raspberryshake.org/
Do It YourSelf Page: http://raspberryshake.org/do-it-yourself
Shop: https://shop.raspberryshake.org/
Website: http://raspberryshake.org/
 
Instagram: https://www.instagram.com/raspberryshake/
Hashtag: #rasperryshake
---
You received this message because you are subscribed to the Google Groups "RaspberryShake" group.
To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshake+unsubscribe@googlegroups.com.
To post to this group, send email to raspberryshake@googlegroups.com.
Visit this group at https://groups.google.com/group/raspberryshake.
To view this discussion on the web visit https://groups.google.com/d/msgid/raspberryshake/fa75331d-1475-4411-abf2-52fb4ab95255%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Heinz-Bernd Eggenstein]

Sure, see attachments.
THX
HB

To unsubscribe from this group and stop receiving emails from it, send an email to raspberryshak...@googlegroups.com.
To post to this group, send email to raspber...@googlegroups.com.

[Larry Cochrane]

Hi HB,

WinQuake can not read dataless miniseed files only miniseed files with data. You can addition information about the 
channel in the sensor.dat file.

Regards,
Larry Cochrane
Redwood City, PSN
http://www.seismicnet.com 

[Juan Antonio]

Hello 

I think you can create dataless miniseed files with this software

http://ds.iris.edu/ds/nodes/dmc/software/downloads/pdcc/

Regards 

Juan Antonio

[Heinz-Bernd Eggenstein]

Thanks all, I will try the suggested solutions.

Cheers
HB

[Juan Antonio]

Please find attached my RS file, if you want to use as template

Regards

[Heinz-Bernd Eggenstein]

Thanks, that was convenient. I modified the station code and geo-coordinates and voila, the modified file loaded successfully in WinQuake!

THX
HB

[Juan Antonio]

Thanks to Tycho Aussien too, he taught me that several weeks ago.  

Regards

Juan Antonio.  

[Heinz-Bernd Eggenstein]

I can now get station coordinates into WinQuake via dataless SEED (not miniseed) files but I think I found two problems:

a) WinQuake crashes when one of these dataless files is stored in a directory from which you want to load event data files, e.g. mseed files. I guess the reason is that something goes wrong when WinQuake tries to read metadata to display in the custom file-chooser

b) after getting the RShake calibration info into Winshake, the sensor information dialog indicates a value of 2.1322e-011 cm per A/D bit.  SInce the sensor type is accurately set to "velocity", I guess this should read "cm/s per A/D count". The bigger problem seems to be the value itself: the dataless file includes the calibration value from the RaspberryShake spec, which is 4.69118E+08 counts per m/s. That would then be 4.69118E+06 counts per cm/s, or   2.1317e-07 cm/s per count. So somehow the sensor settings value is off by a factor of 1E-4, probably by correcting for cm to m in the wrong direction. Thee value can be corrected manually in the sensor settings dialog, tho.

Is there a way to file bug reports for WinQuake? Should I do it via the contact form at http://www.seismicnet.com/contact.html   ?
Cheers
HB