1 / 10

Integrated H IRLAM system

Integrated H IRLAM system. Compilation System Run ECMWF Local installation Browsing cvs : trunk, releases, etc . Naming conventions HL  Arome/IFS. Compilation. Export CVSROOT e.g . at ECMWF: CVSROOT=~nkg/cvsroot cd some_experiment_directory cvs co hirlam cd hirlam gmake.

bian
Download Presentation

Integrated H IRLAM system

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrated HIRLAM system • Compilation • System • Run • ECMWF • Local installation • Browsing • cvs: trunk, releases, etc. Naming conventions HL  Arome/IFS

  2. Compilation Export CVSROOT e.g. at ECMWF: CVSROOT=~nkg/cvsroot cd some_experiment_directory cvs co hirlam cd hirlam gmake

  3. System • Principle: • Mini-SMS controls compilation/linking/execution: overlap compilation with e.g. climate and boundary generation • At ECMWF (and hence local) separate sandbox, on $TEMP, from user mods (on $HOME). • Status: • β-test-releases, to end in β-rel 6.4.1, Sep 05 • No PrepareLibs yet

  4. Run • Set up (revision, architecture, repository, user): • Hirlam setup [ –r n1.n2.n3 ] • Run • Hirlam start DTG=…

  5. ECMWF • Parallellisation: -j8 • 8 minutes / 9 s ET (1st / later) • Overlaps with climate and LBC preparations

  6. Local installation • Access to sources (the “repository”): either • CVSROOT on the HeXnet server • cvs administrator must add your “public key”, usercode/password • cvs login • Copy repository from the HeXnet server to local • Faster local access (but not by much) • cvs administrator must add your “public key” • “mirroring” possible (an application: ECMWF repository) • Either, with CVSROOT at ECMWF • Need access to ECMWF and member of group hirlam • Updated around midnight (in yellow: if only to build the executables; in white: to use the Hirlam system for that) • Create configuration files config.$ARCHand config-sh.$HOST • Copy and install script Hirlam and add to submission.db • cvs, gmakeetc.

  7. Browsing

  8. Documentation hirlam  htdocs  Integrated  index.html  download : 1 To learn about how to access the system, read this separate document. 2 To set up and run a simple HIRLAM experiment, read this separate document. 3 To learn how to install the HIRLAM system, read this separate document.

  9. Trunk, head, releases, merging, andnew releases

  10. Naming conventions HL  Arome/IFS • HL (case sensitive!): • HLes, HLaplpar, HLaconds, HLcloud • Where doctor etc prescribes initial characters: • yHLbasicPhys.F90 • yHLconv.F90 • yHLrad.F90 • yHLturb.F90 • suHLdef.F90 or HLsudef.F90? • suHLbasicPhys (HLsubasicPhys.F90?)

More Related