Log of /MITgcm/pkg/obcs/obcs_prescribe_read.F
Parent Directory
| Revision Log
| Revision Graph
Revision
1.10 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Mon Apr 16 23:35:58 2007 UTC
(17 years, 1 month ago)
by
jmc
Branch:
MAIN
CVS Tags:
checkpoint59,
checkpoint59a,
checkpoint59b,
checkpoint59c,
checkpoint59d,
checkpoint59e,
checkpoint59f,
checkpoint59g,
checkpoint59h
Changes since
1.9: +2 -2 lines
Diff to
previous 1.9
,
to
selected 1.3
move EXF header files from lower_case.h to UPPER_CASE.h
Revision
1.9 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Wed Mar 22 19:21:58 2006 UTC
(18 years, 2 months ago)
by
mlosch
Branch:
MAIN
CVS Tags:
checkpoint58c_post,
checkpoint58d_post,
checkpoint58e_post,
checkpoint58f_post,
checkpoint58g_post,
checkpoint58h_post,
checkpoint58i_post,
checkpoint58j_post,
checkpoint58k_post,
checkpoint58l_post,
checkpoint58m_post,
checkpoint58n_post,
checkpoint58o_post,
checkpoint58p_post,
checkpoint58q_post,
checkpoint58r_post,
checkpoint58s_post,
checkpoint58t_post,
checkpoint58u_post,
checkpoint58v_post,
checkpoint58w_post,
checkpoint58x_post,
checkpoint58y_post
Changes since
1.8: +2 -1 lines
Diff to
previous 1.8
,
to
selected 1.3
bug fix: needs an #include "PARAMS.h" in the (unlikely (o: ) event of
ALLOW_EXF and ALLOW_PTRACERS and ALLOW_OBCS defined (this unlikely
event just occured)
Revision
1.7 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Mon Oct 10 05:53:48 2005 UTC
(18 years, 8 months ago)
by
mlosch
Branch:
MAIN
CVS Tags:
checkpint57u_post,
checkpoint57v_post,
checkpoint57w_post,
checkpoint57x_post,
checkpoint57y_post,
checkpoint57y_pre
Changes since
1.6: +57 -3 lines
Diff to
previous 1.6
,
to
selected 1.3
o OBCS and PTRACERS: add open boundary support for passive tracers
- either use homogenous (pseudo) v.Neumann conditions or prescribe
OB-values from file; this is not different from the way theta and salinity
are treated
- however, Orlanski-radiation conditions are not supported, and the model
will stop if you use pTracers and Orlanski at the same time.
- beefed up the rountine obcs_external_fields_load: now only those open
boundary values are overwritten with values from files for which there
are really files, otherwise the OB-fields remain untouched. This makes
it possible to use different OBs at different ends of the domain (as
with EXF)
- TODO: add support for OB?w and OB?eta, which can currently not be read
from a file.
Revision
1.6 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue Oct 19 17:52:03 2004 UTC
(19 years, 7 months ago)
by
adcroft
Branch:
MAIN
CVS Tags:
checkpoint55h_post,
checkpoint55i_post,
checkpoint55j_post,
checkpoint56,
checkpoint56a_post,
checkpoint56b_post,
checkpoint56c_post,
checkpoint57,
checkpoint57a_post,
checkpoint57a_pre,
checkpoint57b_post,
checkpoint57c_post,
checkpoint57c_pre,
checkpoint57d_post,
checkpoint57e_post,
checkpoint57f_post,
checkpoint57f_pre,
checkpoint57g_post,
checkpoint57g_pre,
checkpoint57h_done,
checkpoint57h_post,
checkpoint57h_pre,
checkpoint57i_post,
checkpoint57j_post,
checkpoint57k_post,
checkpoint57l_post,
checkpoint57m_post,
checkpoint57n_post,
checkpoint57o_post,
checkpoint57p_post,
checkpoint57q_post,
checkpoint57r_post,
checkpoint57s_post,
checkpoint57t_post,
eckpoint57e_pre
Changes since
1.5: +4 -4 lines
Diff to
previous 1.5
,
to
selected 1.3
Bug fix: too many commas led to an empty argument.
Symptom: Model dies silently under MPI (not even a seg fault!)
Comment: Real pain in the butt to find with a 324 processor job.
Thanks for the extra fun, P.
Revision
1.2 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Fri Sep 24 12:32:09 2004 UTC
(19 years, 8 months ago)
by
mlosch
Branch:
MAIN
CVS Tags:
checkpoint55d_pre
Changes since
1.1: +6 -1 lines
Diff to
previous 1.1
,
to
selected 1.3
o initial check-in of alternative to reading open boundary values
with EXF, for those who like the old external_fields_load
o works for me, gives the same results as with EXF, but use at own risk (:
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.