id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
363	Why is azimuth changed by ropp_1dvar_bangle_add_error?	Ian Culverwell	Ian Culverwell	"{{{
ropp_1dvar_add_bangle_error -Omod EC temp1.nc -o temp2.nc
}}}

produces

{{{
ncks -H -vazimuth temp1.nc
dim_unlim[0] azimuth[0]=206.688 

idculv@eld037:> ncks -H -vazimuth temp2.nc
dim_unlim[0] azimuth[0]=3.60738 

idculv@eld037:> ncdump -h temp1.nc |grep azimu
	float azimuth(dim_unlim) ;
		azimuth:long_name = ""GNSS->LEO line of sight angle (from True North) for the reference coordinate"" ;
		azimuth:units = ""degrees_T"" ;
		azimuth:valid_range = 0., 360. ;
	float azimuth_tp(dim_unlim, dim_lev1b) ;
		azimuth_tp:long_name = ""GNSS->LEO line of sight angles (from True North) for tangent points"" ;
		azimuth_tp:units = ""degrees"" ;
		azimuth_tp:valid_range = 0., 360. ;

idculv@eld037:> ncdump -h temp2.nc |grep azimu
	float azimuth(dim_unlim) ;
		azimuth:long_name = ""GNSS->LEO line of sight angle (from True North) for the reference coordinate"" ;
		azimuth:units = ""degrees_T"" ;
		azimuth:valid_range = 0., 6.28318530717959 ;
	float azimuth_tp(dim_unlim, dim_lev1b) ;
		azimuth_tp:long_name = ""GNSS->LEO line of sight angles (from True North) for tangent points"" ;
		azimuth_tp:units = ""degrees"" ;
		azimuth_tp:valid_range = 0., 360. ;

}}}

So it's changed the units from deg to rad, but kept the units attribute as ""degrees_T"".

Range-checking is off by default. 

(Azimuth_tp is - correctly - unchanged, however.)
"	defect	closed	normal	8.0	ropp_1dvar	7.1	fixed