Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data units: radians, strain, micro-strain, or nano-strain #6

Open
andreas-wuestefeld opened this issue Nov 3, 2022 · 2 comments
Open

Comments

@andreas-wuestefeld
Copy link
Collaborator

Does anyone has opinions (and arguments) for or against using as native unit

  • radians
  • strain
  • micro-strain
  • nano-strain
  • ...

As geophysicist I prefer physical units. Using radians also requires the introduction of another header value for the scaling.
units other than strain [m/m] may allow going for lower-precission formats of the data matrix

@gloverha
Copy link

gloverha commented Nov 7, 2022

One bit of info that might be necessary is the original unit for data collection. Some instruments output phase and others provide phase rate. We've been exploring how phase v phase rate impacts channel fading. So, it seems like important info to include in metadata.

@andreas-wuestefeld
Copy link
Collaborator Author

Thanks gloverha
The latest iteration of the format actually incorporates that idea. a new required header field describes the unit of the data on disk.
An additional scale factor is also provided, with a new unit-string after conversion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants