Hi everyone,
I'm currently working with a ROMS model setup that includes a main grid and a nested sub-grid. I've encountered an issue where the model only recognizes station information for the main grid and fails to acknowledge the stations designated for the nested grid. Despite various attempts to resolve this, I'm stuck and would greatly appreciate any advice or insights from the community.
NSTATION Setting: I've set the NSTATION parameter in the .in file to reflect the number of stations in each grid, using the format NSTATION == 1 2
Despite the above settings, the model throws the error: READ_StaPar - Inconsistent number of stations, Nstation = 1 0, indicating it does not recognize the stations for the nested grid.
Could anyone please help me understand what might be going wrong or point me toward what I might be missing?
Best regards,
Mark
Issue with Recognizing Stations in Nested Grid Configuration
-
- Posts: 5
- Joined: Thu Jan 04, 2024 3:34 am
- Location: East China Sea Bureau, Ministry of Natural Resourc
Issue with Recognizing Stations in Nested Grid Configuration
- Attachments
-
- stations.in.txt
- (17.46 KiB) Downloaded 132 times
- jivica
- Posts: 172
- Joined: Mon May 05, 2003 2:41 pm
- Location: The University of Western Australia, Perth, Australia
- Contact:
Re: Issue with Recognizing Stations in Nested Grid Configuration
Hi Mark,
having a look into your stations.in I can see the problem is that you put stations only for GRID 1:
NSTATION == 1 2 ! you want to have 1 station in grid 1 (parent) and 2 stations inside a nested grid 2 (child)
POS = GRID FLAG X-POS Y-POS COMMENT
1 1 120.5750 33.7917 ! this is station inside grid 1 (first integer = 1)
1 1 121.4297 32.5227 !yangkougang leida this is still grid 1
If you want to have 1 station for parent and 1 station for child then put something like this:
NSTATION == 1 1
1 1 lon_station_grid1 lat_station_grid1
2 1 lon_station_grid2 lat_station_grid2
For example, I am running 3 grids and have 6 stations in grid 1, 5 stations in grid 2, and 1 station in grid 3.
You can have the same locations inside different grids to have a feeling for higher resolution benefits etc.
NSTATION == 6 5 1 !
POS = GRID FLAG X-POS Y-POS COMMENT
1 1 115.735666 -31.845516 ! Hillarys 1
1 1 115.716965 -32.063581 ! Fremantle 2
1 1 115.5388 -32.037274 ! Rottnest 3
1 1 114.53745 -28.759551 ! Geraldton 4
1 1 115.608033 -33.309406 ! Bunbury 5
1 1 115.333544 -33.593791 ! Busselton 6
2 1 115.735666 -31.845516 ! Hillarys 1
2 1 115.716965 -32.063581 ! Fremantle 2
2 1 115.5388 -32.037274 ! Rottnest 3
2 1 115.647252 -33.283216 ! Bunbury 4
2 1 115.3334737 -33.629014 ! Busselton 5
3 1 114.603100 -28.761849 ! Geraldton 1
Cheers,
Ivica
having a look into your stations.in I can see the problem is that you put stations only for GRID 1:
NSTATION == 1 2 ! you want to have 1 station in grid 1 (parent) and 2 stations inside a nested grid 2 (child)
POS = GRID FLAG X-POS Y-POS COMMENT
1 1 120.5750 33.7917 ! this is station inside grid 1 (first integer = 1)
1 1 121.4297 32.5227 !yangkougang leida this is still grid 1
If you want to have 1 station for parent and 1 station for child then put something like this:
NSTATION == 1 1
1 1 lon_station_grid1 lat_station_grid1
2 1 lon_station_grid2 lat_station_grid2
For example, I am running 3 grids and have 6 stations in grid 1, 5 stations in grid 2, and 1 station in grid 3.
You can have the same locations inside different grids to have a feeling for higher resolution benefits etc.
NSTATION == 6 5 1 !
POS = GRID FLAG X-POS Y-POS COMMENT
1 1 115.735666 -31.845516 ! Hillarys 1
1 1 115.716965 -32.063581 ! Fremantle 2
1 1 115.5388 -32.037274 ! Rottnest 3
1 1 114.53745 -28.759551 ! Geraldton 4
1 1 115.608033 -33.309406 ! Bunbury 5
1 1 115.333544 -33.593791 ! Busselton 6
2 1 115.735666 -31.845516 ! Hillarys 1
2 1 115.716965 -32.063581 ! Fremantle 2
2 1 115.5388 -32.037274 ! Rottnest 3
2 1 115.647252 -33.283216 ! Bunbury 4
2 1 115.3334737 -33.629014 ! Busselton 5
3 1 114.603100 -28.761849 ! Geraldton 1
Cheers,
Ivica