Comments (7)
The repos are now being backed up at NCAR. We need to check that the data is available and usable, should we need it. My understanding is that the "metadata" (wikis?) is not yet backed up.
from cice.
@dabail10 @duvivier Please, could you get an update on the status of the backups? What is being backed up, how often, and how to we access them should the need arise. Thx
from cice.
@eclare108213 @dabail10 and I checked today on this.
The following CICE-Consortium master repositories and wikis are backed up:
CICE, Icepack, Test-Results
The backups are done 3x day at 6am, noon, and 6pm. At midnight the backups become daily and remain become monthly after a month. These are stored for 2 years at which point we only keep a backup for things up to 2 years old and anything older is scrubbed.
We are able to look at these through an internal CGD webpage. If the need arises (hopefully it never does!) we can just get the most recent backed up version and import it into github as a brand new repository. Mark last tested this about 2 months ago to verify that the process was working properly, though I just checked the internal website today and could see actively backed up files.
There is not yet any backup of metadata (PR, Issues, checkouts/checkins). Mark is working on this because we want metrics for CESM and these same sorts of metrics would be useful for the Consortium as well. As of now there isn't a set date for this to be completed.
I think we still have a bit of research/digging to do to figure out more about how the release tags etc. are stored. I will follow up.
@dabail10 , If you have more to add feel free.
from cice.
@eclare108213
I'm keeping this on the front burner here. We had some issues with this being done correctly. We're at the point where metadata and branches are being saved. However, it looks like Tags aren't being saved yet, which I think is imperative since these are essentially the releases. Mark Moore is working on it this week and has made progress but it isn't complete yet.
from cice.
from cice.
I tested this today with Mark Moore and Alice Bertini. From the code backed up on the cgd server I tested restoring the repo to a dummy repo I created for Icepack. I was successfully able to restore the master branch, all additional branches, tags, and the wikis. I could look at the history of the master branch (merges, commits, etc.)
I think this is all the really important info we need. We weren't able to restore, to my dummy repo, the issues and pull requests to the nicely formatted manner they are in on github. However, they were saved as well as the repository history and you can look through them if necessary and use the repo history to find an issue or PR.
So I'm going to go ahead and close this. I think it'll all taken care of and has been tested for verification that the code is restorable and will build and run.
from cice.
Thank you!
from cice.
Related Issues (20)
- ice_in variables undefined in chapter 5 of docs HOT 4
- shortwave dEdd_snicar_ad setup HOT 10
- grid_location is missing for C and CD grids for call to seabed_stress_factor_LKD HOT 1
- model abort due to dvice negative HOT 11
- Investigate T-Test in cice.t-test.py
- NLON, ELAT not computed when TLAT, TLON, ANGLET on grid file HOT 14
- Some CMIP variables are computed using a mix of U and T quantities HOT 1
- dxT and other grid length variables
- dsnow optional argument in icepack_step_therm1 HOT 2
- evp1d performance evaluation
- Support netcdf-4 compression & chunking HOT 1
- hist_avg on multiple streams writes the same filenames when .false. HOT 9
- Potential instability related to explicit treatment of Coriolis for C-grid HOT 3
- Arguments in update_state need if present. HOT 2
- dynamics U points are active when T points are not HOT 5
- Commit/PR process HOT 3
- PIO and hdf5 failures HOT 4
- Test various restart formats and add Derecho port that uses pio spack HOT 1
- tripole initial/restart file with inconsistent values on the tripole seam HOT 15
- CICE C-grid crash on 1/12 degree tripole HOT 11
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 cice.