v1.3.5: slice selection sliders showing incorrect dimension info

[huiwanpnnl]

See screenshot below. The two sliders in red frame are showing dimension info that seems to have been incorrectly copied from lev and/or ilev.

[jourdain]

Seems correct on my end

[jourdain]

Or maybe you are talking about the way the label is presented. Those *band should not be hPa but another unit?

If that is the case, I'm wondering if we can extract the proper unit from the field (name or property)

@danlipsa do you know if when we read the data we have that info?

[huiwanpnnl]

@jourdain, ah yes, I was talking about the label. Using the ncdump command, I can see the following info about swband:

        float swband(swband) ;
                swband:units = "1/cm" ;
                swband:_FillValue = 3.402824e+33f ;
                swband:long_name = "MISSING" ;
                swband:standard_name = "MISSING" ;

 swband = 1750, 2965, 3625, 4325, 4900, 5650, 6925, 7875, 10450, 14425, 
    19325, 25825, 33500, 44000 ;

So, it looks like the Reader has correctly imported the values of swband but assumed a wrong unit.

[jourdain]

I think the UI/label is hard coded right now, hence the issue. ;-)

[danlipsa]

@huiwanpnnl What is the dataset for this?

[huiwanpnnl]

This is the EAMxx-MAM4xx_ne4pg2_202508.nc data file in this folder. The corresponding connectivity file is connectivity_ne4pg2_TEMPEST.scrip.nc in that same folder.

[huiwanpnnl]

I think the UI/label is hard coded right now, hence the issue. ;-)

Agreed.

And I think there is another category of dimensions that we want to address. In the same data file, I see dimensions ext_cnt, num_gas_aerosol_constituents, and num_phys_constituents which do not have corresponding float or double variables with the same names. For those, I guess we should let their slider labels show the index values (0, ...)?

FYI, for lev and ilev, Ahbishek and I chose to let the labels say [coordinate value] [unit] (k = [index value]). To generalize that pattern, we could perhaps use the following:

• When we do have a float/double coordinate variable AND its unit: Coordinate value: [coordinate value] [unit], index value: [index value]
• When we have a float/double coordinate variable and no unit provided as metadata: Coordinate value: [coordinate value], index value: [index value]
• When we have only a dimension and no coordinate variable: Index value: [index value]

Just my 2 cents.