Changes between Initial Version and Version 1 of Ticket #680


Ignore:
Timestamp:
08/19/15 22:07:35 (10 years ago)
Author:
arango
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #680

    • Property Resolution → Done
    • Property Status new → closed

  • Ticket #680 – Description

    initial v1  
    11'''STATIONS''':
    22
    3 The routine '''read_stapar.F''' that reads the station input script ('''stations.in''') was updated so the CPP option '''STATIONS''' is more robust across nested grids.  Only one '''stations.in''' is needed in nested applications.  As in '''ocean.in''', we just need to use the plural symbol '''==''' after the '''KEYWORD''' for nested grids parameters.
    4 
    5 For example, in a four nested grid application we can have:
     3The routine '''read_stapar.F''' that reads the stations input script ('''stations.in''') was updated so the CPP option '''STATIONS''' is more robust across nested grids.  Only one '''stations.in''' input script is needed in nested applications.  As in '''ocean.in''', we just need to use the plural symbol '''==''' after the '''KEYWORD''' for relevant nested grids parameters.
     4
     5For example, in a four nested grids application we can have:
    66
    77{{{
    … …  
    145145}}}
    146146
    147 Users need to pay attention to all the above parameters.  In particular, '''Lstations''', '''NSTATION''', and '''POS'''.
     147Users need to pay attention to all the above parameters.  In particular: '''Lstations''', '''NSTATION''', and '''POS'''.
    148148
    149149----
    … …  
    151151'''FLOATS''':
    152152
    153 Similarly, one '''floats.in''' is need in nested applications when the CPP option '''FLOATS''' is activated.  Currently, the floats trajectories are independent of each nested grid.  That is, once that the trajectory exit a particular grid it will not continue into the other nested grids.
    154 
    155 As mentioned above, we just need to use the plural symbol '''==''' after the '''KEYWORD''' for nested grids parameters.  For example, in a four nested grid application we can have:
     153Similarly, one '''floats.in''' is need in nested applications when the CPP option '''FLOATS''' is activated.  Currently, the floats trajectories are independent of each nested grid.  That is, once that the trajectory exit a particular grid it will not continue into the other nested grids. We will figure out in the future how to allow this but it is not high in our priority list.
     154
     155As mentioned above, we just need to use the plural symbol '''==''' after the '''KEYWORD''' for nested grids parameters.  For example, in a four nested grids application we can have:
    156156
    157157{{{