New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set correct initial conditions for fields excluded from calibration #153
Comments
There's another solution that doesn't require any changes to the API: we can add a property (either to Loading additional or "auxiliary" fields into the https://github.com/CliMA/Oceananigans.jl/blob/main/src/OutputReaders/field_dataset.jl so that users can easily build initialization functions... ? Something to consider is that there may be initialization requirements that can't be expressed in a I think "multipurposing" objects (eg using |
The |
Yeah! I might be hitting the point where I need this. :) |
|
It might be simple support excluding fields now using I think we'll still need |
@navidcy and I implemented this feature for @navidcy I don't see this feature on |
I opened #217 but I'm debating whether I should cherry-pick the relevant files and leave the calibration attempts out of it. :) |
ok! |
We need a way to be able to set initial conditions for fields that are not to be included in the calibration. Currently, if we want to calibrate the purely convective simulation considering only the field
b
and we start the calibration from 3 hours, fieldsu
,v
, ande
will be set to all zeros because they have not been stored in the observation. It seems to me that we should automatically store all available fields at all time steps in observations and:(1) remove
field_names
from the arguments ofSyntheticObservations
and provide some kind ofExclude
normalization option that will remove the field from the forward map output altogether, or automatically exclude all fields whose normalizations have not been specified.(2) add a
field_names
attribute toInverseProblem
that keeps track of, for each observation, which fields are to be included in the output map (and therefore which fields are to be tracked in thetime_series_collector
).(3) add a ‘field_names
attribute to
SyntheticObservations` that keeps track of which fields are to be included in the output map for that observation.I think option (1) makes the most sense since the choice of
field_names
directly pertains to the output map. Thoughts?The text was updated successfully, but these errors were encountered: