Search found 32 matches
- Sun Jan 27, 2019 10:35 pm
- Forum: Meetings/Workshops
- Topic: IAPSO Symposia, IUGG 2019, Montreal
- Replies: 0
- Views: 829
IAPSO Symposia, IUGG 2019, Montreal
We would like to bring your attention to our symposium, “The Southern Ocean: Where Ocean, Ice and Atmosphere Meet”, at the forthcoming IUGG meeting, as part of a series of IAPSO symposia spanning July 9th to July 14th in Montreal, Canada . The symposium aims to highlight recent advances in understan...
- Tue Mar 06, 2018 7:25 am
- Forum: ROMS Installation
- Topic: An compiling error regarding "crtbegin.o"
- Replies: 6
- Views: 2153
Re: An compiling error regarding "crtbegin.o"
Thank you, David!
I will ask the system manager to do what you suggested.
Best,
Hajoon
I will ask the system manager to do what you suggested.
Best,
Hajoon
- Sun Mar 04, 2018 8:22 pm
- Forum: ROMS Installation
- Topic: An compiling error regarding "crtbegin.o"
- Replies: 6
- Views: 2153
Re: An compiling error regarding "crtbegin.o"
Thank you, Kate.
I will discuss with the system manager!Well, obviously not everything got cleaned out. Try recompiling arpack with gfortran. Everything, including netcdf-fortran, has to be compiled with the same compiler.
- Sun Mar 04, 2018 11:57 am
- Forum: ROMS Installation
- Topic: An compiling error regarding "crtbegin.o"
- Replies: 6
- Views: 2153
Re: An compiling error regarding "crtbegin.o"
Thank you, Kate, for taking a look at this problem. I use the "build.bash" script, so it implicitly does "make clean". I tried gfortran but got the following error. -lnetcdff -L/home/hajsong/ROMS_564/Lib/ARPACK -lparpack-mpif90 -L/home/hajsong/ROMS_564/Lib/ARPACK -larpack-mpif90 /usr/bin/ld: warning...
- Sat Mar 03, 2018 6:33 am
- Forum: ROMS Installation
- Topic: An compiling error regarding "crtbegin.o"
- Replies: 6
- Views: 2153
An compiling error regarding "crtbegin.o"
Hi, I was trying to compile the code with IS4DVAR, and encountered the following error. cd Build; /home/software/pgi/17.3/linux86-64/17.3/bin/pgf90 -c -O3 master.f90 /home/software/pgi/17.3/linux86-64/17.3/bin/pgf90 -O3 Build/roms_import.o Build/propagator.o Build/master.o Build/roms_export.o Build/...
- Thu Mar 14, 2013 8:50 pm
- Forum: ROMS Bugs
- Topic: Typo in adjoint biology codes
- Replies: 1
- Views: 1499
Typo in adjoint biology codes
I found typos in the adjoint codes for biology.
For example, in ad_npzd_iron.h, line 900,
add_cff should be ad_cff.
Thank you.
Hajoon
For example, in ad_npzd_iron.h, line 900,
add_cff should be ad_cff.
Thank you.
Hajoon
- Fri Feb 15, 2013 12:37 am
- Forum: ROMS Bugs
- Topic: Bug in reading tl_LBC for biological variables
- Replies: 2
- Views: 1507
Re: Bug in reading tl_LBC for biological variables
Thank you for fixing the bug!
It was fast!!
It was fast!!
- Wed Feb 13, 2013 9:04 pm
- Forum: ROMS Bugs
- Topic: Bug in reading tl_LBC for biological variables
- Replies: 2
- Views: 1507
Bug in reading tl_LBC for biological variables
I would like to report a possible bug in reading tangent linear (and representer) boundary conditions for biological variables. Since I am working on the NEMURO model, I will follow the script name for this model. But other biological models are also applied. In the standard input file (ocean.in), y...
- Thu Oct 25, 2012 5:32 pm
- Forum: ROMS Bugs
- Topic: Bugs in npzd_iron_inp.h
- Replies: 1
- Views: 1192
Bugs in npzd_iron_inp.h
While trying to compile NPZD_IRON, I found two tiny bugs in 'npzd_iron_inp.h' First one is just typo. "itrcer" at line 33 integer :: i, ifield, igrid, itrcer, itrc, ng, nline, status should be itracer so that integer :: i, ifield, igrid, itracer, itrc, ng, nline, status Next one is at line 627. This...
- Sun Aug 14, 2011 5:14 am
- Forum: ROMS Ecosystem
- Topic: ROMS mex compiles .f files (within rnt toolbox)
- Replies: 3
- Views: 3462
Re: ROMS mex compiles .f files (within rnt toolbox)
Thanks! I will try it again with old Matlab version.
I used to use mex files, but after immigrating to a new system, they do not work well.
And I recall that the old system had older Matlab version.
Best,
Hajoon
I used to use mex files, but after immigrating to a new system, they do not work well.
And I recall that the old system had older Matlab version.
Best,
Hajoon
- Thu Aug 11, 2011 10:44 pm
- Forum: ROMS Ecosystem
- Topic: ROMS mex compiles .f files (within rnt toolbox)
- Replies: 3
- Views: 3462
Re: ROMS mex compiles .f files (within rnt toolbox)
Hi,
I wonder if you resolved this problem.
I have the same issue now...
Thank you.
Hajoon
I wonder if you resolved this problem.
I have the same issue now...
Thank you.
Hajoon
- Wed May 18, 2011 9:07 pm
- Forum: ROMS Bugs
- Topic: Bug in tl_ocean.h
- Replies: 0
- Views: 1136
Bug in tl_ocean.h
Hi, I just found a trivial bug in the tl_ocean.h The local variable, Fcount, is not declared under the 'ROMS_finalize', and this resulted in an error during compiling. SUBROUTINE ROMS_finalize ! !======================================================================= ! ! ! This routine terminates RO...
- Wed Apr 27, 2011 12:06 am
- Forum: ROMS Bugs
- Topic: Bugs in adsen_ocean.h
- Replies: 1
- Views: 1539
Bugs in adsen_ocean.h
Hi, I would like to report some trivial bugs that I found in adsen_ocean.h after updating ROMS code to the most recent version. First, I think the line 219 should be commented out because it is already declared in line 133. Line 219 looks like 10 FORMAT (' Process Information:',/) And under the subr...
- Mon Nov 08, 2010 5:33 pm
- Forum: ROMS Bugs
- Topic: Possible bug in obs_write.F90
- Replies: 2
- Views: 1913
Re: Possible bug in obs_write.F90
Hi Hernan, Thank you for the update. I updated the code and test it, and I think I found another bug regarding this. The misfit is not computed as "NLmodVal(iobs)-ObsVal(iobs)". According to the 'is4dvar_ocean.h', misfit is saved when (line 548 - 555) ! ! Activate switch to write out initial and fin...
- Thu Sep 23, 2010 8:24 pm
- Forum: ROMS Bugs
- Topic: Possible bug in obs_write.F90
- Replies: 2
- Views: 1913
Possible bug in obs_write.F90
Hi, I would like to report the possible bug in computing the misfit in obs_write.F90, which is !----------------------------------------------------------------------- ! Compute and write initial and final model-observation misfit ! (innovation) vector for output purposes only. Write also initial ! ...
- Tue Jul 27, 2010 10:38 pm
- Forum: ROMS Bugs
- Topic: Possible bug in matlab/4dvar/d_std.m
- Replies: 1
- Views: 1653
Possible bug in matlab/4dvar/d_std.m
Hi, It is not about the ROMS code, but about the matlab code that is included tha package. In the recent update, the scripts that compute the standard deviation have been changed a lot. But mis-position of this one line causes very different result. For the line 204-222 in d_std.m file look like thi...
- Thu Apr 29, 2010 12:12 am
- Forum: ROMS Adjoint
- Topic: Not using updated forcing
- Replies: 3
- Views: 2562
Re: Not using updated forcing
Dear experts, It is not a major thing, but I found something suspicious in writing initial file when the surface forcing adjustment option is on. If either 'ADJUST_WSTRESS' or 'ADJUST_STFLUX' is on, then the adjusted surface forcing fields are written in the initial file. The code 'wrt_ini.F' does t...
- Fri Jan 15, 2010 10:43 pm
- Forum: ROMS Adjoint
- Topic: Not using updated forcing
- Replies: 3
- Views: 2562
Re: Not using updated forcing
Thank you for the reply, Hernan. The code you posted looks right. I thought that the updated forcing variables are written in the FWDNAME if I do this T Hout(idUsms) Write out surface U-momentum stress. T Hout(idVsms) Write out surface V-momentum stress. T Hout(idTsur) Write out surface net heat flu...
- Fri Jan 15, 2010 7:58 pm
- Forum: ROMS Adjoint
- Topic: Not using updated forcing
- Replies: 3
- Views: 2562
Not using updated forcing
Hi, I was trying to correct both initial condition and surface forcing, and I found something suspicious. After all inner loops, it seems that the nonlinear model runs with corrected initial condition, but NOT with the corrected forcing. Since the corrected forcing is stored in the FWDNAME file, I t...
- Thu Aug 27, 2009 7:15 am
- Forum: ROMS Adjoint
- Topic: Using Bulk flux forcing in IS4DVAR
- Replies: 2
- Views: 2415
Re: Using Bulk flux forcing in IS4DVAR
The model stopped when the adjoint model is about to start.
So I guess the BULK_FLUXES is not ready for the adjoint ROMS, right?
Thank you.
Hajoon
So I guess the BULK_FLUXES is not ready for the adjoint ROMS, right?
Thank you.
Hajoon
- Thu Aug 27, 2009 1:02 am
- Forum: ROMS Adjoint
- Topic: Using Bulk flux forcing in IS4DVAR
- Replies: 2
- Views: 2415
Using Bulk flux forcing in IS4DVAR
Hi, I am wondering if BULK_FLUXES is working for IS4DVAR. I could see Adjoint/ad_bulk_flux.F, but it says #if defined ADJOINT && defined BULK_FLUXES_NOT_YET 'BULK_FLUXES_NOT_YET' flag means that it is not ready yet? And, although it is compiled with BULK_FLUXES and running, I got this message in sta...
- Thu Apr 09, 2009 6:12 pm
- Forum: ROMS Bugs
- Topic: Possible bug in Utility/normalization.F
- Replies: 3
- Views: 1920
Re: Possible bug in Utility/normalization.F
Dear Hernan,
Thank you.
I got that error when I turned on ONLY "ADJUST_WSTRESS".
I will update it!
Best,
Hajoon
Thank you.
I got that error when I turned on ONLY "ADJUST_WSTRESS".
I will update it!
Best,
Hajoon
- Fri Mar 27, 2009 5:25 pm
- Forum: ROMS Adjoint
- Topic: Error while trying to correct wind forcing in IS4DVAR
- Replies: 1
- Views: 2810
Re: Error while trying to correct wind forcing in IS4DVAR
Hi all, I found the problem. I was using old version of standard input file. There should be the parameter named 'NSFF', which is 'Number of time-steps between 4DVAR adjustment of surface forcing fluxes.' But the old standard input file that I was using did not have this parameter so that ROMS tried...
- Wed Mar 25, 2009 5:10 am
- Forum: ROMS Adjoint
- Topic: Error while trying to correct wind forcing in IS4DVAR
- Replies: 1
- Views: 2810
Error while trying to correct wind forcing in IS4DVAR
Hi all, I tried to include wind forcing correction in IS4DVAR by defining 'ADJUST_WSTRESS'. (I provided wind forcing standard deviation file, too.) It compiled well, but there was an error when I ran it. After reading the standard deviation files for initial and wind forcing, I got this message. DEF...
- Wed Mar 25, 2009 4:57 am
- Forum: ROMS Bugs
- Topic: Possible bug in Utility/normalization.F
- Replies: 3
- Views: 1920
Possible bug in Utility/normalization.F
Hi all, While working on correcting wind forcing in IS4DVAR, I found something suspicious. Utility/normalization.F looks like # if defined ADJUST_WSTRESS || defined ADJUST_STFLUX (line 2236) ...... ...... IF (LwrtNRM(ifile,ng)) THEN (line 2244) ...... ...... # endif (line 2488) # if defined ADJUST_S...
- Fri Nov 14, 2008 8:20 pm
- Forum: ROMS Adjoint
- Topic: Adjoint with MPI?
- Replies: 2
- Views: 2307
Re: Adjoint with MPI?
Dear Hernan,
In order to identify the error messages, I tried to compile it with MPI again.
But it worked at this time.
Sorry about the misleading posting.
Best,
Hajoon
In order to identify the error messages, I tried to compile it with MPI again.
But it worked at this time.
Sorry about the misleading posting.
Best,
Hajoon
- Fri Nov 14, 2008 7:48 pm
- Forum: ROMS Adjoint
- Topic: Adjoint with MPI?
- Replies: 2
- Views: 2307
Adjoint with MPI?
Hi,
I have a quick question.
Does adjoint model is available with MPI?
I tried to compile the adjoint sensitivity run with MPI, but it gave me an error.
(It successfully compiled with serial mode, though.)
Thank you!
Hajoon
I have a quick question.
Does adjoint model is available with MPI?
I tried to compile the adjoint sensitivity run with MPI, but it gave me an error.
(It successfully compiled with serial mode, though.)
Thank you!
Hajoon
- Tue Nov 04, 2008 8:33 pm
- Forum: ROMS Ecosystem
- Topic: npzd_Powell
- Replies: 1
- Views: 2192
npzd_Powell
Hi, I was trying to use npzd variables as passive tracers. So I killed all biological interaction in /Nonlinear/npzd_Powell.h . In order to test this, I ran just 10 days with zero values for npzd in the initial/boundary file. I expected to see zero values throughout the run, but the output are not e...
- Tue Feb 05, 2008 7:07 pm
- Forum: ROMS Bugs
- Topic: Possible typos
- Replies: 1
- Views: 1620
Possible typos
Hi, I found some possible typos in Adjoint/ad_u3dbc_im.F and Tangent/tl_u3dbc_im.F First, in Adjoint/ad_u3dbc_im.F, I suspect line 166, 168, 292, 294, 420 and 422. For example in line 166, it is now tau=M3obc_in(inorth) And I think it should be tau=M3obc_in(ng,inorth) Same chages can be applied in o...
- Fri Feb 01, 2008 7:46 pm
- Forum: ROMS Installation
- Topic: segmentation fault at the end of run
- Replies: 0
- Views: 1015
segmentation fault at the end of run
Hi,
I used to run ROMS 3.0 using openmp on remote computer.
But I got segmentation fault error at the end of run when I tried yesterday.
So I tried to run using serial mode, and it worked.
Have you ever encountered segmentation fault error at the end of run?
Thank you.
I used to run ROMS 3.0 using openmp on remote computer.
But I got segmentation fault error at the end of run when I tried yesterday.
So I tried to run using serial mode, and it worked.
Have you ever encountered segmentation fault error at the end of run?
Thank you.
- Tue Aug 14, 2007 3:22 pm
- Forum: ROMS Discussion
- Topic: SPONGE layer
- Replies: 2
- Views: 1772
- Mon Aug 13, 2007 3:11 am
- Forum: ROMS Discussion
- Topic: SPONGE layer
- Replies: 2
- Views: 1772
SPONGE layer
Hi all,
I remember that I could adjust sponge layer in ROMS 2.2 in /Utility/horz_mix.F
But I cannot find this file in ROMS 3.0.
Then how can I adjust sponge layer??
Thank you.
Ha Joon
I remember that I could adjust sponge layer in ROMS 2.2 in /Utility/horz_mix.F
But I cannot find this file in ROMS 3.0.
Then how can I adjust sponge layer??
Thank you.
Ha Joon