@manishvenu has made a start on setting properties corresponding to each forcing file. For example, calling
expt.initial_condition
now opens the initial conditions from the input directory. We should stop saving self.bathymetry upon generating bathymetry to minimise memory footprint, and instead have a property for each of the files in the input directory which simply opens existing dataarrays, or prints an error message if they're not found.
This would require renaming the current bathymetry_property in #12 to bathymetry, splitting the initial_condition into the tracer and velocity and eta components, and deleting the existing bathymetry property that is saved automatically upon generating bathymetry.
@manishvenu has made a start on setting properties corresponding to each forcing file. For example, calling
expt.initial_condition
now opens the initial conditions from the input directory. We should stop saving
self.bathymetry
upon generating bathymetry to minimise memory footprint, and instead have a property for each of the files in the input directory which simply opens existing dataarrays, or prints an error message if they're not found.This would require renaming the current
bathymetry_property
in #12 tobathymetry
, splitting theinitial_condition
into the tracer and velocity and eta components, and deleting the existingbathymetry
property that is saved automatically upon generating bathymetry.