Closed LukeBarnard closed 4 years ago
When adding in lon_init to HUXt2D, I forgot to update save and load_HUXt2D_run to take account of lon_init. Therefore when loading these data there will be an incorrect time_init and times will be offset.
This is now fixed in the version.
When adding in lon_init to HUXt2D, I forgot to update save and load_HUXt2D_run to take account of lon_init. Therefore when loading these data there will be an incorrect time_init and times will be offset.