search

SeismicData / pyasdf

Python Interface to ASDF based on ObsPy
http://seismicdata.github.io/pyasdf/
BSD 3-Clause "New" or "Revised" License
53 stars 30 forks source link

Put all the packages together #37

Closed wjlei1990 closed 7 years ago

wjlei1990 commented 7 years ago

Hi Lion,

There are some people want to use our tools, including pyflex, pyadjoint, pytomo3d, pyasdf and so on. I am thinking about moving all these packages to one place so people could easily find those resource at once. What do you think about it? If so, what kind of "one place" would be suitable?

Because now all the packages are more or less hosting in quite a few of places, when I introduce these tools to people, they get confused.

@mpbl

krischer commented 7 years ago

Hey Wenjie,

pyasdf and pyflex are on pypi so people can just install these with pip install X. pyasdf is additionally on conda-forge so conda install -c conda-forge pyadsf works as well. If you package up your other packages in the same manner it should be easy to install for everyone. Thus most packages can just be treated as external dependencies and they are "tied" together by using pip or conda which people need to do in any case for the other dependent modules. Additionally you could create a web site/wiki that documents the inversion workflow and how to to install the necessary pieces.

Also the use of pyadsf is not only for FWI so I would prefer if it stays in this github organization where all the ASDF things are collected.

Cheers!

mpbl commented 7 years ago

Hi, Lion,

I guess the issue Wenjie is raising is that the python packages we are using and that rely on pyasdf/pyflex are spread among different people’s github accounts. To ensure a coherent façade, it might me good to gather these pacakges in some place; especially if they are under grad. students’ github repos ---as they tend to leave for another job at some point.

The idea is to mimic what you’ve done for https://github.com/SeismicData, bringing various tools under one umbrella. Where we’d like to have your input is if you think if makes sense to add these packages under the SeismicData organization or to create another one. From your previous answer, my guess is you’d rather go with the latter option. Can you confirm?

Cheers.

krischer commented 7 years ago

Hi Matthieu,

I see. I guess a princeton-seismology group might be useful for that purpose - I don't think it would fit into the SeismicData organization.

We also own the seismology Github group (http://github.com/seismology) but not a lot is under it as of now. You would be welcome to join the group.

Cheers!

Lion

mpbl commented 7 years ago

Hi, Lion,

Thanks for your advices. After talking among us, we'll go with computational-seismology.

Cheers! Matthieu