Skip to content

question about fldgen function conversions from R to python component #60

@abigailsnyder

Description

@abigailsnyder

@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

fullgrids = fldgen.generate_TP_fullgrids(emu, resids, tgav)

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

fullgrids <- fldgen::generate.TP.fullgrids(emu, resids, tgav,
                                  tvarunconvert_fcn = NULL, pvarunconvert_fcn = exp)

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions