Search the Community

Hello, Is it necessary to use the isodate format when specifying boundary conditions that include atmospheric heat calculations? My simulation runs when using isodate, but when I try to run it using model hours (ie time format == hours) the following error is returned: t = 0.000000 hrs. dt = 0.000 / 0.000 s. elapsed time = 0.0 s. Writing H datfile output. t = 0.000000 hrs. Writing TEMP datfile output. t = 0.000000 hrs. Writing V datfile output. t = 0.000000 hrs. Writing TEMP datfile output. t = 0.000000 hrs. Writing V datfile output. t = 0.000000 hrs. Writing NETCDF output. t = 0.000000 hrs. ERROR: day_of_the_year requires tform == 1 ERROR-STACK:fvdomain_run:fvdomain_run_timestep:fvcell_turb:fvatmos_update:heat_sw:day_of_the_year requires tform == 1 In my bc file, I am specifying temperature (water), short wave radiation, long wave radiation, mean sea level pressure, rain, relative humidity, and air temperature. Wondering if maybe the heat transfer calculations require knowledge about the date and that is why it is returning the error when hours are used. Thanks!

Hi folks, We're looking to start a simulation with one body of water (out of many) filled with tracer so we can see where it ends up as the simulation progresses. It's not apparent from the documentation that this is possible except globally; is there a way to do this this locally? Alternatively, is there something analogous to an SA boundary which could include tracer in an inflow over an area (so a small inflow in the first minute with large concentration of tracer, then nothing further for the rest of the simulation)? We currently have applied 11,000 cell boundaries, one for every cell in the area we're interested in! Which sort of works, but ends up with different concentrations in each cell as the element sizes vary (because they all they the same same small quantity of additional water with, with the same concentration of tracer, but have differing volumes of water already in the cells). Any advice or top tips greatly appreciated! I'm hoping we've just missed something in the currently available tool kit, but if this isn't currently possible, could it perhaps be made so? (That is, both setting initial conditions for tracers locally and being able to apply an SA type inflow complete with tracer). Thanks, PHA.