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

[FEATURE] Look for ways to have SmartSolo pickup behave like Fairfield pickup #516

Open
hrotman-pic opened this issue Feb 21, 2023 · 0 comments

Comments

@hrotman-pic
Copy link
Collaborator

hrotman-pic commented Feb 21, 2023

This issue is being opened following internal discussions at PIC (nodes, data).

Is your feature request related to a problem? Please describe.
SmartSolo pickup time currently goes out to the end of zero-padded last trace window in the last file for any given DAS. This is ideal for not having undescribed data in the archive, but the PIC data group has found this leads to requiring significant array table modification to create correct and valid metadata when SmartSolos are used in multiple deployment experiments. The array table modification represents additional steps in PH5 archiving that may be burdensome or confusing to beginning users or community members and the PIC data group has judged the time required not scalable to larger experiments even for expert PH5 users.

Describe the solution you'd like
-If node turn off time is in SmartSolo headers, use that to populate pickup time (may be similar to Fairfield handling). Node end time is available in .txt and .xml files requested from SmartSolo software and it is unclear if this information is populated in the headers.
-Or, if a file ends before 00:00:00 (not a full SEGD day volume), attempt to determine where zero-padded data starts and use that timestamp as the pickup time.

Describe alternatives you've considered
-Manual array table modification was used for the cases encountered thus far and is an option for small experiments.
-Requesting changes from the manufacturer to make headers more optimal may be an option.

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

No branches or pull requests

1 participant