Delete _FillValue and history from parameter files

[samsrabin]

Description of changes

Updates parameter files to c240207b. These are the same as c240105 except:

• Attribute _FillValue has been removed from variables that had it erroneously added in c240105
• Global attributes history, history_of_appended_files, and latest_git_log have been removed

Specific notes

Contributors other than yourself, if any: None

CTSM Issues Fixed:

• Fixes Parameter file formatting has changed #2347

Are answers expected to change (and if so in what way)? No

Any User Interface Changes (namelist or namelist defaults changes)? No

Testing performed, if any:

• aux_clm OK as of 1949f5c
• ncdump -v bgc_rf_l1s1 prints the value instead of _

[samsrabin]

@wwieder and @olyson: New parameter files are available for you to try:

• clm45_params.c240207.nc
• clm50_params.c240207.nc
• ctsm51_params.c240207.nc
• ctsm51_ciso_cwd_hr_params.c240207.nc

[olyson]

Thanks, that seems to be working for me.

[samsrabin]

@ekluzek This is ready for your approval.

[ekluzek]

Thanks for working on this @samsrabin. This will be nice to get in ASAP, since it's causing trouble for people. I'm also glad that you removed the history attribute as we talked about since it wasn't working in cprnc. history is a standard CF standard variable that some tools also update automatically when a change is made (for example NCO), so it's useful in general, but it had become too long. But, we can add it back in when it makes sense, which as we said will likely be when we start tuning things.

This is of course really simple, since it just changes the parameter files. I'm hitting this as approve so as to not slow it down. But, I do have an important question.

This removes _FillValue that were nan, and _FillValue for scalars both of which make sense. What I'm not so sure about is that it also removes _FillValue for arrays and it's also removing _FillValue's that were consciously set to something. Here's a list of non NaN _FillValues...

- 		allconsl:_FillValue = 0. ;
- 		allconss:_FillValue = 0. ;
- 		arootf:_FillValue = 0. ;
- 		arooti:_FillValue = 0. ;
- 		astemf:_FillValue = 0. ;
- 		bfact:_FillValue = 0. ;
- 		cc_dstem:_FillValue = -999.99 ;
- 		cc_leaf:_FillValue = -999.99 ;
- 		cc_lstem:_FillValue = -999.99 ;
- 		cc_other:_FillValue = -999.99 ;
- 		declfact:_FillValue = 0. ;
- 		fd_pft:_FillValue = -999.99 ;
- 		fleafi:_FillValue = 0. ;
- 		fm_droot:_FillValue = -999.99 ;
- 		fm_dstem:_FillValue = -999.99 ;
- 		fm_leaf:_FillValue = -999.99 ;
- 		fm_lroot:_FillValue = -999.99 ;
- 		fm_lstem:_FillValue = -999.99 ;
- 		fm_other:_FillValue = -999.99 ;
- 		fm_root:_FillValue = -999.99 ;
- 		fsr_pft:_FillValue = -999.99 ;
- 		gddmin:_FillValue = 0. ;
- 		graincn:_FillValue = 0. ;
- 		grnfill:_FillValue = 0. ;
- 		hybgdd:_FillValue = 0. ;
- 		laimx:_FillValue = 0. ;
- 		lfemerg:_FillValue = 0. ;
- 		max_NH_planting_date:_FillValue = 0 ;
- 		max_SH_planting_date:_FillValue = 0 ;
- 		mergetoclmpft:_FillValue = 0 ;
- 		min_NH_planting_date:_FillValue = 0 ;
- 		min_SH_planting_date:_FillValue = 0 ;
- 		min_planting_temp:_FillValue = 1000. ;
- 		mxmat:_FillValue = 0 ;
- 		mxtmp:_FillValue = 0. ;
- 		pftpar20:_FillValue = 9999.9 ;
- 		pftpar28:_FillValue = 9999.9 ;
- 		pftpar29:_FillValue = 1000. ;
- 		pftpar31:_FillValue = 1000. ;
- 		planting_temp:_FillValue = 1000. ;
- 		pprodharv10:_FillValue = 0. ;
- 		variantnames:_FillValue = "" ;
- 		ztopmx:_FillValue = 0. ;

I think those ones likely have some meaning and should probably remain as they were. Other's of the arrays probably should have _FillValue as well, but it would take some time to analyze which ones and what the value should be. So that would be a job for later...

[samsrabin]

@ekluzek Good point. I've now made new files, *c240207b.nc, with _FillValue only removed from variables that had it erroneously added in c240105. Does that work?