Error in step1_preprocess_forcings (line 109) - "Variable 'lons' not found."

[patricksykes]

The lons variable doesn't seem to be defined in the step1_preprocess_forcings file. I'm not exactly sure what it's supposed to be either. (Should it also be a vector like lats is currently defined? Or something else?)

Full error message follows.

Operation terminated by user during step1_preprocess_forcings (line 83)

Error using save
Variable 'lons' not found.

Error in step1_preprocess_forcings (line 109)
save processed_forcings/cesm_lons.mat lons

[jaseeverett]

Thanks @patricksykes. I had the same problem. I will look into it.

[ric325]

I think lons is from 0 to 359 in steps of 1 for BOATS. From: patricksykes <notifications@github.com> Reply to: MathMarEcol/BOATS_workshop <reply@reply.github.com> Date: Monday, 1 June 2020 at 3:27 pm To: MathMarEcol/BOATS_workshop <BOATS_workshop@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [MathMarEcol/BOATS_workshop] Error in step1_preprocess_forcings (line 109) - "Variable 'lons' not found." (#1) The lons variable doesn't seem to be defined in the step1_preprocess_forcings file. I'm not exactly sure what it's supposed to be either. (Should it also be a vector like lats is currently defined? Or something else?) Full error message follows. Operation terminated by user during step1_preprocess_forcings (line 83) Error using save Variable 'lons' not found. Error in step1_preprocess_forcings (line 109) save processed_forcings/cesm_lons.mat lons — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABLPRX5ZA4YPJCAL626TZYDRUM32NANCNFSM4NPQQHCA>.

[patricksykes]

@ric325 I assumed that's the case but want to check this, because when I made that fix, the step 2 script throws a warning on the dimension of lons, and an error related to dimensions in line 162. I don't want to raise an issue for that before making sure it's not the lat/lons making it fail.

[patricksykes]

My pull request (#2) should fix it, but I'm still not sure it's the right ones.

I'm using lons = 0:359 and lats -89.5:89.5 (following from the input data itself), but I noticed in step5 the lines:

ncwrite(curr_name, 'lon', -179.5:1:179.5); %% THESE LONS HAVE BEEN CHECKED FOR GFDL AND CESM, CHECK IF USING DIFFERENT FORCING
ncwrite(curr_name, 'lat', -89.5:1:89.5);

This agrees with the lats we've input, but not the lons. I'm no expert (not even a novice) in netCDFs, so for all I know this apparent discrepancy is actually the correct way.