Opened 10 years ago

Closed 9 years ago

#428 closed defect (fixed)

ROPP returning azimuths between -180 deg and 180 deg

Reported by: Ian Culverwell Owned by: Ian Culverwell
Priority: normal Milestone: 9.0
Component: ropp_utils Version: 8.0
Keywords: Cc:

Description

ROPP seems to be returning azimuths between -180 deg and 180 deg, eg running

/data/nwp1/idculv/ROPP/ropp_src/branches/dev/Share/ROPP81_prototype/ropp_pp/tools/ropp_pp_occ_tool IT-PP-03_prof19.nc -o IT-PP-03_prof19_cntl.nc -mfile MSIS_coeff.nc -c gras_pp.cf -ellipsoid -d -m MSIS -no-ranchk

on the attached gives

ncks -H -vazimuth IT-PP-03_prof19_cntl.nc                                        
dim_unlim[0] azimuth[0]=-7.26265 

If run without the -no-ranchk option, we get

idculv@eld037:> ncks -H -vazimuth IT-PP-03_prof19_cntl.nc                                              
dim_unlim[0] azimuth[0]=-9.9999e+07

This is because the valid range of azimuths in ROPP is [0, 360]. This is easy enough to fix, but the consequences need careful checking.

Attachments (2)

IT-PP-03_prof19.nc (647.6 KB ) - added by Ian Culverwell 10 years ago.
IT-PP-03_prof19.nc
occ_point.f90 (4.7 KB ) - added by Ian Culverwell 10 years ago.
occ_point.f90

Download all attachments as: .zip

Change history (6)

by Ian Culverwell, 10 years ago

Attachment: IT-PP-03_prof19.nc added

IT-PP-03_prof19.nc

comment:1 by Ian Culverwell, 10 years ago

Note that azimuth_tp is OK, even when we run without -no-ranchk:

ncks -H -vazimuth_tp -ddim_lev1b,0,4 IT-PP-03_prof19_cntl.nc
dim_unlim[0] dim_lev1b[0] azimuth_tp[0]=352.417 
dim_unlim[0] dim_lev1b[1] azimuth_tp[1]=352.42 
dim_unlim[0] dim_lev1b[2] azimuth_tp[2]=352.423 
dim_unlim[0] dim_lev1b[3] azimuth_tp[3]=352.426 
dim_unlim[0] dim_lev1b[4] azimuth_tp[4]=352.429 

This is because azimuth_tp is calculated by ropp_utils/coordinates/tangent_point.f90, which includes the relevant line:

if (azimuth_tp(i) < 0.0_wp ) azimuth_tp(i) = azimuth_tp(i) + 360.0_wp 

ropp_utils/coordinates/occ_point.f90, which calculates the georef%azimuth (among other things), does not have this line.

The only problem with just inserting this check on negative azimuths in occ_point.f90 is that it's called by ropp_pp_preprocess.f90 and ropp_pp_spectrum_tool.f90, although I don't think either uses the azimuth that it calculates.

comment:2 by Ian Culverwell, 10 years ago

Checked that when I rerun with the attached occ_point.f90 I get (with or without the -no-ranchk option)

ncks -H -vazimuth IT-PP-03_prof19_test.nc
dim_unlim[0] azimuth[0]=352.737 

which looks fine.

There are no other differences in the output files.

I think this is probably grounds enough for making the change.

by Ian Culverwell, 10 years ago

Attachment: occ_point.f90 added

occ_point.f90

comment:3 by Ian Culverwell, 10 years ago

Stig and Chris B agree this is a sensible fix. CB points out that UCAR azimuths lie between -180 deg and 180 deg.

See #325 and #233 for earlier work on this.

comment:4 by Ian Culverwell, 9 years ago

Component: ropp_ppropp_utils
Resolution: fixed
Status: newclosed

Introduced at r4753.

Closing ticket.

Note: See TracTickets for help on using tickets.