Load(): Bug in s2dv >= 2.3.0 when order of variable definitions in NetCDF files is changed. Problems with infinite values.

After e-mail exchange and meetings between @mmenegoz , @pabretonniere and I, Martin has detected that when the variable definitions in the NetCDF files are changed of order, Load() may crash.

This didn't happen in s2dv < 2.3.0 which reminds of a bug or change of behaviour in ncdf4 R library.

Martin's examples:

This is a temporary experiment output with only some members:

/cfunas/exp/MORDICUS/PTUBO_1991/save_monthly_mean/tas_6hourly/tas_19910101.nc

This is the final file with all the members, after PA concatenated them to the original file:

/cfunas/exp/MORDICUS/PTUBO_1991/monthly_mean/tas_6hourly/tas_19910101.nc

This is the path to the script to load the data:

/cfunas/scratch/mmenegoz/MORDICUS/map_tas_mordicus_summer.R

This is the output of the script:

[1] "* /cfunas/exp/MORDICUS/PTUBO_1991/monthly_mean/tas_6hourly/tas_19910101.nc"
starting worker pid=21305 on localhost:10187 at 17:27:18.135
starting worker pid=21314 on localhost:10187 at 17:27:18.380
starting worker pid=21323 on localhost:10187 at 17:27:18.638
starting worker pid=21332 on localhost:10187 at 17:27:18.876
starting worker pid=21342 on localhost:10187 at 17:27:19.113
starting worker pid=21351 on localhost:10187 at 17:27:19.358
starting worker pid=21360 on localhost:10187 at 17:27:19.605
starting worker pid=21369 on localhost:10187 at 17:27:19.840
cdf_put_vara_double : ncid = 131072 varid = 5 val0 = inf
cdf_put_vara_double : varname = tas

Error in checkForRemoteErrors(val) :
  one node produced an error: incorrect number of dimensions