Aketh,POP generally uses k as the loop index for loops over the vertical dimension. Execpt for a single loop in init_baroclinic, all k loops in baroclinic.F90 are inside a loop over blocks. These block loops are all parallelized with OMP PARALLEL DO directives.I think adding more parallelization to the k loops would be difficult. One issue is that some of the loops have data dependencies from one k value to the next. An example is the variable WTK in baroclinic_driver and tracer_update. WTK's value for one k value depends on its value, and other computations, from previous k values. In order to parallelize these loops, the code would need to be restructured to eliminate these data dependencies. This would take considerable work to track down all dependencies and work around them. Another issue is that some diagnostic and tavg buffers get summed cummulatively over k. The code would need to be restructed to avoid parallel instances of these sums clobbering each other's computations. There might be other issues too. I would only suggest attempting this if you are fairly familiar with how POP works.Keith