from wrf-sfire.

@llsalazar
Can you please provide some details with "line starts looping at rsl.error.0000 and never stops". I see in your rsl.error.0000 multiple lines with a warning about extinction moisture, is that the looping you are referring to? Also, I see at the beginnng
git commit c959580 1 file changed, 1 insertion(+), 1 deletion(-)
which means something changed against the version on github and we do not know what. If you could run git diff in the directory with the code and send the output please. Thanks!

from wrf-sfire.

Good morning @janmandel @adamk0
Thank you for answering me so fast.

@adamk0 We are doing the test that you recommended and solving the first errors that appear in the rsl.error.0000 file.

@janmandel yes, it's those multiple lines with a warning about moisture extinction that start looping in rsl.error.0000 and never stop. We run git diff in our directory with the code and this is the output.

[u101126@login03 WRF-SFIRE]$ git diff
diff --git a/arch/Config.pl b/arch/Config.pl
index f31b33827..008994d19 100644
--- a/arch/Config.pl
+++ b/arch/Config.pl
@@ -248,7 +248,7 @@ while ( substr( $ARGV[0], 0, 1 ) eq "-" )

environment variables JASPERLIB and JASPERINC to paths to library and

include files to enable this feature prior to running configure.

• $I_really_want_to_output_grib2_from_WRF = "FALSE" ;

• $I_really_want_to_output_grib2_from_WRF = "TRUE" ;

  if ( $ENV{JASPERLIB} && $ENV{JASPERINC} && $I_really_want_to_output_grib2_from_WRF eq "TRUE" )
  {

If you need more details, please let me know.

Thanks again for your help

from wrf-sfire.

Good morning @adamk0 @janmandel

The problem with the sfire was solved, this problem appeared because the way it managed the nodes was not correct. We managed to run a successful simulation with WRF-SFIRE

Thank you for your help

from wrf-sfire.

from wrf-sfire.

Hello @adamk0

The problem was that I was using a wrong line in the jobs. I was using a parameter used mainly for OpenMp jobs instead of MPI jobs.

from wrf-sfire.