issues

What is your issue?

I'm trying to produce a facet plot which contains maps with different overlaid layers (e.g. a pcolormesh and streamplot). At the moment I'm creating the plot and then iterating over the axes to add the plots manuallay

```python p = dss['LH'].plot.pcolormesh( x='lon', y='lat', col="exp", )

for i, ax in enumerate(p.axes.flat): ax.coastlines() ax.streamplot( dss.isel(exp=i).lon.values, dss.isel(exp=i).lat.values, dss.isel(exp=i)['u_10m_gr'].values, dss.isel(exp=i)['v_10m_gr'].values, ) ```

This is far from optimal and doesn't really look clean to me. Also, I'm not entirely sure the order of p.axes.flat correspond to the one of the exp dimension I'm using to facet.

All examples in the doc (https://docs.xarray.dev/en/stable/user-guide/plotting.html) refer to the plot method of DataArray, so it seems that, once created the p object, no other variable from the dataset can be accessed.

However, on the doc it is mentioned

TODO: add an example of using the map method to plot dataset variables (e.g., with plt.quiver).

It is not clear to me whether the xarray.plot.FacetGrid.map method can indeed be used to plot another dataset variable or not. If that's not the case, is there any way to achieve what I'm doing without manually looping through the axes?

Code Sample

Unfortunately I cannot include the original data, as it is quite large, but I can make an accessible dropbox folder if needed.

```python debug = False if not debug: import matplotlib matplotlib.use('Agg')

import matplotlib.pyplot as plt import xarray as xr import metpy.calc as mpcalc from metpy.units import units from glob import glob import numpy as np import pandas as pd from multiprocessing import Pool from functools import partial import os from utils import * import sys

variable_name = 'cape_cin' projections = ['de','it','nord']

def main(): """In the main function we basically read the files and prepare the variables to be plotted. This is not included in utils.py as it can change from case to case.""" files = glob(input_file) dset = xr.open_mfdataset(files) # Only take hourly data dset = dset.sel(time=pd.date_range(dset.time[0].values, dset.time[-1].values, freq='H')) # Parse metadata for metpy dset = dset.metpy.parse_cf() # Select variable cape = dset['CAPE_ML'].squeeze().load()

# Get coordinates
lon, lat = get_coordinates(dset)
lon2d, lat2d = np.meshgrid(lon, lat)

time = pd.to_datetime(dset.time.values)
cum_hour=np.array((time-time[0]) / pd.Timedelta('1 hour')).astype("int")

levels_cape = np.arange(250., 2000., 250.)

cmap = truncate_colormap(plt.get_cmap('gist_stern_r'), 0., 0.7)

for projection in projections:
    fig = plt.figure(figsize=(figsize_x, figsize_y))
    ax  = plt.gca()        
    m, x, y =get_projection(lon2d, lat2d, projection, labels=True)

    # All the arguments that need to be passed to the plotting function
    args=dict(m=m, x=x, y=y, ax=ax, cmap=cmap,
             cape=cape, levels_cape=levels_cape,
             time=time, projection=projection, cum_hour=cum_hour)

    print('Pre-processing finished, launching plotting scripts')
    if debug:
        plot_files(time[1:2], **args)
    else:
        # Parallelize the plotting by dividing into chunks and processes 
        dates = chunks(time, chunks_size)
        plot_files_param=partial(plot_files, **args)
        p = Pool(processes)
        p.map(plot_files_param, dates)

def plot_files(dates, **args): first = True for date in dates: # Find index in the original array to subset when plotting i = np.argmin(np.abs(date - args['time'])) # Build the name of the output image filename = subfolder_images[args['projection']]+'/'+variable_name+'_%s.png' % args['cum_hour']

    # Do the plot 
    cs = args['ax'].contourf(args['x'], args['y'], args['cape'][i], 
                                             extend='both', cmap=args['cmap'],
                                             levels=args['levels_cape'])

    if first:
        plt.colorbar(cs, orientation='horizontal', label='CAPE [J/kg]', pad=0.03, fraction=0.04)

    if debug:
        plt.show(block=True)
    else:
        plt.savefig(filename, **options_savefig)

    remove_collections([cs, an_fc, an_var, an_run])

    first = False

if name == "main": main() ```

Problem description

My task is to routinely plot output from weather models in an automatized way. The main driver script is written in 'bash' and calls different 'python' scripts at the same time.

Given that the input data is always dimensioned '(time, level, latitude, longitude)' and that I have to do one plot per timestep it seemed natural to me to use multiprocessing to split the load of different time-chunks over different processors. Since I also have to pass some parameters/variables I call the function to do the actual plotting plot_files using the partial constructor plot_files_param=partial(plot_files, **args). This way I can then unpack all the needed parameters/variables in the function itself without needing to declare them as global variables. Note that this is fundamental as, to make everything fast, I only create most of the variables/instances once and then update them at every iteration.

This works fine if I load the input netcdf file with open_dataset, but instead if I use open_mfdataset (as in some case I have many files scattered in a folder) then I have to be careful in explicitly loading the arrays before passing them to the plotting function, otherwise the script will hang.

More specifically. if I remove the .load() statement from this line python cape = dset['CAPE_ML'].squeeze().load() then cape stays a dask array and gets passed as argument to plot_files. Then I was expecting the plot call to load it as array in memory before doing the plot, but this does not happen (I think) and then the script just hangs (does not post any error). Interestingly enough, if I use the option debug = True, which instead of parallelizing the plotting just plot 1 timestep and directly show the output, everything works fine, although the array passed is still a dask array. So, this is definitely something related to the use of the partial construct.

In theory I would like to keep the .load() usage as small as possible as data can be pretty huge and I only want to load it into memory when I have to plot it.

It may well be that my code is somehow malformed but as far as I know this should not be the expected behaviour. Please apologize if I'm doing something wrong; every suggestion is highly appreciated! Thought that I report the error as I found it to be non-expected behaviour.

Expected Output

Array should load into memory when plotting without the need to do it explicitly.

Output of xr.show_versions()

What happened?

I'm trying to merge the following datasets, which have exactly the same coordinates and extents (not sure why it could cause any conflict).

After merging them, with xr.merge([ds, alt]) (the order does not matter), the resulting altitude has NaNs all over the place. I could tell that something wrong was going on because the merge took too long (about 30s, while it should be pretty much instantaneous given the dimensions).

Here is a comparison of the altitude before and after the merge

If I try to create the DataArray manually, that is

python ds['altitude'] = xr.DataArray(data=alt.altitude.values, dims=("lat","lon")) everythign works fine.

What did you expect to happen?

Normal broadcasting rules should apply and the resulting array should not have NaNs.

Minimal Complete Verifiable Example

No response

MVCE confirmation

• [X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
• [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
• [ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
• [ ] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output

No response

Anything else we need to know?

No response

Environment

What happened?

I have a script structured like this

```python def main(): global ds ds = xr.open_dataset(file) for point in points: compute(point)

def compute(point): ds_point = ds.sel(lat=point['latitude'], lon=point['longitude'], method='nearest') print(ds_point.var.mean()) # do something with ds_point and other data...

if name == "main": main() ```

This works as expected. However, if I try to parallelize compute by calling it with

python process_map(compute, points, max_workers=5, chunksize=1)

The results of the print are completely different from the serial example and they change every time that I run the script. it seems that the sel is giving back a different part of the dataset when there are multiple processes running in parallel.

If I move the open_dataset statement inside compute then everything works also in the parallel case in the same way as in the serial one. Also, if I load the dataset at the beginning, i.e. ds = xr.open_dataset(file).load(), I also have reproducible results.

Is this supposed to happen? I really don't understand how.

What did you expect to happen?

The behaviour of sel should be the same in parallel or serial execution.

Minimal Complete Verifiable Example

No response

MVCE confirmation

• [X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
• [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
• [ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
• [ ] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output

No response

Anything else we need to know?

No response

Environment

What happened?

Suppose I have the following dataset

python <xarray.Dataset> Dimensions: (lat: 468, lon: 520, n_stations_t_2m_min_anom: 930) Coordinates: * lon (lon) float64 6.012 6.037 6.062 ... 18.96 18.99 * lat (lat) float64 36.01 36.04 36.06 ... 47.66 47.69 Dimensions without coordinates: n_stations_t_2m_min_anom Data variables: t_2m_min_anom (lat, lon) float32 ... t_2m_min_anom_stations (n_stations_t_2m_min_anom) float64 1.935 ... 0.8557

and a mask to apply

python <xarray.DataArray 'mask' (lat: 468, lon: 520)> array([[False, False, False, ..., False, False, False], [False, False, False, ..., False, False, False], [False, False, False, ..., False, False, False], ..., [False, False, False, ..., False, False, False], [False, False, False, ..., False, False, False], [False, False, False, ..., False, False, False]]) Coordinates: * lat (lat) float64 36.01 36.04 36.06 36.09 ... 47.61 47.64 47.66 47.69 * lon (lon) float64 6.012 6.037 6.062 6.087 ... 18.91 18.94 18.96 18.99

If I apply the mask to the dataset doing

python data = data.where(mask)

then lat, lon dimensions are also broadcasted to t_2m_min_anom_stations, which is a 1-D array that does NOT have these coordinates.

python <xarray.Dataset> Dimensions: (lat: 468, lon: 520, n_stations_t_2m_min_anom: 930) Coordinates: * lon (lon) float64 6.012 6.037 6.062 ... 18.96 18.99 * lat (lat) float64 36.01 36.04 36.06 ... 47.66 47.69 region int64 0 abbrevs <U2 'r0' names <U7 'Region0' Dimensions without coordinates: n_stations_t_2m_min_anom Data variables: t_2m_min_anom (lat, lon) float32 nan nan nan nan ... nan nan nan t_2m_min_anom_stations (n_stations_t_2m_min_anom, lat, lon) float64 nan ...

This causes all sort of issues as the newly created array t_2m_min_anom_stations is too large to be hold in memory

What did you expect to happen?

The final result should apply mask only on the variables that have lat,lon as dimensions

python <xarray.Dataset> Dimensions: (lat: 468, lon: 520, n_stations_t_2m_min_anom: 930) Coordinates: * lon (lon) float64 6.012 6.037 6.062 ... 18.96 18.99 * lat (lat) float64 36.01 36.04 36.06 ... 47.66 47.69 region int64 0 abbrevs <U2 'r0' names <U7 'Region0' Dimensions without coordinates: n_stations_t_2m_min_anom Data variables: t_2m_min_anom (lat, lon) float32 nan nan nan nan ... nan nan nan t_2m_min_anom_stations (n_stations_t_2m_min_anom) float64 1.935 ... 0.8557

Minimal Complete Verifiable Example

No response

MVCE confirmation

• [X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
• [ ] Complete example — the example is self-contained, including all data and the text of any traceback.
• [ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
• [ ] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output

No response

Anything else we need to know?

No response

Environment

What happened: When trying to write a dataset to netcdf file using the netcdf4 engine time is not saved correctly.

What you expected to happen: Time to be saved correctly as in the original dataset.

Minimal Complete Verifiable Example:

python ds.to_netcdf(filename, encoding={product_type: {'zlib': True, 'complevel': 9}}, engine='netcdf4')

is giving me the warning SerializationWarning: saving variable time with floating point data as an integer dtype without any _FillValue to use for NaNs

xarray Dataset

saved on disk (notice time values)

I cannot see anything special in the time array...is there a limitation because of the compression?

Environment: