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

[HELP] What cause the "No data for xxx" in lag_calc #602

Open
zhong-yy opened this issue Jan 3, 2025 · 1 comment
Open

[HELP] What cause the "No data for xxx" in lag_calc #602

zhong-yy opened this issue Jan 3, 2025 · 1 comment

Comments

@zhong-yy
Copy link

zhong-yy commented Jan 3, 2025

What do you need help with?

lag_calc

Provide an example so that we can reproduce your problem

Not ready yet

What help would you like?

What cause the "No data for xxx" problem (e.g. No data for 2022_09_20t01_36_59_20150225_204411380000) in lag_calc ?

I guess it is because of gaps, but why is the data available for detect but not for lag_calc?

What is your setup? (please complete the following information):**

  • Operating System: Ubuntu 24.04
  • Python version: 3.10
  • EQcorrscan version: 0.5.dev
@calum-chamberlain
Copy link
Member

This is usually caused by seed-id naming issues. Lag-calc is more strict about matching full seed ids than detect is. If this is the issue you should have had a warning from this line though. Without a useful example and explicit outputs it is near impossible to say what the issue is.

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