Hi,
I would like to know if the database schema for mustang metrics is available. I am using some of the metrics and I am writing my own schema to download the data but it would be easier I can use the schema you are using.
Regards
Omar E. Marcillo
EES-17, Geophysics Group
Los Alamos National Laboratory
Los Alamos, NM 87545
Phone:(505) 606 0192
Email: omarcillo<at>lanl.gov<omarcillo<at>lanl.gov>
Mailing address:
P.O. Box 1663
MS D446
Los Alamos, NM 87545
I would like to know if the database schema for mustang metrics is available. I am using some of the metrics and I am writing my own schema to download the data but it would be easier I can use the schema you are using.
Regards
Omar E. Marcillo
EES-17, Geophysics Group
Los Alamos National Laboratory
Los Alamos, NM 87545
Phone:(505) 606 0192
Email: omarcillo<at>lanl.gov<omarcillo<at>lanl.gov>
Mailing address:
P.O. Box 1663
MS D446
Los Alamos, NM 87545
-
Hi Omar-
Thanks for your interest in MUSTANG. We are generally reluctant to release our schemas and code for the MUSTANG system as it is pretty extensive when you get down into the details. It is also for security considerations.
In general terms, we maintain a table with unique 'target' names, such as IU.ANMO.00.BHZ.M, which are referenced from the metric value tables, one table per metric, that contains the fields you see in the MUSTANG output. The target ID is a foreign key from the metric value table to the 'target' table, so when considering from this level, it's not terribly complicated. You could certainly create a capture schema based on this simple model.
-Rob
-
Hi Omar-
I also forgot to mention that you can get a metric summary that is schema-like by using our 'metrics' metadata service:
Default HTML output: http://service.iris.edu/mustang/metrics/1/query
XML output: http://service.iris.edu/mustang/metrics/1/query?output=xml
XSD output: http://service.iris.edu/mustang/metrics/1/query?output=xsd
-Rob
On Apr 10, 2017, at 12:39 PM, Rob Casey <rob<at>iris.washington.edu> wrote:
Hi Omar-
Thanks for your interest in MUSTANG. We are generally reluctant to release our schemas and code for the MUSTANG system as it is pretty extensive when you get down into the details. It is also for security considerations.
In general terms, we maintain a table with unique 'target' names, such as IU.ANMO.00.BHZ.M, which are referenced from the metric value tables, one table per metric, that contains the fields you see in the MUSTANG output. The target ID is a foreign key from the metric value table to the 'target' table, so when considering from this level, it's not terribly complicated. You could certainly create a capture schema based on this simple model.
-Rob
----------------------
MUSTANG QA (http://ds.iris.edu/message-center/topic/mustang-qa/)
Sent from the IRIS Message Center (http://ds.iris.edu/message-center/)
Update subscription preferences at http://ds.iris.edu/account/profile/
-