Yes, thank you. I added the generic logic in varinfo.dat and mod_ncparam.F to process the variables for inert tracers boundary conditions:
'dye_west_' ! Input
'dye concentration western boundary condition'
'kilogram meter-3' ! [kg/m3]
'dye_west_, scalar, series'
'dye_time'
'idTbry(iwest,inert(i))'
'nulvar'
1.0d0
'dye_east_' ! Input
'dye concentration eastern boundary condition'
'kilogram meter-3' ! [kg/m3]
'dye_east_, scalar, series'
'dye_time'
'idTbry(ieast,inert(i))'
'nulvar'
1.0d0
'dye_south_' ! Input
'dye concentration southern boundary condition'
'kilogram meter-3' ! [kg/m3]
'dye_south_, scalar, series'
'dye_time'
'idTbry(isouth,inert(i))'
'nulvar'
1.0d0
'dye_north_' ! Input
'dye concentration northern boundary condition'
'kilogram meter-3' ! [kg/m3]
'dye_north_, scalar, series'
'dye_time'
'idTbry(inorth,inert(i))'
'nulvar'
1.0d0
There is not need to add an additional option or code for analytical lateral boundary conditions since ANA_TOBC and ana_tobc.h controls all the tracer fields. I not allowing to have both tracer boundary data (NetCDF file) and analytical expressions (ana_tobs.h) at the same time. You either set all the conditions for all tracers in ana_tobc.h or read all the data from NetCDG file. The tracer logic is ROMS is complex.