You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently write_timeseries_dsg() builds a netCDF with 2 dimensions: time and the instance names. Would it be within scope for that function to add the option to specify a 3rd dimension? Our use case would be packaging up timeseries of predicted lake temperature profiles, where we have the 3rd dimension of depth below the lake surface.
The text was updated successfully, but these errors were encountered:
That would be in scope. One way to handle it would be to add the additional dimension and the data after creating the base file. Maybe you could mock that up and we could incorporate the code into a package function? The basic write_timeseries_dsg() function already has a ton going on.
Okay, thanks, Dave. That's a good thought to modify the file to add the extra dimension and data after building it with write_timeseries_dsg() and data for a single depth. We're in a bit of a sprint for our lake modeling project, so I will plan to write a function specific to our use case for now, trying out your suggested approach. I will link to the resulting function here, as I may have the bandwidth to return to this issue to make a more generic version later on.
Currently
write_timeseries_dsg()
builds a netCDF with 2 dimensions: time and the instance names. Would it be within scope for that function to add the option to specify a 3rd dimension? Our use case would be packaging up timeseries of predicted lake temperature profiles, where we have the 3rd dimension of depth below the lake surface.The text was updated successfully, but these errors were encountered: