Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Where possible, edges connecting nodes are
given different colours to make them easier to distinguish in
large graphs.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Where possible, edges connecting nodes are
given different colours to make them easier to distinguish in
large graphs.
Source Code
subroutine ocean_dyn_enter_data_impl(this)type(ocean_dyn_t),intent(inout)::thiscall barotropic_workstate_enter_data_impl(this%bt_work)! accel_visc_rem stage-entry snapshots: eagerly allocated at setup! (host source=0) only when the knob is on, so `copyin` (not `create`)! and gate on allocation — symmetric with the setup allocation and the! exit_data delete.if(allocated(this%avr_u0))then!$acc enter data copyin(this%avr_u0, this%avr_v0)end if! bt_wide is attached by ocean_dyn_enable_bt_wide (AFTER enter_data! for the rest of dyn); no attach here — see ocean_dyn_enable_bt_wide.end subroutine ocean_dyn_enter_data_impl