Skip to content
Discussion options

You must be logged in to vote

As you've guessed we don't have an interface for specifying more than one forcing right now, though I think it might be convenient for use cases like yours.

As a temporary workaround before we have such a feature, you can embed a Relaxation object inside another forcing function and call it with

relaxation(x, y, z, t, f)

where relaxation::Relaxation and f is the field being relaxed (the velocity component in question in this case).

@pjrusello would you like to open an issue with a feature request for specifying multiple forcing functions and we can discuss further there? We might be able to handle this by having users specify forcings as a tuple, eg in a model constructor,

forcing = (; u =

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@pjrusello
Comment options

Answer selected by pjrusello
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants