-
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @jojomale sorry just found this discussion. noisepy-io was previously part of noisepy main package, until we found that several basic IO operations (e.g., reading the stacked correlation, plotting, etc.) don't really need the entire noisepy dependencies. However, in order to use noisepy as a single package, we still need to all dependencies. That's why we decided to make the IO part a separate package: small with very few dependencies. We also expect that people only change the IO part when working on different data, leaving the main package untouched. noisepy-io is now a dependent of noisepy, which is why it is automatically installed through PyPI. However, since it shares the same name space with noisepy (noisepy.seis), this makes developing a little bit different. After cloning the noisepy repo, I usually do Best, |
Beta Was this translation helpful? Give feedback.
Hi @jojomale sorry just found this discussion.
noisepy-io was previously part of noisepy main package, until we found that several basic IO operations (e.g., reading the stacked correlation, plotting, etc.) don't really need the entire noisepy dependencies. However, in order to use noisepy as a single package, we still need to all dependencies. That's why we decided to make the IO part a separate package: small with very few dependencies. We also expect that people only change the IO part when working on different data, leaving the main package untouched.
noisepy-io is now a dependent of noisepy, which is why it is automatically installed through PyPI. However, since it shares the same na…