Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nitrogen deposition files from the SSP scenarios have a noticeable "jump" from the historical period at 2015 #968

Closed
timhoar opened this issue Apr 3, 2020 · 13 comments
Closed

nitrogen deposition files from the SSP scenarios have a noticeable "jump" from the historical period at 2015 #968

timhoar opened this issue Apr 3, 2020 · 13 comments
Assignees
@ekluzek
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix investigation Needs to be verified and more investigation into what's going on.

Comments

@timhoar
Copy link

timhoar commented Apr 3, 2020

I need to continue an existing run from 2014 to the present day and was exploring which of the scenarios might be the most appropriate. I decided to first look at the (unweighted) global mean timeseries for each variable from each SSP scenario that matched my resolution. I looked for SSPs in /glade/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata and used SSP1-2.6, SSP2-4.5, SSP3-7.0 and SSP5-8.5 and compared them to fndep_clm_hist_b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.ensmean_1849-2015_monthly_0.9x1.25_c180926.nc.
Everything overlaps nicely until 2015 and then there seems to be no scenario that continues along without a bias or discontinuity. I understand that the scenarios are intended to be different, but I'm really looking for a smooth transition into a 'business as usual' scenario consistent with the data up to 2015.

clm_ndep_timeseries.pdf

Each figure has a title with the 'experiment name', variable, variable size, and variable long name. The files used for each label are under each figure, the units for each variable/file are along the y axis.

I've also put the population density plots on this graphic - they are a good example of what I hope the transition to the new SSPs should be.

The existing case is a
HIST_CAM60_CLM50%BGC-CROP_CICE%PRES_DOCN%DOM_MOSART_SGLC_SWAV
compset running at 1 degree with a 0.25degree SST from Reynolds.
@ekluzek ekluzek self-assigned this Apr 3, 2020
@ekluzek ekluzek added the investigation Needs to be verified and more investigation into what's going on. label Apr 3, 2020
@ekluzek
Copy link
Collaborator

ekluzek commented Apr 3, 2020

@olyson can you take a look at this and let us know if you see the same thing? Is there something different about how 2015 is handled in the ndep script?

@dlawrenncar
Copy link
Contributor

dlawrenncar commented Apr 3, 2020 via email

@ekluzek
Copy link
Collaborator

ekluzek commented Apr 3, 2020

Doing an ncdump -h on the file indicates that @dlawrenncar is correct:

// global attributes:
:Conventions = "CF-1.0" ;
:source = "CAM" ;
:case = "b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.001\n",
"b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.002\n",
"b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.003" ;
:logname = "cmip6" ;
:host = "cheyenne1" ;
:initial_file = "b.e21.BW1850.f09_g17.CMIP6-piControl.001.cam.i.0056-01-01-00000.nc" ;
:topography_file = "/glade/p/cesmdata/cseg/inputdata/atm/cam/topo/fv_0.9x1.25_nc3000_Nsw042_Nrs008_Co060_Fi001_ZR_sgh30_24km_GRNL_c170103.nc" ;
:model_doi_url = "https://doi.org/10.5065/D67H1H0V" ;
:time_period_freq = "month_1" ;
:history = "Mon Oct 7 15:59:37 2019: ncrcat /glade/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata/fndep_clm_hist_b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.ensmean_1849-2013_monthly_0.9x1.25_c191007.nc /glade/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata/fndep_clm_SSP585_b.e21.BWSSP585cmip6.f09_g17.CMIP6-SSP5-8.5-WACCM.001_2014-2101_monthly_0.9x1.25_c190211.nc /glade/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata/fndep_clm_f09_g17.CMIP6-SSP5-8.5-WACCM_1849-2101_monthly_c191007.nc\n",
"Mon Oct 7 14:59:00 2019: ncks -d time,0,1979 /glade/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata/fndep_clm_hist_b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.ensmean_1849-2015_monthly_0.9x1.25_c180926.nc /glade/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata/fndep_clm_hist_b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.ensmean_1849-2013_monthly_0.9x1.25_c191007.nc\n",
"" ;
:NCO = "netCDF Operators version 4.7.9 (Homepage = http://nco.sf.net, Code = http://github.com/nco/nco)" ;
:nco_openmp_thread_number = 1 ;
:source_data = "\n",
"Ensemble mean of linearly interpolated 5 year averages of CAM output from cases:\n",
" b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.001\n",
" b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.002\n",
" b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.003\n",
"Years 1850 to 2014" ;
:creation_date = "\n",
"Wed Sep 26 12:11:25 MDT 2018" ;
:cesm_contact = "\n",
"Keith Oleson, NCAR CGD, oleson@ucar.edu" ;
:data_script = "\n",
"Converted from data_source_files by program CreateNDepFile_Task5B.ncl\n",
"path: /glade/u/home/oleson/misc_programs/CLM5Dev/CMIP6" ;
:comment = "1849 and 1850 data are from 1850 WACCM simulation (b.e21.BW1850.f09_g17.CMIP6-piControl.001; file is /gpfs/fs1/p/cesmdata/cseg/inputdata/lnd/clm2/ndepdata/fndep_clm_WACCM6_CMIP6piControl001_y21-50avg_1850monthly_0.95x1.25_c180802.nc), 1851 and 1852 are the 1850-1854 average, 2012, 2013, 2014 are the 2010-2014 average, 2015 is also 2010-2014 average" ;

@ekluzek
Copy link
Collaborator

ekluzek commented Apr 3, 2020

The suggestion I had for @timhoar was to cycle over the 2015 data for his "present-day" cases.

I assume there must not be three ensemble members for the SSP cases then right? Or have they been run since this file was created?

@klindsay28
Copy link

The SSP5-8.5 file metadata has the comment:

2014 data is from year 2014 of WACCM ensemble member #1 historical simulation (b.e21.BWHIST.f09_g17.CMIP6-historical-WACCM.001), 2015, 2016, 2017 are the 2015-2019 average, 2098 and 2099 are interpolated between the 2095-2099 average and 2100, and 2100 and 2101 are the same as 2100

@olyson and I discussed different options of creating this dataset from the single WACCM SSP run. In the end, we decided to live with a jump going from historical to SSP.

@olyson
Copy link
Contributor

olyson commented Apr 3, 2020

While I was formulating a response, comments rolled in, all of which are correct.

@wwieder
Copy link
Contributor

wwieder commented Apr 3, 2020 via email

@klindsay28
Copy link

For what it's worth, I needed a similar dataset for forcing OMIP runs for 2015-2018. I did what @ekluzek suggests, cycle the last year of the historical forcing for the last few years.

@ekluzek ekluzek changed the title nitrogen deposition files from the SSP scenarios nitrogen deposition files from the SSP scenarios have a noticeable "jump" from the historical period at 2015 Apr 3, 2020
@ekluzek
Copy link
Collaborator

ekluzek commented Apr 3, 2020

OK, it sounds like this an issue that was looked at and decided there wasn't a way around it. So I'll close it in a bit. But, I'll leave it around a bit for discussion. Feel free to add to the discussion even after I've closed it.

@timhoar
Copy link
Author

timhoar commented Apr 3, 2020 via email

@ekluzek ekluzek added the closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix label Apr 4, 2020
@ekluzek
Copy link
Collaborator

ekluzek commented Apr 5, 2020

@timhoar @danicalombardozzi ran the TRENDY simulations for this year. I looked up her cases and see the ndep file for that simulation here:

/glade/p/cgd/tss/people/dll/TRENDY2019_Forcing/Ndep/TRENDY2019_Ndep_Monthly_c190821.nc

From looking at the meta-data on it, I don't see any new data post 2015. So it seems unlikely to help.

@ekluzek ekluzek closed this as completed Apr 7, 2020
@danicalombardozzi
Copy link
Contributor

@ekluzek The 2019 TRENDY N dep file goes through 2099. I had to create this from the data that the TRENDY project provided, which was from CESM1 simulations. @timhoar Given that these are derived from an older version of CESM, I'm not sure it's what you want to use. The file that I created for the TRENDY simulations is here: /glade/p/cgd/tss/people/dll/TRENDY2019_Forcing/Ndep/TRENDY2019_Ndep_Monthly_c190821.nc

@timhoar
Copy link
Author

timhoar commented Apr 8, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ekluzek ekluzek

Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix investigation Needs to be verified and more investigation into what's going on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@wwieder @ekluzek @timhoar @klindsay28 @olyson @dlawrenncar @danicalombardozzi