You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I just found another issue with the flags, not using the flag -teos10 in the cdfbuoyflx program does not change how the beta is computed. In other words, despite not having the flag, the default beta is computed with the beta_2d program (teos10) instead of the the beta_2d_80 program.
Additionally, I'm confused with how beta and alpha are computed. I've compared the values of beta and alpha from the CDFTools and python libraries sw and gsw. I've noticed that associated with the issue above, in the CDFtools both beta and alpha when using the using the beta_2d program is multiplied by a factor of 1026 (the reference density). I'm not sure if I'm missing something, but I found it extremely confusing and there is no documentation anywhere on this.
I haven't checked if this issue extends to other routines...
The text was updated successfully, but these errors were encountered:
josuemtzmo
changed the title
Issues with the cdfbuoyflx program and potentially the computation of alpha and beta
Issues with the cdfbuoyflx program and documentation on the computation of alpha and betaApr 13, 2023
Hello,
I just found another issue with the flags, not using the flag
-teos10
in thecdfbuoyflx
program does not change how thebeta
is computed. In other words, despite not having the flag, the default beta is computed with thebeta_2d
program (teos10
) instead of the thebeta_2d_80
program.Additionally, I'm confused with how
beta
andalpha
are computed. I've compared the values ofbeta
andalpha
from the CDFTools and python libraries sw and gsw. I've noticed that associated with the issue above, in the CDFtools bothbeta
andalpha
when using the using thebeta_2d
program is multiplied by a factor of1026
(the reference density). I'm not sure if I'm missing something, but I found it extremely confusing and there is no documentation anywhere on this.I haven't checked if this issue extends to other routines...
The text was updated successfully, but these errors were encountered: