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
@crvernon@FeralFlows I don't know if this is an oversight, or something that got taken care of in a different part of the code calling the fldgen R functions from python but I noticed in line 908 of components.py, in the run_fldgen function, there is this line
If I was doing that in R, the final reconstructed full grids would be given in units of Kelvin (the temperature units of the training data) and LogPrecipitation still.
In R, if I wanted units of precipitation, the call I would do is
I don't know enough of how we go from fldgen::generate.TP.fullgrids in R to fldgen.generate_TP_fullgrids in components.py to know if that happened somewhere else in that process, or if it's not happening at all in the code.
The text was updated successfully, but these errors were encountered:
Note that there was this issue opened in the fldgen repo (JGCRI/fldgen#32) that sounds kind of related. I closed it out there, because the function does properly convert the mean field back to native units (that is, from logP to P) if you give the function the right arguments to do so. I didn't think about where the use of fldgen might have brought that issue up, so I didn't look outside of the fldgen repo. I checked the order of operations a bunch of times because it is a little finicky, and I recorded my notes in the issue when I closed it out. Always possible I made a mistake though.
But now, I wonder if it came up from looking at these pipeline results and thinking it was an issue with the function itself rather than the call to the function within the pipeline, and so got put in the fldgen repo instead of here. I could also be completely wrong.
*I did just remember that tvarunconvert_fcn = NULL, pvarunconvert_fcn = exp) are the default arguments to fldgen::generate.TP.fullgrid, so in R, you wouldn't have to include those arguments. So maybe it is the same in python code calling R functions, sorry, I just don't know.
@crvernon @FeralFlows I don't know if this is an oversight, or something that got taken care of in a different part of the code calling the fldgen R functions from python but I noticed in line 908 of
components.py
, in therun_fldgen
function, there is this lineIf I was doing that in R, the final reconstructed full grids would be given in units of Kelvin (the temperature units of the training data) and LogPrecipitation still.
In R, if I wanted units of precipitation, the call I would do is
I don't know enough of how we go from
fldgen::generate.TP.fullgrids
in R tofldgen.generate_TP_fullgrids
incomponents.py
to know if that happened somewhere else in that process, or if it's not happening at all in the code.The text was updated successfully, but these errors were encountered: