Coder Social home page Coder Social logo

esmvalgroup / esmvaltool-ar6-originalcode-finalfigures Goto Github PK

View Code? Open in Web Editor NEW
2.0 2.0 6.0 200.48 MB

Original ESMValTool code used to produce IPCC figures. This repository will be made public shortly after the publication of the IPCC report

License: Apache License 2.0

NCL 4.18% Python 0.45% Jupyter Notebook 95.37%

esmvaltool-ar6-originalcode-finalfigures's People

Contributors

bettina-gier avatar chaincy-cal avatar chaincy-ipcc avatar ipcc-wgi avatar ledm avatar lisabock avatar malininae avatar mwjury avatar remi-kazeroni avatar valeriupredoi avatar yteunicelo avatar yukosaka avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

esmvaltool-ar6-originalcode-finalfigures's Issues

Info on Nathan's figures in ar6_chapter_3

Here is the stage 1 of Nathan's code submission. The figures are 3.7-8 as well as .csv file, which was used by TSU to create FAQ 3.1 FIgure 1 and SPM Figure 1, panel (b).

What about WG2 or WG3?

All of our naming standards are assuming we're working in AR6 WG1. Do we need to explicitly allow for future assessment reports and other working groups?

Created README_AR6_WG1_Chap3_Figure_3_10_vertical_temp.md

This is the README for Chapter 3 Figure 3.10. It is named README_AR6_WG1_Chap3_Figure_3_10_vertical_temp.md.

Note the figure number was originally 3.9, so the relevant branches are still named ar6_chap_3_fig_3_9 and info_on_ar6_chap_3_fig_3_9. I hope this is OK and does not cause confusion, and I am sorry if it does. Please rename them for me if you see fit.

Uploading the IPCC figures

Hi @LisaBock, @ledm,
It seems that we now ask the contributors to upload a copy of their final IPCC figures in this repository. I would like to edit the instructions to state this clearly and create an images directory so that we IPCC contributors would know where to upload the figures after doing git clone of this repository. Note that once we will merge all the info_on_branch, we will have all the figures collected in a directory. Does this work for you?

Creation of development_ar6_chap_3_ocean branches

I did most of my code development for IPCC AR6 Chap 3 in a single branch called: development_ar6_chap_3_ocean.

This code covers four figures:

  • Atlantic Meridional Overturning Current (figure 3.XX )
  • Ocean Heat Content (figure 3.XX )
  • Halosteric Sea Level Rise (figure 3.XX )
  • Global Sea Surface Salinity trends (figure 3.XX )

@LisaBock, can you confirm what the final figure numbers were?

I've created this branch following the instructions in Contributing.md.

I've added two branches to this code:

  • ar6_chap_3_ocean
  • info_on_development_ar6_chap_3_ocean

Where the ESMValTool code is in ar6_chap_3_ocean, the conda & pip environments and the README's are in info_on_development_ar6_chap_3_ocean.

Before completing step 1: I have the following tasks remaining:

  • Split the readme into four separate files.
  • Figure out what the final image numbers were for these figures.
  • Bring in the auxiliary data somewhere.
  • Prune away some of the more unnecessary files.
  • Create a pull request. not sure that I want to do this yet though, it's a scary task!
  • Create a zenodo citation

Step 2 is a whole other thing, and I'm holding off doing that in the short term.

Info on ar6 chapter 10 figures

New issue opened on Chapter 10 figures as indicated in the manual.
This pull request concerns the READMEs and figure images for Fig. 10.6, 10.9, 10.10, 10.11, 10.12, 10.13, 10.18, 10.19, 10.20, 10.21, CB10.3 Fig 1., CCB10.4 Fig 1.

Extra branch for README and environments?

Hi @remi-kazeroni @ledm @valeriupredoi,

it is unclear to me why we should store the READMEs and the environment files in another branch than in the branch with the ESMValTool code? Is there are special reason?
I have the feeling that this leads to a confusion of all the branches.
Is there are possibility just to add the IPCC_README_files and the IPCC_environments folder to the ESMValTool directory?

Cheers,
Lisa

Can we make the README template a bit better?

Hi,

I'd like to suggest a few changes to make the README a bit better? I'll put this in a PR in a minute. Here are some ideas:

  • It would be nice if we made better use of the markup environment and style in the template.
  • Change the name of IPCC_README_File/README.md to IPCC_README_File/README_template.md
  • Change the contents of the README template to exclude the header parts.
  • Change the content of the template to something like:
FIGURE TITLE
============

Figure number(s): e.g. Figure 3.3

Description:
------------
Please describe the figure . 

Author list:
------------
-  Author, A: Institute, contact email (lead only) github ID 
-   Author, B: Institute,
-


Publication sources:
--------------------
Please list any publications that describe, explain or use this figure. 

ESMValTool Branch:
------------------
- ESMValTool-AR6-OriginalCode-FinalFigures: ar6_chap_3_Fig_03


ESMValCore Branch:
------------------
- ESMValCore-AR6-OriginalCode-FinalFigures: ar6_Core_changes


Recipe & diagnostics:
---------------------
Recipe(s) used: e.g. recipes/ipccar6wg1ch3/recipe_eyring21ipcc_3-3-ocean.yml
Please describe this recipe:

Diagnostic(s) used: e.g. diag_scripts/ipcc_ar6/tsline.ncl
Please describe this diagnostic. 


Recipe generations tools: 
-------------------------
Were any tools used to populate the recipe? if so what were they? N/A if not applicable. 


Ancillary figures and datasets:
-------------------------------
In addition to the main figure, diagnostics may produce several figures and datasets along the way or several versions of the main figure. Please use this space to highlight anything that may be useful for future iterations:


Additional datasets:
--------------------
What additional datasets were used to produce this figure?
Where are they on the computational machine or in the respository?
Can they be re-created?
What are their access permissions/Licenses?


Software description:
---------------------
Software versions, name of environment file (see **save conda environment** in CONTRIBUTING.md), other software packages,โ€ฆ
- ESMValTool environment file: e.g. IPCC_environments/$NAME_conda_environment.yml
- pip file: e.g. IPCC_environments/$NAME_pip_environment.txt
- Other software used:


Hardware description:
---------------------
What machine was used:  e.g. Mistral or Jasmin
When was this machine used?


Any further instructions: 
-------------------------




When do we publish this code?

What is the plan to publish this code? The repository says that it will be made available shortly after the AR6 WG1 report is published, but that was several months ago.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.