Comments (9)
Each PISM release is now archived at Zenodo? Nice! (Maybe this is proposed only.) The release info at https://github.com/pism/pism/releases will/should contain a Zenodo link?
from pism.
I see that the zenodo links already exist. The release statements should contain these too, right?
from pism.
Each PISM release is now archived at Zenodo? Nice!
Yes, starting from 2.0.
The release statements should contain these too, right?
Hmm. I'm not sure. The DOI for a particular release does not exist when release notes get written, so this would require manually updating release notes after Zenodo generates the DOI. It's not hard, but I don't know if it's necessary.
from pism.
Zenodo DOIs lead to a .zip snapshot of the source, which (I think) we would want to discourage for almost all users. (In theory there is someone who wants to reproduce a result and never use PISM again?) Presumably support is better if people are getting versions from git. How about just the root zenodo DOI at the end of each release statement?: "Follow https://doi.org/10.5281/zenodo.1199019 to the zenodo DOI for this release."
from pism.
I don't really think the invention of zenodo helps humanity very much. Just putting repository urls into publications, and stating version tags, is much more effective for actual "reproducibility" purposes. But you are dealing with zenodo as it is. 😄
from pism.
Zenodo DOIs lead to a .zip snapshot of the source, which (I think) we would want to discourage for almost all users.
I don't have a problem with using .zip
archives from Zenodo to install PISM. (This reminds me that I need to make a small change to ensure that PISM version info is properly recorded in this .zip
and binaries built using sources in it.)
How about just the root zenodo DOI at the end of each release statement?: "Follow https://doi.org/10.5281/zenodo.1199019 to the zenodo DOI for this release."
Sure!
Just putting repository urls into publications, and stating version tags, is much more effective for actual "reproducibility" purposes.
I disagree.
- Zenodo is backed by CERN and is likely to outlast an average repository. (Recall that Gna! is down and an URL pointing to it is useless.)
- Unlike URLs and version tags, DOIs correspond to immutable snapshots. This immutability is also backed by an authority or at least a third party, which I think is great. (Even if a repository still exists, there is no guarantee that its contents did not change. Version tags can be deleted or rewritten.)
Just the other day I spent way too much time fixing URLs pointing to UMT's SeaRISE wiki and P. Huybrechts' old web page. Luckily the SeaRISE wiki is now archived on Zenodo, but I have to rely on web.archive.org to maintain our EISMINT and ISMIP-related stuff. I wish I didn't.
I wish the GitHub-Zenodo integration setup archived a snapshot of the repository including commit history up to the tag corresponding to a release (instead of a snapshot of the contents of a repository), but that's a minor thing.
from pism.
@ckhroulev That makes sense. I guess I thought that helping users running from a .zip was an issue, but in practice I guess it is not. I am confident github will last a lot longer than GNA. 😜
from pism.
@bueler To add to the confusion: the name "Gna!" and the domain gna.org
got recycled.
from pism.
@ckhroulev Yikes! "How the mighty have fallen!" would hardly fit ... gna was never mighty.
from pism.
Related Issues (20)
- SSAFD KSP (linear solver) failed HOT 2
- Conservative regridding (averaging) for 2D fields HOT 1
- Put projection info into files HOT 1
- Building user manual with Sphinx >= 5.0 fails with 'language = None'
- Black-hole calving HOT 15
- Unable to read from a compressed NetCDF file with permuted dimensions HOT 1
- Bed deformation models need to use the load averaged over the duration of a time step HOT 3
- Antarctic example has a reprojection error HOT 1
- Error building pism 2.1 since switch to pkg-conf HOT 4
- no difference between ncap scripts in doc/sphinx/manual/practical-usage/conservation HOT 2
- Use of "0001-1-1" as reference year instead of "1-1-1" for compatibility with Xarray HOT 1
- PISM's continous integration setup should include tests that use PETSc --with-64bit-indices HOT 1
- Is PISM able to do global simulation? HOT 3
- Add "tendency_of_ice_mass_due_to_grounding_line_flux"
- PETSc 3.21 compatibility
- Improve instructions describing how to cite PISM
- Fix PISM installation instructions for macOS
- Consider using `kelvin` instead if `Kelvin` for units HOT 4
- Goldsby (2006) rheology
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pism.