MESMER-OpenSCM Runner
Coupling between MESMER and OpenSCM-Runner.
Installation
Citing MESMER-OpenSCM Runner
Scientific publications using MESMER-OpemSCM Runner should cite the following publications alongside the appropriate global-mean temperature emulator publications:
Beusch, L., Nicholls, Z., Gudmundsson, L., Hauser, M., Meinshausen M., and Seneviratne, S. I.: From emission scenarios to spatially resolved projections with a chain of computationally efficient emulators: MAGICC (v 7.5.1) - MESMER (v 0.8.1) coupling, Geosci. Model Dev. Discuss. [preprint], https://doi.org/10.5194/gmd-2021-252, in review, 2021.
Beusch, L., Gudmundsson, L., and Seneviratne, S. I.: Emulating Earth system model temperatures with MESMER: from global mean temperature trajectories to grid-point-level realizations on land, Earth Syst. Dynam., 11, 139–159, https://doi.org/10.5194/esd-11-139-2020, 2020.
License
Copyright (c) 2021 MESMER-OpenSCM Runner contributors, listed in AUTHORS, and ETH Zurich.
MESMER-OpenSCM Runner is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License (see LICENSE), or (at your option) any later version.
MESMER-OpenSCM Runner is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see <https://www.gnu.org/licenses/>.
The full list of code contributors can be found in AUTHORS or at github.com/MESMER-group/mesmer-openscmrunner/graphs/contributors.
Metadata
Release files for mesmer-openscmrunner 2.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mesmer-openscmrunner-2.0.1.tar.gz | 497.2 kB | Without provenance | Details for mesmer-openscmrunner-2.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mesmer_openscmrunner-2.0.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for mesmer_openscmrunner-2.0.1-py2.py3-none-any.whl |
Total release size: 514.3 kB
Release files / mesmer-openscmrunner-2.0.1.tar.gz
| Download URL | mesmer-openscmrunner-2.0.1.tar.gz |
|---|---|
| Size | 497.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4883c48e67c6e490534c0ee937ac6a2a0cff2861556a8a6a8f66753c03086614
|
|
BLAKE2b-256 checksum How to use checksums |
1c349f69ab94d685a87c0ce6938c050db1d8da75d792cfd8639168edbeec3f25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.10
|
Release files / mesmer_openscmrunner-2.0.1-py2.py3-none-any.whl
| Download URL | mesmer_openscmrunner-2.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 17.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
ad005e2981051e6146682b7a405864603bb609aba948854f8f2b1d92a8142698
|
|
BLAKE2b-256 checksum How to use checksums |
a24d55434e41a3499428cd45287cf79ee9c0256a3779c5e46e0f19f1f116b333
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.10
|
Security for mesmer-openscmrunner 2.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.