Recent Changes

Sunday, September 16

  1. page Data publishing guidelines edited ... The JGR-Space Physics editor-in-chief has listed some of these challenges and clarified the sc…
    ...
    The JGR-Space Physics editor-in-chief has listed some of these challenges and clarified the scope of the policy on his blog. This include references to model data which apply to lots of the ARCCSS data as well.
    How to publish
    ...
    metadata. This isinclude a work in progressgeonetwork catalogue to describe your dates (i.e. a metadata repository) and when they will be in production mode we'll list them here.
    We are working with them
    provide links to provideother description and to the dataset access point. Once you have a waygeonetwork record, NCI can mint a DOI for the dataset, as for papers a DOI makes the dataset easy to cite.
    The files can be made accessible
    to publish also smaller datasets through this services.
    In
    the meantime we canpublic by using their TDS catalogue or thredds.
    We also
    create a
    ...
    by ANDS. Once you have a record onWe do this because RDA has more visibility then the journal will be satisfied that readers canNCI catalogue, including being harvested by the new google dataset search toolbox. All these records are referencing each other so no matter where a user find all the necessary information about your data. The record it will also contain information on how to access the data, this will be a direct linkalways get to the same DOI, data itself once the data is published on a repositoryaccess point and a contact to obtain the data in the meantime.information.
    There a few necessary steps to make your data available:
    move the data to a new directory under /g/data1/ua8: this disk space started as a storage for ERA Interim, but it is now dedicated to ARCCSS shared datasets;
    get the dataset to a good quality level, necessary to share it successfully: metadata in the files should satisfy CF conventions, there should be a READ-ME file or some data description sitting with the data and both directory structure and filenames should be understandable and contains information on the data. It sounds more difficult that normally it is, once you moved the data I'll have a look and tell you if there's anything which needs to be done

    Create a data management plan for your collection using the ARCCSS DMPonline tool, if you don't have one already. If you do make sure to have filled in the third phase of the plan which deals with the publishing details. You then should share the plan with me when you're ready (share with paola.petrelli@utas.edu.au). I use the dmp to collect the necessary information to create a metadata record on RDA on your behalf. You can look at one of ARCCSS records as an example of the kind of information required.
    We will use the information on the plan to automatically generate the NCI and RDA records and a directory in /g/data/ua8/ARCCSS_Data/<your-dataset> which will contained also a draft for a readme file and the license attached to the data.
    move the data to the your dataset directory: /g/data/ua8/ARCCSS_Data/<your-dataset>/tmp .
    get the dataset to a good quality level, necessary to share it successfully: metadata in the files should satisfy CF conventions, there should be a READ-ME file or some data description sitting with the data and both directory structure and filenames should be understandable and contains information on the data. It sounds more difficult that normally it is, once you moved the data I'll have a look and tell you if there's anything which needs to be done.
    Once the files are ready we will ask NCI to run their QA/QC checker on them, if they pass these quality checks the dataset is added to the thredds catalogue and the metadata records are updated.
    Other advice:

    Think carefully about the license and rights terms, you'll find some options on the form itself, contact me if there are other collaborators involved or any other special terms to be kept into account, the license will be virtually null if either the ARCCSS and/or your university don't hold the copyright.
    if you don't have one already to make a ORCID http://orcid.org/ identity which we can list in the record as well. In the future you might be able to reference all your work through a researcher identity, when applying for a grant.
    The above steps, don't needgive some thought to be executed in the listed order, in particular we can start working on the RDA record before your dataset has undergone proper curation. Sowhat you can go ahead with submittingwant to publish, as well as satisfying the paper, ideally though the data should be readyjournal requirements, you want to make sure to include anything that could be shared beforeuseful to other researchers. This will increase the value of your paper is published.data and potentially get more people to cite you. Look here for guidelines.
    Managing your data is an essential part of the publishing process for more detailed information go to the Data management induction training
    I'm still working on this page and the DMPonline tool, any feedback on both is welcome!
    (view changes)
    6:29 pm

Sunday, September 9

  1. page ARCCSS induction edited ... Monash holger.wolff@monash.edu Danny Eisenberg UNSW d.eisenberg@unsw.edu.au (Note: ther…
    ...
    Monash
    holger.wolff@monash.edu
    Danny Eisenberg
    UNSW
    d.eisenberg@unsw.edu.au

    (Note: there is no typo, Claire is sitting at ANU but has a UNSW email address).
    Although we won't ignore emails sent to our individual addresses, our preferred way of contact is through our help desk email address: climate_help@nf.nci.org.au. Contacting the help desk will make sure your email is seen by one of us in case the person at your institution is away for example. Don't worry about the help desk email being an NCI account, you can still ask any question there.
    (view changes)
    10:12 pm
  2. page news edited ... /g/data1/rr7/ana4MIPs/reanalysis/JRA/JRA55 to /g/data1/rr7/JRA55 CMS Training Talks 3D Vi…
    ...
    /g/data1/rr7/ana4MIPs/reanalysis/JRA/JRA55 to
    /g/data1/rr7/JRA55
    CMS Training Talks
    3D Visualisation - Martin Jucker, UNSW https://youtu.be/ya-xXY5uzeo
    Nectar Research Cloud - Just Berkhout, TPAC https://youtu.be/8jluqwOOS0U
    (view changes)
    9:15 pm
  3. page news edited ... /g/data1/rr7/ana4MIPs/reanalysis/JRA/JRA55 to /g/data1/rr7/JRA55 CMS Training Talks 3D Vis…
    ...
    /g/data1/rr7/ana4MIPs/reanalysis/JRA/JRA55 to
    /g/data1/rr7/JRA55
    CMS Training Talks
    3D Visualisation - Martin Jucker, UNSW https://youtu.be/ya-xXY5uzeo
    Nectar Research Cloud - Just Berkhout, TPAC https://youtu.be/8jluqwOOS0U

    2018-08-01
    New blog
    (view changes)
    9:15 pm

Wednesday, September 5

  1. page sealevel_GLO_PHY_L4_REP_observations_008_047 edited ... On raijin This dataset is available in the ua8 project: /g/data/ua8/CMEMS_SeaLevel/v3-0/<…
    ...
    On raijin
    This dataset is available in the ua8 project:
    /g/data/ua8/CMEMS_SeaLevel/v3-0/<year>/<files>/g/data/ua8/CMEMS_SeaLevel/<version>/<year>/<files>
    v4-0 is the most recent version

    Filenames are:
    dt_global_allsat_phy_l4_YYYYMMDD_<production_date>.nc
    (view changes)
    9:41 pm
  2. page news edited CMEMS-sea level v4.0 There's a new version 4.0 available for CMEMS-sea level (previously known …

    CMEMS-sea level v4.0
    There's a new version 4.0 available for CMEMS-sea level (previously known as AVISO). For more info see the relevant wiki page

    JRA55 moving on Monday 13th August
    We are going to move JRA55 (not JRA55-do!!!) 6hr and day data, from
    (view changes)
    9:39 pm

Monday, September 3

  1. page WRF v3.9 installation edited ... Go to the WPS/ subdirectory, run: cd /short/$PROJECT/$USER/WRF/WPS/ ... choose the config…
    ...
    Go to the WPS/ subdirectory, run:
    cd /short/$PROJECT/$USER/WRF/WPS/
    ...
    choose the configure input to the configure script from the
    ...
    well as to cleancleaning a previous
    ./run_compile -h
    To configure and compile WPS with the default options, you simply run:
    (view changes)
    9:03 pm
  2. page WRF v3.9 installation edited ... git clone -b V3.9 git@github.com:coecms/WRF.git Building WRF (ARW)Building WRF (ARW) By def…
    ...
    git clone -b V3.9 git@github.com:coecms/WRF.git
    Building WRF (ARW)Building WRF (ARW)
    By default, WRF will output files in netcdf 3 format. If you would like to directly output files in netcdf 4 format with compression, you need to edit the file WRF/build.env before compilation. Note if you are planning to generate very frequent outputs, this will significantly slow down your simulation. You could be better off compressing the outputs afterwards but please don't forget to compress your data.
    Go to the WRFV3/ subdirectory, run:
    cd /short/$PROJECT/$USER/WRF/WRFV3/
    ...
    csh/tcsh syntax:
    alias my_compile 'run_compile --compile_case <replace with the compile option here>'
    Tip: run_compile is sourcing the environment as defined in WRF/build.env. Feel free to change the versions of software you want to use in here. Note the module purge at the start. This means your currently loaded environment will be completely ignored.
    Debugging with WRF
    If you want to compile WRF for debugging, the default option for compilation is not valid because it includes some optimisation. You'll need to use one of the first four architecture options. For example, to debug with the distributed memory only option (dmpar):
    (view changes)
    9:00 pm

More