{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":171692561,"defaultBranch":"master","name":"HYCOM-src","ownerLogin":"HYCOM","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-02-20T14:54:32.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/30185783?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1556906436.0","currentOid":""},"activityList":{"items":[{"before":"62954f2b85bb2d078fd02de1bbc3e68336a3e422","after":"5fb66b6d854083d2ffe769b9a57ffd44634ebdc9","ref":"refs/heads/master","pushedAt":"2024-09-22T14:35:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Add hybthk to expand thin layers\n\nHYBGEN often creates a thick-thin-thick layer structure.  Which\nreduces the effective vertical resolution.\n\nThe bkldat variable hybthk controls expanding such thin layers with\nwater from adjacent layers above and below.\n\nAll blkdat.input files must be updated.  Setting this to 0.0 recovers\nthe original behaviour.  The maximum value is 0.9 and this is often\na good choice.  For example:\n\n0.01 'hybiso' = HYBGEN: Use PCM if layer is within hybiso of target density\n5.0  'hybthn' = HYBGEN: ratio of layer thicknesses to select the thiner\n0.9  'hybthk' = HYBGEN: thick-thin-thick ratio to expand the thin layer\n3    'hybmap' = HYBGEN: remapper flag (0=PCM, 1=PLM, 2=PPM, 3=WENO-like)\n\nNote that hybthk cannot distinguish between pathological thick-thin-thick\nlayers and layers that are that way because of dynamics, e.g. in strong\nfronts and eddies.  So use with care.","shortMessageHtmlLink":"Add hybthk to expand thin layers"}},{"before":"d3f5330ce53b4103507d4ac60a5863fa8ea0b8bb","after":"62954f2b85bb2d078fd02de1bbc3e68336a3e422","ref":"refs/heads/master","pushedAt":"2024-09-22T13:24:57.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"dx0k-ed layers are never remapped with PCM","shortMessageHtmlLink":"dx0k-ed layers are never remapped with PCM"}},{"before":"9643d25dcdf706c24a496684c63aecb7e7aa01a8","after":"d3f5330ce53b4103507d4ac60a5863fa8ea0b8bb","ref":"refs/heads/master","pushedAt":"2024-08-19T18:27:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Add ocnscl for finer control of relative winds\n\nExisting options are wndflg 4,5 to use relative wind U10-Uocn;\nand -4,-5 to use absolute wind U10.  The new blkdat variable ocnscl\nsets wind to U10-ocnscl*Uocn.  So 0.0 is absolute winds and 1.0\nis full relative winds.  Setting ocnscl to 0.7 is a popular choice.\n\nThis adds a line to all blkdat.input files, for example:\n\n  -5      'wndflg' = wind stress input flag (0=none,1=uv-g,2,3=p-grd,4,5=wnd10m)\n   0.0    'ocnscl' = scale factor for Uocn in relative wind (0.0: absolute wind)","shortMessageHtmlLink":"Add ocnscl for finer control of relative winds"}},{"before":"7661e14f2983a7e9a28f6fccb0c963bfb8f18124","after":"9643d25dcdf706c24a496684c63aecb7e7aa01a8","ref":"refs/heads/master","pushedAt":"2024-05-06T12:46:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"set ldebug_empbal=.false.","shortMessageHtmlLink":"set ldebug_empbal=.false."}},{"before":"430a38bd523575cf749f2651932640817adaa703","after":"7661e14f2983a7e9a28f6fccb0c963bfb8f18124","ref":"refs/heads/master","pushedAt":"2024-05-06T12:36:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"added epmass=2 for river only mass exchange","shortMessageHtmlLink":"added epmass=2 for river only mass exchange"}},{"before":"aac48d5ff9bc83fd2de473ddc7387c1d37fb0017","after":"430a38bd523575cf749f2651932640817adaa703","ref":"refs/heads/master","pushedAt":"2024-05-06T12:20:16.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"add -fallow-argument-mismatch to gnu for MPI","shortMessageHtmlLink":"add -fallow-argument-mismatch to gnu for MPI"}},{"before":"f3ad2c49be7c2a9ac5091b4dabbc3c3d3db66eb1","after":"aac48d5ff9bc83fd2de473ddc7387c1d37fb0017","ref":"refs/heads/master","pushedAt":"2024-01-22T18:28:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Bugfix for epmass=1 when oneta is small\n\nThe actual depth is oneta * depth, with oneta limted to be at least oneta0.\nThere was a bug in epmass=1 for oneta close to oneta0.  This has been fixed\nby:\n  a) replacing oneta limit (oneta0), internally with pbot limit (pbotmin)\n  b) allowing evaporation to extend below a thin enough layer 1\n  c) clipping evaporation if it would drive oneta below oneta0\n\nNote that SSH is typically greater than -2 m without tides and so a\nsmall oneta is unlikely to occur for a typical minimum rest depth unless\ntides are included.\n\nThe reporting of oneta=oneta0 was every 3 time steps, but now it is when\nother extended diagnostics are reported (e.g. every diagfq days).","shortMessageHtmlLink":"Bugfix for epmass=1 when oneta is small"}},{"before":"b1dd7404936d87559123a877b0eb86aee508b95e","after":"f3ad2c49be7c2a9ac5091b4dabbc3c3d3db66eb1","ref":"refs/heads/master","pushedAt":"2024-01-17T18:28:30.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"use variable cesmbeta for macro USE_NUOPC_CESMBETA","shortMessageHtmlLink":"use variable cesmbeta for macro USE_NUOPC_CESMBETA"}},{"before":"f021fdd2b5a593a4d2f3367ca017415a222038cb","after":"b1dd7404936d87559123a877b0eb86aee508b95e","ref":"refs/heads/master","pushedAt":"2023-09-19T15:34:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Initialize si_h to zero","shortMessageHtmlLink":"Initialize si_h to zero"}},{"before":"b7e9322fa3b616df18c71bac6f6270a5fb142e2c","after":"f021fdd2b5a593a4d2f3367ca017415a222038cb","ref":"refs/heads/master","pushedAt":"2023-09-08T15:48:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Add short decription to README.md","shortMessageHtmlLink":"Add short decription to README.md"}},{"before":"083ba069cfb442271b3f2850662713dba306e60a","after":"b7e9322fa3b616df18c71bac6f6270a5fb142e2c","ref":"refs/heads/master","pushedAt":"2023-09-08T14:51:29.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Add README.md, upodate README.src","shortMessageHtmlLink":"Add README.md, upodate README.src"}},{"before":"49820380150ec080a4d7303416b8a0e59f738e2a","after":"083ba069cfb442271b3f2850662713dba306e60a","ref":"refs/heads/master","pushedAt":"2023-07-16T18:57:47.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Correct negative salinities from KPP\n\nVertical diffusion does not typically create new extrema, so\nnon-negative salinities typically stay non-negative in mixed layer\nsub-modules that imploy vertical diffusion.  However KPP has a\n\"non-local\" option that can produce negative salinities in its\nattempt to stabalize the water column.  These are rare, and are\nnow explicitly corrected while preserving the vertical average\nsalinity.\n\nThe calcultion of relaxation to SSS in thermf.F90 now involves the\nparameter frac_clim to control how much fresher then climatology\nSSS needs to be to override sssrmx.  The default is 0.5, i.e.\nfully relax when fresher than half of climatological sss, which\nis identical to its previous behaviour.  However, frac_clim can be\nset at compile time to zero to turn off this sssrmx override.\n\nAlso, sssE-P in .txt profile output is now clipped when SSS is\nless than 0.1 psu.  The result is then incorrect, but avoids\ndividing by zero.","shortMessageHtmlLink":"Correct negative salinities from KPP"}},{"before":"4334a885e899e136f7654affacdc2d3f0e29ccc8","after":"49820380150ec080a4d7303416b8a0e59f738e2a","ref":"refs/heads/master","pushedAt":"2023-07-01T22:26:35.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Add diagnostic tracers\n\nDiagnostic tracers use the existing dynamic tracer infrastructure, but\nsince they are diagnostic they are not written to the rerstart file.\n\nSupported by two new blkdat variables mtracr and dtrflg, but if mtracr\nis 0 dtrflg is not included:\n\n   0      'ntracr' = number of tracers (0=none,negative to initialize)\n   0      'trcflg' = tracer flags      (one digit per tr, most sig. replicated)\n   3      'mtracr' = number of diagnostic tracers\n 801      'dtrflg' = diagnostic tracer flag (one per tracer, 801-899)\n 802      'dtrflg' = diagnostic tracer flag (one per tracer, 801-899)\n 803      'dtrflg' = diagnostic tracer flag (one per tracer, 801-899)\n\nAt present only three diagnostic tracers are provided:\n\n  dtrflg=801: change in layer thickness   due to hybgen, m/day\n  dtrflg=802: change in layer temperature due to hybgen, degC/day\n  dtrflg=803: change in layer salinity    due to hybgen, psu/day\n\nSee hybgen.F90 for how these are calculated.  Tracer flags 804 to 899\nare available to implement other diagnostic tracers in the future.\nThe only restrictions are that they are nominally layer averaged\nquantities, and they must be calculatable every time step.  Like\nvisc and diff, they could also be layer interface quantities but\nthen their means would not be accuate.","shortMessageHtmlLink":"Add diagnostic tracers"}},{"before":"1d44d4ac7000a9460c802b0e3c52842d262aedc0","after":"4334a885e899e136f7654affacdc2d3f0e29ccc8","ref":"refs/heads/master","pushedAt":"2023-05-19T15:25:31.614Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Add dx0k for maximum layer thickness\n\nThere are new optional blkdat.input variables:\n\n! --- 'dx00'   = maximum layer thickness minimum, optional (m)\n! --- 'dx00x'  = maximum layer thickness maximum, optional (m)\n! --- 'dx00f'  = maximum layer thickness stretching factor (1.0=const)\n\nor\n\n! --- 'dx0k  ' = layer k maximum layer thickness (m)\n\nFor the GOFS 3.1 41-layer setup dp0k is 1 to 600m and a good choice\nfor better deep vertical resolution might be dx0k(1:41)=750 which\nwould be inactive for shallow layers:\n\n 750.00   'dx00  ' = maximum layer thickness minimum, optional (m)\n 750.00   'dx00x ' = maximum layer thickness maximum, optional (m)\n   1.00   'dx00f ' = maximum layer thickness stretching factor (1.0=const)\n   1.00   'dp0k  ' = layer   1 deep    z-level spacing minimum thickness (m)\n\n 600.00   'dp0k  ' = layer  41 deep    z-level spacing minimum thickness (m)\n\ndx0* is optional, and is disabled if not present. It \"inflates\"\nzero thickness layers at the bottom if the layer above is thicker\nthan its maximum.  This replaces very thick isopycnal layers with\nseveral thinner layers that might still have about the same\ndensity but can have different velocities.  Hence increasing the\ndeep vertical resolution.  The idea behind dx0k comes from\nMOM6's HYCOM1 option MAX_LAYER_THICKNESS.","shortMessageHtmlLink":"Add dx0k for maximum layer thickness"}},{"before":"de5f57e093d31060047bf992ff3d2011730a8ebc","after":"1d44d4ac7000a9460c802b0e3c52842d262aedc0","ref":"refs/heads/master","pushedAt":"2023-05-19T12:05:10.051Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Better support for doubly periodic domains\n\nDoubly periodic domains must be on a f-plane and are primarily used for\n1-D (single column) cases, with idm=jdm=5 and no variation in x or y,\nbut also for some idealized test cases such as an isolated gyre.\n\nThese domains were only previously supported on a single task, but\nnow multple tasks (i.e. MPI) is now allowed provided there is only\none tile in the j direction (mpe=1).","shortMessageHtmlLink":"Better support for doubly periodic domains"}},{"before":"bf5f2f8aa90fb6a3597b1f0ca333bd95623f8fee","after":"de5f57e093d31060047bf992ff3d2011730a8ebc","ref":"refs/heads/master","pushedAt":"2023-03-19T14:33:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Added the macro MASSLESS_1MM\n\nIn mxkprf.f the \"lowest substantial mass-containing layer\" is at\nleast 10cm thick by default.  The compile time macro MASSLESS_1MM\nchanges this to 1mm, which is the minimum possible in this context.\n\nNote that in hybgen, the \"lowest substantial mass-containing layer\"\nis at least 0.001mm thick.  This difference is due to avoiding ill\nconditioned tridiagonal matrices in mxkprf.f\n\nThis is implemented as a compile time macro because 10cm has worked\nwell in most cases and 1mm has not be extensively tested.  The 10cm\ncriteria has lead to anomalous T and S values in GOFS 3.1 when a\nlayer is always less than 10cm thick at the bottom.  So setting\nMASSLESS_1MM is advisable when running with data assimilation, and\nshould arguably be the default.\n\nMake.csh has been updated to document the available OCN_MISC flags.\nIt also now defaults to -DEOS_SIG2 and -DEOS_17T.","shortMessageHtmlLink":"Added the macro MASSLESS_1MM"}},{"before":"00dfbdf06eb6573cfff424367808c028fe6ca1c6","after":"bf5f2f8aa90fb6a3597b1f0ca333bd95623f8fee","ref":"refs/heads/master","pushedAt":"2023-03-19T14:12:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"Added the macro MOMTUM_CFL\n\nThe compile time macro MOMTUM_CFL adds a CFL limiter to momtum, similar\nto the existing MOMTUM4_CFL in momtum4.  In both cases velocities are\nclipped if they exceed a CFL limit, and if the clipping exceeds 0.5 m/s\nat a location a diagnostic is written to the .log file.\n\nThis is a macro because CFL should not be exceeded when HYCOM runs\nwith appropriate parameters and because clipping is not a physical\nprocess.  If MOMTUM_CFL is applied at compile time, the model .log\nfile should be monitored for \"velocty clipped\" warning messages.\n\nThe fatal stop for large negative dp's in loop 19 of cnuity has been\nremoved, because these might be corrected in loop 15.","shortMessageHtmlLink":"Added the macro MOMTUM_CFL"}},{"before":"c98fb34dd6c1f7ef23dc3243e4eb804f317a280e","after":"00dfbdf06eb6573cfff424367808c028fe6ca1c6","ref":"refs/heads/master","pushedAt":"2023-03-14T13:59:27.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"awallcraft","name":"Alan Wallcraft","path":"/awallcraft","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/29555153?s=80&v=4"},"commit":{"message":"bugfix to dp0cum in hybgenaj\n\ndp0cum sets hybgen's minimum interface depths and therefore its near surface fixed depth layers.  A bug made this slightly dependent on the instantaneous layer structure when in \"deep\" water, when it should be constant in time.  The incorrect minimum interface depths were shallower than the correct values.\n\nThe bug changes answers, but may not have caused serious issues for HYCOM.  However, when ported to MOM6 hybgen was applied with a much longer time step (e.g. 1200 seconds in MOM6 vs 180 seconds for the same global domain in HYCOM) and the bug caused a wildly inaccuate layer structure at isolated points.\n\nIf you have encountered single column model blow ups in HYCOM that were resistant to halving the time step, they might have been due to this bug.  In practice HYCOM's baroclinic time step, baclin, is often set to less than its theoretical maxium to maintain stability.  It is possible that the bugfix will allow a longer baclin time step in practice, i.e. the instabilites that limited baclin might have been from this bug.","shortMessageHtmlLink":"bugfix to dp0cum in hybgenaj"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yMlQxNDozNToyNi4wMDAwMDBazwAAAAS9OFgj","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wMy0xNFQxMzo1OToyNy4wMDAwMDBazwAAAAMDJuyf"}},"title":"Activity · HYCOM/HYCOM-src"}