CMS forces longitude in releaseFile to [0, 360] range

[milancurcic]

After reading the input data in releaseFile, CMS forces the input longitude to be in the [0, 360] range.

connectivity-modeling-system/cms-master/src/input.f90

Lines 291 to 297 in fb49138

	read (iunit,*) id,lon,lat,depth,num_rel, year, month, day,seconds
	DO while (lon .lt. 0.)
	lon = lon + 360.
	ENDDO
	DO while (lon .ge. 360.)
	lon = lon - 360.
	ENDDO

However, the input data may be, say, in [-180, 180] longitude range, for example HYCOM GOMb0.01, and we can specify xstart and xend in nest_1.nml.

Is this range change necessary for some logic elsewhere in CMS? If not, we should remove this code as it needlessly complicates working with various model data.

[milancurcic]

From @beatrixparis: The longitude needs to be in the [0, 360] range if the Periodic Boundary Condition is true in runconf.list.