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

Allow import/export completely custom SEG-Y via spec override environment variable #440

Merged
merged 3 commits into from
Sep 26, 2024

Conversation

tasansal
Copy link
Collaborator

There are some edge cases (i.e. custom header definitions out of spec) when default MDIO SEG-Y spec doesn't unpack some values into JSON and if it is exported, the data will be lost.

In those cases we can give a full SEG-Y spec based on the TGSAI/segy schema as a JSON environment variable: MDIO__SEGY__SPEC.

As long as the user has the JSON available at runtime; MDIO should be able to ingest/export files conforming to that spec.

IMPORTANT: Re-emphasizing that the files ingested with a custom JSON spec will ONLY be exportable if the spec is available. Or else default MDIO can't export it since it will be out of spec.

@tasansal tasansal added the enhancement New feature or request label Sep 26, 2024
@tasansal tasansal self-assigned this Sep 26, 2024
@tasansal tasansal merged commit a663aca into main Sep 26, 2024
20 checks passed
@tasansal tasansal deleted the require-newer-segy branch September 26, 2024 21:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant