Add MOAB driver changes for wave-ice coupling and fix array bounds issue.#8225
Conversation
|
Thanks @sbrus89. To clarify, the MOAB driver doesn't support the WAV model yet. Are you just syncing changes from driver-mct? |
|
Yes, exactly. Right now the changes from #7958 are causing a fail in the |
|
In testing this I found a divide by zero issue caused by the array indexing change: |
|
Not sure what you mean by "the array indexing change". Are you trying to run with the new coupling? I think all you need to get past the moab build error is the changes in driver-moab/cime_config. |
|
Was the error you mentioned in #8225 (comment) already fixed? |
Add the MOAB driver changes for wave-ice coupling from e8b7da4 It also fixes an array bounds issue for debug gnu builds. [BFB]
| waveFrequency = waveFrequency_TEMP(2:nFrequencies-1) | ||
| waveFreqBinWidth = waveFreqBinWidth_TEMP(2:nFrequencies-1) | ||
| waveFrequency(1:nFrequencies-2) = waveFrequency_TEMP(2:nFrequencies-1) | ||
| waveFreqBinWidth(1:nFrequencies-2) = waveFreqBinWidth_TEMP(2:nFrequencies-1) |
There was a problem hiding this comment.
@rljacob, this was the indexing change that I was hoping would fix the wave test fail in the extra coverage suite: https://my.cdash.org/tests/368302943, but it ended up causing divide by zero errors when I ran the wave developer tests.
There was a problem hiding this comment.
Ok. It wasn't clear if your #8225 (comment) was something you were noting for the record or something you wanted me to fix.
There was a problem hiding this comment.
Sorry about that. I was going to look into fixing it.
Add the MOAB driver changes for wave-ice coupling from e8b7da4
It also fixes an array bounds issue for debug gnu builds.
[BFB]