-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't build coupled model in debug mode on orion #287
Comments
Has anyone else been able to replicate this? I tried running the cpld_debug test for the currrent develop branch. The err log (in rt_number/compile_3) shows:
The esmf debug library on orion is esmf/8_1_0_beta_snapshot_27-debug Any ideas on why this is getting set incorrectly? |
In compile.sh, we have:
module use $PATHTR/modulefiles/${MACHINE_ID}
modulefile="fv3"
if [[ "${MAKE_OPT}" == *"DEBUG=Y"* ]]; then
[[ -f $PATHTR/modulefiles/${MACHINE_ID}/fv3_debug ]] && modulefile="
fv3_debug"
fi
module load $modulefile
module list
Would you please check in compile.sh command, if it has "DEBUG=Y"?
…On Mon, Nov 30, 2020 at 10:07 AM Denise Worthen ***@***.***> wrote:
Has anyone else been able to replicate this? I tried running the
cpld_debug test for the currrent develop branch. The err log (in
rt_number/compile_3) shows:
1. esmf/8_1_0_beta_snapshot_27
The esmf debug library on orion is esmf/8_1_0_beta_snapshot_27-debug
Any ideas on why this is getting set incorrectly?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#287 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TPBZQXQSMHUN7QUNQTSSOYLBANCNFSM4T3OJXPQ>
.
|
My build directory on orion is: /work/noaa/marine/dworthen/ufs_dw. In there, I have rt.conf reduced to just the cpld_debug compile and run. One output directory is here: /work/noaa/stmp/dworthen/stmp/dworthen/FV3_RT/rt_112174 I just noticed that in the compile_1/err I see: The following have been reloaded with a version change:
|
So that looks to me you are loading esmf810bs27 debug.
…On Mon, Nov 30, 2020 at 1:10 PM Denise Worthen ***@***.***> wrote:
My build directory on orion is:
/work/noaa/marine/dworthen/ufs_dw. In there, I have rt.conf reduced to
just the cpld_debug compile and run.
One output directory is here:
/work/noaa/stmp/dworthen/stmp/dworthen/FV3_RT/rt_112174
I just noticed that in the compile_1/err I see:
The following have been reloaded with a version change:
1. esmf/8_1_0_beta_snapshot_27 => esmf/8_1_0_beta_snapshot_27-debug
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#287 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TPYURWLDVYXWIVNI6DSSPNYTANCNFSM4T3OJXPQ>
.
|
Yes, I agree that it seems to be loading the right esmf debug module, but the compile immediately fails on 'use esmf', as if it is actually trying to use the non-exisistent "_debug." |
I can compile in debug mode on orion if I do not use ecflow. |
Not sure if we have the same problem with debug tests. Please see Issue #279
<#279>. Can you
check the ESMF lib path when you use ESMF debug lib in ecflow on orion?
…On Mon, Nov 30, 2020 at 2:19 PM Denise Worthen ***@***.***> wrote:
I seem to be able to compile in debug mode on orion if I do not use ecflow.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#287 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TPCTUNXSW3WB3W2UYLSSPV4TANCNFSM4T3OJXPQ>
.
|
@DeniseWorthen can you check if you have an old version of the ecflow server running ( |
Yes thanks. I did find a very old ecflow job running which I killed. I'll try again. |
It seems that the old ecflow server was the issue. I've been able to repeat the same test now and am able to build in debug mode. Thanks all! |
* gitmodule to climbfuji/flake_from_yihua and ccpp/physics pointer update * new pointer update * Pointer update * updated pointer to NCAR/ccpp-physics and reverted .gitmodules
…semble forecasts; remove obsolete physics suites; get WE2E tests to run on cheyenne (#287) ## DESCRIPTION OF CHANGES: ### Bugs fixed: * In exregional_make_orog.sh, remove the else-statement that causes the script to exit if the suite is not FV3_RRFS_v1beta. * In exregional_run_fcst.sh, remove lines that create a symlink in the run directory to the model_configure file in the cycle directory. These lines seem to have been inadvertantly reintroduced into the script and cause ensemble forecasts to fail. ### Other modifications: * Remove suites FV3_GSD_SAR_v1 and FV3_RRFS_v0 from workflow since they are no longer in ufs-weather-model. Also remove the WE2E test configuration files for these suites (config.regional_013.sh and config.regional_016.sh). * In exregional_make_orog.sh, for the RRFS_v1beta suite, modify the command that copies the orography statistics files needed by the drag parameterization such that only files matching *_ls*.nc and *_ss*.nc are copied instead of everything (because the source directory may contain other files that do not need to be copied). * In the WE2E configuration file for the RRFS_v1beta suite (config.FV3_RRFS_v1beta.sh), change the location where the additional orography files needed by this suite are copied from to a common location rather than a user directory. * Remove unused script create_model_config_files.sh. * Rename the function (and file) create_model_config_file(.sh) to create_model_configure_file(.sh) because the file that this function creates is called model_configure, not model_config. * Modify WE2E test configuration files as well as the test run script (tests/run_experiments.sh) to get the tests to run more easily on cheyenne. Still need to make a manual change to the settings in run_experiments.sh, but this made it possible to run the tests. ## TESTS CONDUCTED: Ran all 26 WE2E tests both **on hera and cheyenne**. 24 of the 26 succeeded. Details: * regional_010 failed, but it was already broken. * user_download_extrn_files failed. It seems to have failed to obtain the external model files from NOMADS (and this step is done during workflow generation, not as part of any workflow task). This test is completely unrelated to this PR, so the failure may have already existed in the develop branch. * The remaining 24 tests (including the one for the FV3_RRFS_v1beta suite) succeeded without problems. Note that the FV3_RRFS_v1beta suite was also tested on the GSD_HRRR3km grid. This failed at around hour 4 (for a 6-hour forecast) with a very non-informative error. This test was also tried previously with hash 8165575 from the NCAR fork of ufs-weather-model (in the dtc/develop branch), and that finished successfully. Not clear what changed between these two versions of ufs-weather-model. ## OTHER CONTRIBUTORS: @JeffBeck-NOAA
Description
Building the coupled model with DEBUG=Y fails on orion. The same commands build the model on hera successfully.
To Reproduce:
Checkout ufs-weather develop branch:
module use modulefiles/orion.intel
module load fv3_debug
CMAKE_FLAGS="-DS2S=ON -DDEBUG=ON" CCPP_SUITES="FV3_GFS_2017_coupled,FV3_GFS_2017_satmedmf_coupled,FV3_GFS_v15p2_coupled" ./build.sh >output 2>&1 &
Output
Build fails:
Build directory on Orion:
/work/noaa/marine/dworthen/ufs_tod
The text was updated successfully, but these errors were encountered: