got it, thanks very much!jzavala wrote:Yes, ROMS SSH is the sum of the MDT, the SLA and tides (if you have them defined in ROMS).
Be careful to add the model MDT and not other product such as that provided by AVISO.
The model MDT can be obtained as the mean of a long (say 5 years or more) forward run.
Jvr
Search found 17 matches
- Sat Nov 12, 2016 12:46 pm
- Forum: ROMS Discussion
- Topic: assimilate TSLA into the restart fields of my ROMS model
- Replies: 6
- Views: 6132
Re: assimilate TSLA into the restart fields of my ROMS model
- Tue Nov 01, 2016 3:11 am
- Forum: ROMS Discussion
- Topic: assimilate TSLA into the restart fields of my ROMS model
- Replies: 6
- Views: 6132
Re: assimilate TSLA into the restart fields of my ROMS model
The point of having a PERFECT RESTART option in ROMS is to be able to be able to restart a run as if it were never interrupted. To do so it needs all levels that are carried for the 3td-order predictor-corrector time stepping. . Hello , I have a basic confusion. When I use the 4Dvar to assimilate ...
- Mon Sep 26, 2016 8:42 am
- Forum: ROMS Problems
- Topic: ecmwf2roms
- Replies: 10
- Views: 12366
Re: ecmwf2roms
Dear ymamoutos many thanks for your answer i have got what is my problem :wink: sincerely yours fereshte hello , in the file 'd_ecmwf2roms.m',there have the lines as follow to change the 'previous accumulation'. but I find that the variable 'field_previous' used without in initial value. How to ...
- Tue Jul 05, 2016 12:45 pm
- Forum: ROMS Problems
- Topic: forrtl: severe (174): SIGSEGV, segmentation fault occurred
- Replies: 24
- Views: 22031
Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr
No need to double post - I answered your other one. But what I'd really do is run this in a debugger and figure out exactly what's going on. This can be solved in serial mode, so the free gdb would work. Sorry, I am just too worry about my research. I used the blkm2.nc and brym2.nc which time index ...
- Mon Jul 04, 2016 1:57 pm
- Forum: ROMS Problems
- Topic: forrtl: severe (174): SIGSEGV, segmentation fault occurred
- Replies: 24
- Views: 22031
Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr
I have remove the cycle attribute, and just use bulkm2.nc and brym2.nc. but also the same problem.How to check the error.kate wrote:You can't have negative time, you can't have a cycle_length of zero, and you can't have this:in the forcing file , the time index is all the same.
- Mon Jul 04, 2016 1:49 pm
- Forum: ROMS Discussion
- Topic: i have a question
- Replies: 11
- Views: 8242
Re: i have a question
The time in the initial conditions file does not have to match the first time in all the boundary conditions, forcing, and other input files. ROMS is clever enough to take the initial conditions time and figure out which records to read and interpolate from all the others. If it were any other way ...
- Thu Jun 30, 2016 12:26 pm
- Forum: ROMS Problems
- Topic: forrtl: severe (174): SIGSEGV, segmentation fault occurred
- Replies: 24
- Views: 22031
Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr
I don't think the problem is in the time indexing. What is at line 100 of your get_data.F? get_data_ 100 get_data.f90 Which field is it trying to read there? You're right in that it's trying to read the time associated with that variable. the position of the get_data.f90 line 100 is try to read the ...
- Wed Jun 29, 2016 11:27 am
- Forum: ROMS Discussion
- Topic: bulk forcing
- Replies: 7
- Views: 5318
Re: bulk forcing
Thanks , I have understood it.kate wrote:The option is used in pre_step3d and it brings solar radiation down into the water column as heat instead of leaving it all at the surface.
- Wed Jun 29, 2016 11:25 am
- Forum: ROMS Installation
- Topic: Blowing-up: Saving latest model state into RESTART file
- Replies: 11
- Views: 12053
Re: Blowing-up: Saving latest model state into RESTART file
sorry applying so late.I run successful with your suggestion.Thank you very much.kate wrote:You are clamping to monthly climatology for T and S? I prefer RadNud from something like daily HYCOM fields. Same for u,v.
- Wed Jun 29, 2016 9:39 am
- Forum: ROMS Problems
- Topic: forrtl: severe (174): SIGSEGV, segmentation fault occurred
- Replies: 24
- Views: 22031
Re: forrtl: severe (174): SIGSEGV, segmentation fault occurr
Maybe show us that whole chunk of your ocean.in file. Did you ask it to read an initial conditions file? Do you have a comment on the ININAME line? It's reading that just before the ITLNAME. Hello Kate I may have a problem when the model read the focring/bulk file. But I can't find the point,could ...
- Wed Jun 22, 2016 9:37 am
- Forum: ROMS Discussion
- Topic: bulk forcing
- Replies: 7
- Views: 5318
Re: bulk forcing
I have a question that when I should define the option 'SOLAR_SOURCE' if I use the BULK_FLUXES?kate wrote:1. If you define BULK_FLUXES, you don't have to provide the stresses.
2. If you don't define QCORRECTION, SCORRECTION or SRELAXATION, you don't have to provide SST or SSS.
- Thu Jun 16, 2016 9:11 am
- Forum: ROMS Installation
- Topic: Blowing-up: Saving latest model state into RESTART file
- Replies: 11
- Views: 12053
Re: Blowing-up: Saving latest model state into RESTART file
Visualize your restart file. In this business, you need to build some debugging skills of your own. Hello! I have a problem when run a spinup with climatology data. I have run 855 days without error but blowup suddenly. I see the restart file,it has 11 variables 'zeta' 'u' 'v' 'ubar' 'vbar' 'temp ...
- Thu Jun 16, 2016 9:09 am
- Forum: ROMS Usage
- Topic: MAIN: Abnormal termination: BLOWUP.
- Replies: 18
- Views: 17097
Re: MAIN: Abnormal termination: BLOWUP.
I can't speak for the rest, but I don't want to look at your restart file. You need to start developing tools for looking at ROMS output, including restart files. The simplest way to start is with ncview, which will show you the fields in any netcdf file (or group of files). That is often good ...
- Tue May 03, 2016 1:28 am
- Forum: ROMS Tools and Techniques
- Topic: Problems in using Arango 's matlab scripts
- Replies: 8
- Views: 9065
Re: Problems in using Arango 's matlab scripts
Got it, Thank you very much!kate wrote:No, ROMS does not read the coast variable - that's just for plotting codes.
- Mon May 02, 2016 11:40 am
- Forum: ROMS Tools and Techniques
- Topic: Problems in using Arango 's matlab scripts
- Replies: 8
- Views: 9065
Re: Problems in using Arango 's matlab scripts
[quote="kate"]The grid file only has horizontal information in it - ROMS won't try to read Vstretching from it. Own, I have found that with the grid file of WC13/Data/wc13_grd.nc. Thank you. Another qusetion: in the grid file generated using the ROMSTOOLS, there is no variable "coast". Whether it's ...
- Sun May 01, 2016 10:38 am
- Forum: ROMS Tools and Techniques
- Topic: Whether the ROMS_TOOLS of ROMS_AGRIF version can used
- Replies: 0
- Views: 6013
Whether the ROMS_TOOLS of ROMS_AGRIF version can used
Hi, I'm a newer to use ROMS of Rutgers version. Because there is no mannual of the matlab tools, I want to use the "ROMSTOOLS" which belong to ROMS_AGRIF version. so I want to know if the tools can be matched the Rutgers version correctly. If it can be use, will we also follow the step "make_grid ...
- Sun May 01, 2016 10:09 am
- Forum: ROMS Tools and Techniques
- Topic: Problems in using Arango 's matlab scripts
- Replies: 8
- Views: 9065
Re: Problems in using Arango 's matlab scripts
Hi. I'm a new learner of roms,too. Could you help me? I found that you have used to prepare the gird files with "ROMSTOOLS" which belong to ROMS_AGRIF version to run some application of Rutgers version. So I have some question. In the ROMSTOOLS of ROMS_AGRIF version, there is no parameter ...