Hello Xinjie,
RHO stores the density but most of the time is useless in TELEMAC-3D as what is used to solve the equations is Delta rho / rho. That is why the key subroutine is DRSURR.
What do you mean by "is is RHO an array variable?"?
Be careful, USER_CONDI3D_TRAC is a user subroutine, defined by user, not standard TELEMAC-3D. The numbering of tracer (1 in USER_CONDI3D_TRAC) should be consistent with the numbering defined in NAMES OF TRACERS. IND_T and IND_S are generic number of tracers for temperature and salinity defined from your steering files.
If you exactly want to know how RHO is defined, have a look at how it is allocated in POINT_TELEMAC3D subroutine:
CALL BIEF_ALLVEC(1, RHO , 'RHO ', IELM3, 1, 1,MESH3D)
In short, that means RHO is defined at every node of the 3D mesh.
When calling DRSURR subroutine from TELEMAC3D subroutine, density is computed in RHO, you only need to use it if you want.
What do you mean by "how do I get a density field that is changing in time". If you do not use DENSITY LAW = 5, density varies most of the time if the tracers are active.
My last remark is, as a rule of this forum: DO NOT CROSS-POST THE SAME QUESTION TO MULTIPLE PLACES !!! It will be the best way I will not answer you next times for sure.
See
opentelemac.org/index.php/kunena/21-tele...cted-results-emerged
Hope this helps,
Chi-Tuan