Changes between Version 53 and Version 54 of RoseCylc/Hints


Ignore:
Timestamp:
03/05/17 21:10:22 (3 years ago)
Author:
annette
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • RoseCylc/Hints

    v53 v54  
    474474 
    475475This is because rose is running a command called `rose host-select` to chose a machine to submit the suite to, and this command needs to know your ARCHER username. To set this follow these instructions: http://cms.ncas.ac.uk/wiki/RoseCylc/Hints#Settinguprosehost-selectarcher 
     476 
     477=== Unable to access STASHmaster from branch on ARCHER ===  
     478 
     479Some suites may reference files held in the repository for use at runtime. The most common example of this is the STASHmaster file. To make a change to the STASHmaster file requires editing the file in a branch and setting the path to this in the suite. However the method described in the instructions below will not work on ARCHER:  
     480 
     481https://code.metoffice.gov.uk/doc/um/latest/um-training/stashmaster.html 
     482 
     483You will get an error like: 
     484{{{ 
     485[FAIL] file:STASHmaster=source=fcm:um.xm_tr/rose-meta/um-atmos/HEAD/etc/stash/STASHmaster@31236: bad or missing value 
     486Received signal ERR 
     487}}} 
     488 
     489This is because the job tries to access the repository from the ARCHER queues, which will not work. Note this will work on the XCS machines, so if you are porting a suite, it may have something like this in.  
     490 
     491The solution is to make the suite extract the file on PUMA and then copy over to ARCHER with the other suite files.  
     492 
     493You will have a line in `app/um/rose-app.conf` such as:  
     494{{{ 
     495[file:STASHmaster] 
     496source=fcm:um.xm_tr/rose-meta/um-atmos/HEAD/etc/stash/STASHmaster@31236 
     497}}} 
     498 
     499This should be removed, and the following added to the `rose-suite.conf` file:  
     500{{{ 
     501[file:app/um/file/STASHmaster]  
     502source=fcm:um.xm_tr/rose-meta/um-atmos/HEAD/etc/stash/STASHmaster@31236 
     503}}} 
     504 
     505 
     506Note the `source=` line is identical but the target `[file:]` line needs to reflect the intended location in the suite directory structure.  
     507 
     508This will extract the file on PUMA and install it to the `app/um` directory on ARCHER which will have exactly the same affect as extracting on ARCHER directly would have done.  
     509 
     510This method will work for any similar files.