Ivana Escobar

Catching up now, I can compile and run for `verification/global_oce_biogeo_bling`. I do get the warning that `g_xx_*.data` are being initiated to zeros, but that's to be expected, right?

@mjlosch are the `exf` package errors present when the edits from this PR are removed? An idea could be to wrap the REQUIRED directive by `#ifdef ALLOW_TANGENTLINEAR_RUN`. I'm not sure...

Ok, So this PR should be good as is

I haven't tried removing the conditional. I was assuming there was a reason beyond my understanding for why it's there.

I’m happy to try out the changes you’ve implemented! I don’t have an alternative conceptualized, so @mjlosch feel free to take this to a PR!

This may be unrelated to this issue, but I'll post here to start. ## Using the verification problem `verification/global_oce_biogeo_bling` along with modifications from #873 , I am able to get...

Ok, to make sure I understood. A forward sensitivity perturbation should be defined via `g_xx_*.data` for the TLM to show non-zero adjustments in the forward gradients. This is independent of...

Back to the purpose of this issue: It sounds like adapting the package for global file writing may be too big of an endeavor. Running the `verification/global_oce_biogeo_bling` set-up with `grdchk`,...

Another thing to note is that using `pkg/grdchk` with `pkg/ecco` may result in confusing final results for cost function accumulation.   For example, in `verification/global_oce_biogeo_bling`, compiling and running the TAF AD...

> Another thing to note is that using `pkg/grdchk` with `pkg/ecco` may result in confusing final results for cost function accumulation. @mjlosch this issue has been fully addressed by your...