Can we define the list of tracer names for model construction programatically? #3650
Replies: 3 comments 5 replies
-
What do you mean by "inputting"? For post-processing, you can make a vector pretty easily: vector_tracers = [c for c in model.tracers] That just converts function get_vector_tracers(sim)
tracers = sim.model.tracers
return [c for c in tracers]
end If you want the tracers to be in a 4D array or something like that, and not just for post-processing but also while the simulation is running, that's also possible but a bit more work. |
Beta Was this translation helpful? Give feedback.
-
Thanks @glwagner for the reply and I am sorry I was not clear. When we define the model, we must specify what tracers we want to use. For example, we could have Instead, can we define a tracer to be a vector field and evolve each of those fields? Maybe this is what you were thinking when you said a 4D array? |
Beta Was this translation helpful? Give feedback.
-
You could do |
Beta Was this translation helpful? Give feedback.
-
I want to do a simulation with a lot of tracers, maybe 100 or more. Rather than inputing each individually, I would really like to use a tracer that is a vector. Is this possible?
If not, how much work would it be to get this working?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions