Search found 14 matches
- Mon Mar 13, 2023 7:02 pm
- Forum: ROMS Bugs
- Topic: History file archiving intervals: bug in output.F?
- Replies: 12
- Views: 54986
Re: History file archiving intervals: bug in output.F?
I understand that this isn't a priority for the main trunk code, so I'll just go ahead and implement the fix on my end for now. But I'll add a few responses to the queries raised in case it helps anyone else down the road. First, it may help to clarify my context somewhat. I am running many of my ...
- Sat Mar 11, 2023 12:38 am
- Forum: ROMS Bugs
- Topic: History file archiving intervals: bug in output.F?
- Replies: 12
- Views: 54986
Re: History file archiving intervals: bug in output.F?
Okay, I have now reproduced the issue in the main trunk version of ROMS. I used the bio_toy Fennel application as my starting point, and made only a few minor tweaks to the input to replicate the starting time and archiving interval options from my primary app. Same basic scenario as described ...
- Mon Mar 06, 2023 6:18 pm
- Forum: ROMS Bugs
- Topic: History file archiving intervals: bug in output.F?
- Replies: 12
- Views: 54986
Re: History file archiving intervals: bug in output.F?
Following up, any clues on the logic here? It's primarily this line that is problematic in my case: IF (nHIS(ng).ne.ndefHIS(ng).and.iic(ng).eq.ntstart(ng)) THEN idefHIS(ng)=idefHIS(ng)+nHIS(ng) ! multiple record offset END IF (and yes, I've confirmed that the output.F logic is identical in my ...
- Thu Mar 02, 2023 12:09 am
- Forum: ROMS Bugs
- Topic: History file archiving intervals: bug in output.F?
- Replies: 12
- Views: 54986
Re: History file archiving intervals: bug in output.F?
I'm using a fork of Kate Hedstrom's ice-enhanced version of the code, with some additional biological model development layered on top (see https://github.com/beringnpz/roms/tree/main). I try to keep up with the latest major updates; I regularly pull in changes from Kate's upstream repo and peruse ...
- Wed Mar 01, 2023 8:17 pm
- Forum: ROMS Bugs
- Topic: History file archiving intervals: bug in output.F?
- Replies: 12
- Views: 54986
History file archiving intervals: bug in output.F?
I'm trying to diagnose a bug related to file archiving time periods. In my particular case this is manifesting as an error in the history file counts, but I think the same issue could possibly arise in all the multi-file-allowing output files (history, average, etc.). In short, my application ...
- Thu Jan 12, 2023 6:34 pm
- Forum: ROMS Ecosystem
- Topic: Runoff/river-derived biogeochemical tracer fluxes
- Replies: 5
- Views: 18689
Re: Runoff/river-derived biogeochemical tracer fluxes
Thanks for the quick reply! My recent runs have used the lateral flux river sources, not the runoff. I stole a wind-wave mixing parameterization (Li and Fox-Kemper) to add more surface mixing. We also changed the vertical profile of the input so that flow comes in below the surface too, instead of ...
- Wed Jan 11, 2023 6:57 pm
- Forum: ROMS Ecosystem
- Topic: Runoff/river-derived biogeochemical tracer fluxes
- Replies: 5
- Views: 18689
Runoff/river-derived biogeochemical tracer fluxes
TL;DR question: In the meandering discussion below, I'm looking for answers to a few questions: 1) How exactly do changes in zeta affect biogeochemical tracer concentrations? 2) How are other ROMS modelers implementing biogeochemical tracer fluxes associated with freshwater runoff from land? Point ...
- Thu Jul 28, 2022 6:33 pm
- Forum: ROMS Problems
- Topic: %files memory allocation: Seg fault with NDEFHIS and/or NDEFAVG > 0
- Replies: 4
- Views: 10347
Re: %files memory allocation: Seg fault with NDEFHIS and/or NDEFAVG > 0
Haha, definitely not afraid to make changes... that's what gets me into these problems! For once the error wasn't of my own making, which is why I had such trouble tracking it down; I just assumed I had broken something and so was concentrating on the portions of code I had modified.
- Thu Jul 28, 2022 5:46 pm
- Forum: ROMS Problems
- Topic: %files memory allocation: Seg fault with NDEFHIS and/or NDEFAVG > 0
- Replies: 4
- Views: 10347
Re: %files memory allocation: Seg fault with NDEFHIS and/or NDEFAVG > 0
As mentioned, the trigger for the seg fault was assignment to an unallocated pointer, not the write itself. Not quite sure why the seg fault didn't occur immediately and instead waited for the next print to standard output... but that's not really relevant to diagnosing the problem. I did track down ...
- Wed Jul 27, 2022 10:59 pm
- Forum: ROMS Problems
- Topic: %files memory allocation: Seg fault with NDEFHIS and/or NDEFAVG > 0
- Replies: 4
- Views: 10347
%files memory allocation: Seg fault with NDEFHIS and/or NDEFAVG > 0
Can someone clarify where memory for the HIS(ng)%files and AVG(ng)%files pointer arrays are allocated? I'm hitting an odd segmentation fault when related to these arrays. If I set NDEFHIS and NDEFAVG to 0, everything is fine. But if I choose a non-zero value, I'm getting a seg fault associated with ...
- Tue Jul 26, 2022 9:06 pm
- Forum: ROMS Problems
- Topic: check_multifile error (possibly boundary file-related?)
- Replies: 1
- Views: 3476
Re: check_multifile error (possibly boundary file-related?)
In case any future readers are interested... I finally, through copious use of print statements, tracked the source of this error to a typo in get_state.F, where I had mistakenly treated my benthic tracer variables as 2D rather than 3D variables (their vertical dimension is always set to 1 in my ...
- Wed Jul 20, 2022 9:59 pm
- Forum: ROMS Problems
- Topic: check_multifile error (possibly boundary file-related?)
- Replies: 1
- Views: 3476
check_multifile error (possibly boundary file-related?)
While developing some new biology modules for our Bering Sea ROMS domain, I seem to have broken... something... related to how boundary condition files are processed. I have exhausted all my usual techniques for tracking down the mistakes/bugs/etc, so I'm hoping someone here might have some ...
- Mon Mar 18, 2019 7:10 pm
- Forum: ROMS Problems
- Topic: How to tell ROMS to exit due to problematic numbers?
- Replies: 3
- Views: 3078
Re: How to tell ROMS to exit due to problematic numbers?
Sorry for the delayed response... I'm starting with the Al Hermann's Bering 10K code, which derives from the NEP5 code... which derives from one of your branches with sea ice. The version is identified as svn $Id: License_ROMS.txt 895 2009-01-12 21:06:20Z kate $ in the License, though I believe it ...
- Thu Oct 18, 2018 10:26 pm
- Forum: ROMS Problems
- Topic: How to tell ROMS to exit due to problematic numbers?
- Replies: 3
- Views: 3078
How to tell ROMS to exit due to problematic numbers?
In our current ROMS domain (which includes sea ice and biological dynamics), numerical instability issues (i.e. blowups) sometimes manifest themselves in ice- or biology-related portions of the code before hitting the usual checks for speed and energy (in diag.F). Specifically, we sometimes get ...