Skip to content

Releases: Chrismarsh/CHM

1.5.0 beta 9

31 Jan 04:32
Compare
Choose a tag to compare
  • output the vtu and shp points for forcing into a seperate dir

1.5.0 beta 8

27 Jan 17:56
Compare
Choose a tag to compare
  • FIx incorrect handling of netcdf multipart enddate

1.5.0 beta 7

26 Jan 21:35
Compare
Choose a tag to compare
  • FIx precip unit conversion
  • Output PVD to base of output folder

1.5.0 beta 6

26 Jan 03:50
Compare
Choose a tag to compare
  • Allow for checkpointing at arbitrary timesteps
  • Basic unit conversion for netcdf files

Full Changelog: 1.5.0b5...1.5.0b6

1.5.0 beta 5

19 Jan 20:02
Compare
Choose a tag to compare
  • Fix a regression with custom starting points from either user of checkpoint when using multipart nc files

1.5.0 beta 4

09 Jan 03:35
Compare
Choose a tag to compare

Fix ascii timeseries not being correctly loaded after the multipart nc feature was added

1.5.0 beta 3

16 Dec 19:44
Compare
Choose a tag to compare
1.5.0 beta 3 Pre-release
Pre-release

FIx delta_t consistency check. How it just checks that the offsets are spaced consistently. Should be more reliably and more performant

1.5.0 beta 2

16 Dec 16:30
Compare
Choose a tag to compare
1.5.0 beta 2 Pre-release
Pre-release

Fix netcdf loading bug with hourly

1.5.0 beta 1

12 Dec 04:02
Compare
Choose a tag to compare
1.5.0 beta 1 Pre-release
Pre-release
  • fix missing file

1.5.0 beta 0

12 Dec 02:20
Compare
Choose a tag to compare
1.5.0 beta 0 Pre-release
Pre-release

This version includes a major rewrite of the netCDF loader:

  • requires CF-compliant standard_name attributes to dynamically determine variables
  • support multipart netcdf files (e.g., one nc file per day)
  • the grid of each multipart does not need to remain constant, allowing for trivially changing the resolution or product used at different timesteps, for example to switch from a short term 2.5km forcing to a coarser long-term 10km forcing
  • output of a per-rank grid centres used for forcing as shapefiles

This also fixes a bug associated with loading too many forcing points for a mesh.