Test QuickView for regional output

[huiwanpnnl]

A colleague from the E3SM atmosphere group says they also have some simulation files that contain data only on a portion of the globe. I suppose QuickView will be able to handle those after we generate the corresponding connectivity files. I will get a sample file from the colleague and then follow up here.

[huiwanpnnl]

Hi @jourdain , it turns out I've gotten an example of regional output myself. Below is a screenshot I got at NERSC and here is the corresponding state file: quickview-state_NSA_regional.json.

The good news is that since I did create (some months ago, for ParaView) the connectivity file for the regional subset of grid cells, I was able to load the connectivity and simulation files with QuickView and visualize the fields!

A couple of issues I noticed are:

• The latitude slider is not working properly: it not only crops the map but also crops my data. The longitude slider seems to be working fine, though.
• The region, 170E-230E, 55N-85N, is shown in 2 corners of the global map. I guess it's time to address this open issue: Enable center to be defined in lat/lon #16

Thanks in advance for your help!

[jourdain]

• The latitude slider crop the data right away rather than respecting the offset/region the data is bound onto.
• The longitude seems to be working probably because the data span the full range (because of the cut). But I suspect that if the data was only located in one region, we might run into similar cropping offset issue.

[huiwanpnnl]

@jourdain, you were correct about the longitude slider! After you fixed the data loading issue in #122 , I was able to see the tiny region that had data in that example, and there, I indeed saw the longitude slider crop the data!

[jourdain]

Will be fixed in >2.9.1