You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tricky one. In the beginning we wanted people to come from pandas to xarray. It was kind of assumed that everybody uses and loves pandas, therefore will also use and love xarray. (my own experience).
But do we have to build the docs for non-pandas users as well? It could make quite a few things redundant with the pandas documentation...
But do we have to build the docs for non-pandas users as well? It could make quite a few things redundant with the pandas documentation...
I personally think we should. I think there are a very large number of numpy users who don't use pandas or any labelled data libraries at all, who cannot be assumed to know what Pandas does. I definitely didn't understand what the references to Pandas meant when I first read xarray's documentation, and everyone else in my field seems to fit in this category at least...
A relatively new user here gave me an incomplete list of things they found to be confusing in the docs:
What is xarray's data model?opened Document xarray data model #2913What is split-apply-combine?
What are dummy dimensions and
np.newaxis
quick-overiew: Index so that you extract a subset!
too many references to pandas!
do I need to know pandas to use xarray?
what is the difference between attrs and encoding? How do I use them properly/correctly?
why
isnull
anddropna
: whydropna
instead ofdropnull
compute
docstring doesn't mention computation!compute vs persist vs load: what's the difference
do I get parallelization for free?
I'm crossing out things that I've started to fix.
The text was updated successfully, but these errors were encountered: