id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
384	Multifile vs single file processing differences in ropp_fm_bg2ro_1d	Ian Culverwell	Ian Culverwell	"There are some differences in the the output, esp of WARNING messages, when '''ropp_fm_bg2ro_1d''' is run on single files and multifiles.  See attached '''GRAS_xxx_1B_M02_20141115142313Z_20141115142727Z_N_O_20141115152139Z.bg.nc''' (singlefile) and '''GRAS_xxx_1B_M02_20141031001713Z_20141031002055Z_N_O_20141031014235Z.bg.nc''' (multifile), and their associated outputs and run script. 


In addition, undulations seem to be handled differently in the different profiles of a multifile, so that this input

{{{
 /data/nwp1/idculv/ROPP/Work/ROPP8.0/ropp_fm
idculv@eld037:> ncks -H -vundulation GRAS_xxx_1B_M02_20141031001713Z_20141031002055Z_N_O_20141031014235Z.bg.nc
dim_unlim[0] undulation[0]=-9999.9 
dim_unlim[1] undulation[1]=-9999.9 
}}}

gives this output

{{{
/data/nwp1/idculv/ROPP/Work/ROPP8.0/ropp_fm
idculv@eld037:> ncks -H -vundulation GRAS_xxx_1B_M02_20141031001713Z_20141031002055Z_N_O_20141031014235Z.fw.nc
dim_unlim[0] undulation[0]=0 
dim_unlim[1] undulation[1]=-9.9999e+07 
}}}

This is wrong."	defect	closed	normal	9.0	ropp_fm	7.1	fixed	undulation