Before you run Met4moves, can you check whether your METMOVES input file covers your modeling date or not? Your METMOVES input file may not have August 2, 2016?
My METMOVES input has all date from July 1 to Auguet 31 so I believe that is not the problem. Once I add 4013 to the met4move to have a new METMOVE for RPP simulation, I got a new error from mrgmoves log file:
ERROR: No factor file foundfor reference county000000001049in reference county factors list.
I believe county ….01049 is from Alabama. Do you have Alabama emission factors?
Thanks for your help. Once I add 1049 to emission factor file, the error get back to:
*** ERROR ABORT in subroutine MOVESMRG
Could not find minimum or maximum temperatures for county 000000004013 and episode month 8
Date and time 0:00:00 Aug. 5, 2016 (2016218:000000)
Hi, I got another error when testing mrgmoves program. I got:
At line 260 of file /uufs/chpc.utah.edu/common/home/holmes-group1/copycky/model/smk_4.8//subsys/smoke/src/movesmrg/rdmrclist.f
Fortran runtime error: Index ‘805’ of dimension 1 of array ‘reffip’ above upper bound of 804
It seems like the number of reference in MRCLIST it too much than the setting in rdmrclist.f. I got 804 lines in my MRCLIST file. Do you have any suggestion for this bug? Hope to receive your help. Thanks!
That does not make sense. I do not believe there are more than 804 reference counties. The latest version of RPD MRCLIST input file only holds 658 entries in the file (329 reference counties * 2 fuel months). I think there is something wrong with your MRCLIST input file. Can you upload the MRCLIST input for me to review?
Thanks for your reply. I attached the mrclist is modified and used in this run.
mrclist_RPP_2016version1_AQ_CB6_02aug2019_05aug2019_v0.txt (72.2 KB)
I made some modification on the MRCLIST I was using for this run. Since I got errors using SRGPRO, SRGDESC, MCXREF, MFMREF and MRCLIST from 2016v1 platform:
*** ERROR ABORT in subroutine MOVESMRG
Could not find minimum or maximum temperatures for county 000000004013 and episode month 8
Date and time 0:00:00 Aug. 2, 2016 (2016215:000000)
Thus I used SRGPRO, SRGDESC, MCXREF, MFMREF from 2017 platform and the error turned to:
ERROR: No factor file foundfor reference county000000001049in reference county factors list.
I check eftables folder and found there are some county references not included in mrclist from 2016 version but listed in 2017 so I added them to the mrclist I am using thus having 804 lines in this file.
Once I used 2017 platform as input (MCXREF, MFMREF, SRGPRO_PATH, SRGDESC and COSTCY) for both Met4moves and RPP simulation, the error turned to:
*** ERROR ABORT in subroutine MOVESMRG
Could not find minimum or maximum temperatures for county 000000004013 and episode month 8
I was wrong. There are 804 files listed in the MRCLIST file for the RPP run, and I do not see any issue with the MRCLIST input file.
However, I am not sure what you are trying to say here. Do you mix and match between 2016 and 2017 platform packages for RPP runs?
Yes, since I got error when using 2016v1 platform input for RPP so I am trying to merge 2017 inputs with run script in 2016v1 platform, and I got the error shown in the standard log file:
At line 260 of file xxxx/rdmrclist.f
Fortran runtime error: Index ‘805’ of dimension 1 of array ‘reffip’ above upper bound of 804
It seems like the program can’t read mrclist morethan 804 lines?
I am concerned that there are some issues that occurred when you mixed these two platform inputs. I would strongly recommend you to use the same platform files for this run.
No, there is no problem with reading the MRCLIST input file. The code can read the file and allocate the memory based on the number of entries in the file. If the code has an issue, then it should happen for other sectors like RPD, RPV,
Thanks for your patients and your valuable time. Once I turned back to use the original input from the 2016v1 platform, the error turns to previous one again:
*** ERROR ABORT in subroutine MOVESMRG
Could not find minimum or maximum temperatures for county 000000004013 and episode month 8
Date and time 0:00:00 Aug. 2, 2016 (2016215:000000)
I had re-run met4moves using same setting. Do you know how could I do with this?
I solve this problem. I have to run MET4MOVES using an executable I compiled with an Intel compiler so that the SMOKE_DAILY_xxx file contains information needed for the RPP run. But once I compile executables with the GCC compiler, there are some unknown problems even though the MET4MOVES run successfully. Perhaps some issue with the node and compiler themselves. Thanks a lot for your time and help for my case.
1 Like
That is wonderful news! Glad to hear that you are now able to move forward.