Opened 6 years ago
Closed 3 years ago
#590 closed task (fixed)
Changing maximum data gap size to 0.8 [1 h]
Reported by: | Ian Culverwell | Owned by: | Ian Culverwell |
---|---|---|---|
Priority: | normal | Milestone: | ROPP9.1 carry over |
Component: | ropp_pp | Version: | 11.0 |
Keywords: | Cc: |
Description
https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/build/Makefile.am https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/bangle/ropp_pp_bending_angle_go.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_cutoff.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preproc.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess_champ.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess_cosmic.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess_grasrs.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/tools/ropp_pp_spectra_tool.f90
Original changesets:
Changing maximum data gap size to 0.8: https://trac.romsaf.org/ropp/changeset/3207/ropp_src/branches/dev/Share/dmi_trunk/ropp_pp/preprocess/ropp_pp_preprocess_grasrs.f90
Change history (1)
comment:1 by , 3 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Version: | 9.0 → 11.0 |
No justification given, so we'll just take Stig's (or really Hallgeir's) word for it.
Checks out OK. (Note that we say
gap = 0.8_wp
rather than the less precisegap = 0.8
in the ticket.) Has no effect on the rs core test because for that datasetBTEST(mg_LCF(i),3)
is always.FALSE.
, so the condition that can lead to gap-filling, namelyis never met. Could affect test folder results, of course.
Max data gap size in this tool is not documented in the PP user guide, so no changes needed there.
Change committed at r6828.
Closing ticket.