Comments (3)
I agree with time delay filters being applied directly to the time series.
Scalars could be either domain. I guess in general most people will be be using calibrated transfer functions, but maybe for plotting they would want calibrated data, in which case we can have a function calibrate
or something to visualize calibrated data.
from mt_metadata.
Committed a change to address this.
The remaining issue is potentially encountering filters that have a time delay, and a non-flat frequency response. If we encounter such a filter it will not play nice.
I put a note in the Friday Discussion page to ask Tim about examples of these filters...
The only type of Stage in the StationXML reference document that has a is the Decimation Stage. However the decimation stage does not have a way to describe a non-trivial frequency response. This seems not quite right, as decimation should have an anti-alias filter applied. It could be that they factor the digital decimations into a FIR/IIR stage and then add the "decimation time delay" as a separate stage, but what they really mean is "downsample after IR" rather than "decimation".
Pending that discussion we can close this issue.
from mt_metadata.
The only StationXML stage that has a delay is the decimation stage. It does not have a mechanism to apply a variable frequency response. So we should in general be able to separate time delays from all other types of stages.
from mt_metadata.
Related Issues (20)
- List of next level objects should become an OrderedDict HOT 1
- Should Auxiliary channels require component field? HOT 1
- Make validation more efficient
- MTime does not support nanoseconds
- pandas Timestamp does not support years greater than 2600 or so
- remove aurora dependencies from processing config HOT 2
- Aurora not passing since merge HOT 1
- No attribute period error HOT 2
- Replace ListDict with Box
- TF instance has different values for self.transfer_function and self.dataset.transfer_function HOT 1
- TF XML Ingest HOT 13
- Z-file headers HOT 3
- write/read tf broken by "comments" HOT 1
- Add mt_metadata version in summary of metadata standards.
- TF should use SurveyMetadata as sole metadata object
- time and frequency axes are permuted in FC HOT 2
- Use Loguru for logging
- dataless mth5 from fdsn HOT 16
- python 3.7 install failing on fcs branch HOT 1
- Exceptions when reading tf in emtfxml format HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mt_metadata.