Search results

Jump to navigation Jump to search
  • = Output from GLAM = == Selecting output from GLAM ==
    3 KB (554 words) - 15:42, 1 August 2007
  • ...To do this, it needs to know where the model source code is kept and the output directory. These default to '''~/genie''' and '''~/genie_output''', but ca ...m normal working checkout), the makefiles also have varaibles for the code output directories. All makefile variables can be overridden on the command line,
    1 KB (184 words) - 09:15, 7 June 2007
  • #- output files storing R_SORTIE_OCE=${R_TMP}/output/
    3 KB (475 words) - 11:22, 18 January 2008
  • # [[Input files]] # [[Output files]]
    584 bytes (83 words) - 17:32, 16 November 2007
  • ...er code changes impact on model output. The comparison is based on output files from glam in netcdf format. * make the netcdf output filename a namelist option
    1 KB (210 words) - 14:19, 3 July 2008
  • ...ers on a graph and a globe. When directed to an ALADDIN run directory (the output from a particular run of a GENIE experiment - normally found as a subdirec ...and plot sensible NetCDF output (it currently only works with ascii output files. It will be able to configure and launch mulitple instances of GENIE on rem
    2 KB (321 words) - 09:21, 23 March 2010
  • * You need to control model data output. We recommend the following choices: ** changing the frequency of timeseries output, by setting ea_5, go_5, gs_5 = 100 (to give annual 1 January snapshots)
    3 KB (542 words) - 08:49, 6 March 2008
  • ...nts. We hope that this new method of approaching the organisation of GENIE files will make more sense to new users too. By convention, the normal place for GENIE to output data is a directory outside of the genie source tree, normally at the same
    13 KB (2,019 words) - 09:30, 23 March 2010
  • ...s in your directory (plus the required result files). The meaning of these files is explained [[Run_ESTEL_in_parallel#Note_about_parallel_outputs | further = Note about parallel output =
    7 KB (1,231 words) - 09:37, 7 September 2007
  • ...up parameters for the experiment. This includes pointers to the following files: This is the root name for the climate forcing files. Each should be named metname_year.txt where year is the year of the data
    6 KB (993 words) - 15:29, 31 October 2007
  • ...up parameters for the experiment. This includes pointers to the following files: This is the root name for the climate forcing files. Each should be named metname_year.txt where year is the year of the data
    7 KB (1,045 words) - 18:34, 12 November 2007
  • ===File Output=== ...cause the timestep and flux outputs are calculated at the boundary and the output grid is offset by 0.5*dx for simplified display in GIS packages. It is ther
    6 KB (1,000 words) - 12:28, 17 December 2009
  • ...Glimmer documentation. It can itself reference other Glimmer configuration files, if more than one ice sheet instance is to be run. * <tt>$RUNTIME_OUTDIR</tt>, the main output directory, typically <tt>~/genie_output/$EXPID</tt>.
    4 KB (588 words) - 11:15, 17 February 2009
  • ...y to start the TELEMAC jobs and use the MS Windows environment for editing files etc... See [[General_use_of_the_TELEMAC_system#A_note_about_ASCII_files | n ...figure the environment to use TELEMAC as you simply have to source central files. Simply add the following lines into your .bashrc configuration file, then
    6 KB (1,081 words) - 09:57, 19 September 2008
  • ...' and provide the dir '''~/genie_output''' in which to collect your output files, '''your setup step will be considerably easier.''' ...ts. Since the model has been tested before you downloaded the code, these files are '''assumed''' to be 'good'. Type:
    8 KB (1,256 words) - 09:35, 25 June 2010
  • * Tools used to analyse model output data can use the information supplied in a gridspec to provide more advance * Regridding of model input or output data will be more straightforward, as it will be standards-based rather tha
    10 KB (1,481 words) - 15:28, 2 April 2007
  • ==Example BFG metadata files== Examples of BFG definition, composition and deployment files are discussed below. A description of BFG itself can be found here: [[GENI
    10 KB (1,089 words) - 17:44, 26 February 2007
  • ..._LIM is downloaded through CVS when getting Nemo and the necessary forcing files are provided through a link on the Nemo website or can be copied from ~ggda ...new", check whether it is running using "showq", and obviously look in the output directory.
    13 KB (2,173 words) - 16:02, 8 January 2009
  • ...the THREW model. You may now throw away the cvode-2.5.0/ folder since both files (which are static libraries) contain all the functionality we need. ..., because the frequency of the input data may be higher than the requested output.
    5 KB (779 words) - 20:38, 10 April 2009
  • ...el run, the mode the model is going to be run in, and the input and output files required and generated, respectively. ...l's performance is measured are read in. The names and the format of these files are described in the [[control file]] section. The model is capable of usin
    6 KB (960 words) - 17:12, 9 November 2007

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)