Research data supporting 'Coupled modelling of subglacial hydrology and calving-front melting at Store Glacier, West Greenland'

Numerical model outputs from my PhD (titled: Will fast glaciers accelerate under climate change?) and the RESPONDER project that form the basis of the figures and data in the associated publication. Data provided as .tar.gz archives containing several thousand .vtu and .pvtu files. The .pvtu and .vtu files are outputs from the numerical finite-element model, Elmer/Ice, set up to model the evolution of the subglacial hydrology of Store Glacier, a tidewater glacier in western Greenland. Information about Elmer/Ice can be found here: http://elmerice.elmerfem.org/ and I hope to have all the code I used uploaded to the main Elmer/Ice repository soon (in the meantime, please contact me if you're interested in the code). The model outputs are grouped into six .tar.gz archives, all representing three months of model time. Each archive contains three sets of files: PostCalve files are output for the ice mesh; Hydro files are outputs for the hydrology mesh (conceptually, at the base of the ice mesh) and channel files are the channel elements on the hydrology mesh (because the channels are complicated). One archive (WinterToUpload) contains the results for a representative winter scenario (no surface melt, only basal and internal melt). Two (Summer12Steady and Summer17Steady) contain results for the summers (Jun-Jul-Aug) of 2012 (high surface melt) and 2017 (low surface melt), respectively, forced using constant average surface melt derived from the regional climate model, RACMO. Two more (Summer12Daily and Summer17Daily) model the same periods, but use daily-resolution surface melt from RACMO to explore whether this more realistic method of forcing really impacts the model results (in some ways it does, in other, it doesn't). Finally, Summer12MT is identical to Summer12Steady, except the mesh resolution is coarser, to check whether that significantly impacts the results (it doesn't). When looking at the results in Paraview, just load in the .pvtu files - they reference the appropriate .vtu files. You only need to worry about individual .vtu files if you want to look at one specific mesh partition at one timestep.