Open crvernon opened 4 years ago
CI will fail right now due to the previous version of the .travis.yml
not loading an R environment.
Looks good to me. Only one comment, is there a way to keep track of the fact that Tgav sometime is defined as land-only and sometime (most of the times) refers to land+ocean average?
@claudiatebaldi Thanks! I am not sure and will have to think about this. I think it would be assumed from the parent model in use. Perhaps we just make that as a parameter for the config file where the user can specify. Although, aren't the land-only values taking the land+ocean interactions into account anyway even if they are not reporting ocean grid values?
Not sure what you mean with the "although" question, Chris. My point being only that if one is using a Tgav series it would be good to know if it is a global average or just land-only.But then again I'm not sure how this would work operationally, so it may be a redundant piece of information, already obvious to the user
Not sure what you mean with the "although" question, Chris. My point being only that if one is using a Tgav series it would be good to know if it is a global average or just land-only.But then again I'm not sure how this would work operationally, so it may be a redundant piece of information, already obvious to the user
I agree with @claudiatebaldi this is useful information to have and while this might be obvious to the original user I think it would be extremely useful to specify this sort of information for other users in order to understand what is actually being read into the pipeline.
FYI, note that SULI Skylar Gering's project this summer is to split Hector Tgav
into separate land and ocean variables, following e.g. MAGICC, with land Tgav warming faster in general.
@crvernon note this PR in the fldgen repo (implementing updates discussed in group call about 3.5 or 4 weeks ago) that may be useful https://github.com/JGCRI/fldgen/pull/49
Desire was to create a
Tgav
stub component to facilitate extracting data for a specific configuration (e.g., scenario, etc.) from ESM runs that were used to train thefldgen
emulator.Per @abigailsnyder:
The component named
TgavStubComponent
was added to Cassandra and provides the following capabilities:Tgav
: A data frame containing global mean temperature with fields ['year', 'scenario', 'variable', 'value', 'units']; where value isTgav
and type is a Pandas DataFrametgav_metadata
: A dictionary of metadata for theTgav
capability including: [rds_file, scenario, climate_var_name, source_climate_data, units, count, mean, median, min, max, std, na_count, null_count, all_finite] designations; typedict
The configuration block for the
TgavStubComponent
is the following:This component conducts validation at run time as well as being equipped with a robust test suite. All tests for this component are now passing locally. The metadata output is a summary of both the Tgav configuration as well as the data itself. The following is logged from the
tgav_metadata
capability:There are currently no constraints on these reported factors though they can be added easily if so desired. @kdorheim provided a summary of over 50 CMIP5 runs that we could use as
min
andmax
constraints from Taylor (2012) and stored here/pic/projects/GCAM/Dorheim/hectorcal/data-raw/CMIP5_annual_global_average.csv
:Please also consider constraints for finite, no data, and NaN if they were to be present in the data.
The following full run for this configuration was completed successfully:
With a logfile of:
I also checked the Xanthos outputs for global runoff per year resulting in the following:
Resolves #58