DOI: 10.6073/pasta/9589b946c54e172fe4dfaf269b59ba23
title: SBC LTER: Regional Oceanic Modeling System (ROMS) Setup Files, Code, and Lagrangian Model Setup Files

description: This data contains all the necessary code, grid, forcing, initial, and boundary condition files for running the UCLA version of the Regional Oceanic Modeling System (ROMS) for the Santa Barbara Channel nested solution set that is analyzed in Dauhajre and McWilliams (2019): Nearshore Lagrangian Connectivity: Resolution Sensitivity and Submesoscale Influence. Along with this abstract and separate methods, a brief readme file (README_ROMS) contains other relevant details for running the simulations. The ROMS files in this data correspond to a one-way grid-nesting with the following horizontal resolutions: dx=1km, 300m, 100m, 36m that correspond to R1km, R300m, R100m, and R36m in the publication. In the data directories here, these grids have the following prefixes for all relevant files (grids, forcing, initial condition, and boundary conditions): “usw1” (dx=1km), “usw2” (dx=300m), “usw3” (dx=100m), and “usw4sbc” (dx=36m). The ROMS code is in fortran and requires compilation, with compilation instructions in the directory /src_ROMS_UCLA_2018 in the file “compile.sh”. All grid, forcing, initial, and boundary condition files are in netcdf form. The grid files are in the directory “grids”. Note that the R1km grid has 2 files: usw1_grd.nc and usw1_grd_samp.nc. The latter is a smaller version of the grid that focuses on the Santa Barbara Channel that can be used for the offline Lagrangian model for faster computation (which requires an analogous sub-sampling of the ROMS output). For running ROMS, usw1_grd.nc needs to be used as it corresponds to the entire domain. The atmospheric forcing, derived from a Weather Research and Forecasting model at dx=6km resolution is given in the directory “forcing_files”; all atmospheric forcing files are interpolated to the relevant ROMS grid and formatted to be used as inputs in ROMS. Each grid contains a file corresponding to precipitation (e.g., usw1_prec.nc), radiation (e.g., usw1_rad.nc), atmospheric temperature and specific humidity (e.g., usw1_tra.nc), and wind (e.g., usw1_wnd.nc). Initial and boundary conditions are located in the directory “init_bry_files” with initial condition files denoted by the suffix “init” and boundary conditions denoted by the suffix “bry”. The input files for the ROMS code are located in the directory “infiles_ROMS”. Each input files specifies the time-stepping, initial and boundary conditions, forcing files, and output frequency. The files in this directory are specific to the simulations used in Dauhajre and McWilliams (2019): that is, output files comprised of 30 min. averages. This data also contains the input and output files of the Python-based, offline Lagrangian model that simulates particle trajectories using the Eulerian velocities from the ROMS solutions. The Lagrangian model input files (in the directory “pypart_infiles”) provide the setup of the coastal connectivity experiment of Dauhajre and McWilliams (2019); these Python files work as inputs to the offline Lagrangian model that is available on GitHub: https://github.com/ddauhajre/PY_PART_ROMS/ (with further explanation therein). In the data here, there are input and output files for five Lagrangian experiments: four 3-D Lagrangian simulations at the four resolutions (dx=1km, 300m, 100m, and 36m) and one 2-D Lagrangian simulation at dx=36m. The input files have a “.py” (python script) file and “.p” (python pickle data structure) file. The “.py” files (e.g., R100m_pypart_params.py) contain the input parameters for the Lagrangian model. There are two types of .p files (e.g., L2_SBC_masks.p and L2_SBC_init_part_oct31.p). The “masks” files contain the boundaries of the coastal connectivity cells for each grid (1km = L1, 300m = L2, 100m = L3, and 36m = L4). The “init_part” files are generated from the python model code containing the pre-determined initial particle positions relative to the coastal connectivity cells defined in the “masks” file.