# Grid cell temperature out of range **URL:** \ **Category:** SMOKE\ **Created:** [September 10, 2025, 2:53am UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992 "2025-09-10T02:53:28Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 10, 2025, 2:53am UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/1 "2025-09-10T02:53:28Z")
I am running SMOKE v4.8.1 for the 2019 emission platform. When I run ‘Monthly\_onroad\_ca\_adj\_RPD\_daily\_12US1\_2019ge\_cb6\_19k.csh’, it showed the following error. I don’t know why the Grid Cell temperature is a large negative value. How to fix it? All the data are downloaded from the CMAS google drive. _\*\*\* ERROR ABORT in subroutine MOVESMRG ERROR: Grid cell temperature -459.67 out of range of minimum emission factor data 0.00 Date and time 0:00:00 June 1, 2019 (2019152:000000)_ ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [September 10, 2025, 12:42pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/2 "2025-09-10T12:42:32Z")
What meteorological data are you using for this run (especially the METCRO2D files)? It is possible some data got corrupted at some stage of the data transfer. Can you provide the Movesmrg log for the day that failed? ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 10, 2025, 6:21pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/3 "2025-09-10T18:21:44Z")
Attached is the log file. [movesmrg\_RPD\_onroad\_ca\_adj\_jun\_2019ge\_cb6\_19k\_20190601\_12US1\_cmaq\_cb6ae7.txt](https://forum.cmascenter.org/uploads/short-url/zMSaC6DikG33eW1bEMNPwQYw2QH.txt) (162.6 KB) I used the EQUATES 2019 MCIP files. To test your hypothesis, I switched to another set of MCIP files from our own WRF simulations, but got the same error. So it looks like it not caused by the MCIP input file. Hao ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [September 11, 2025, 12:40am UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/4 "2025-09-11T00:40:27Z")
We have not seen this issue when we processed this year of data. Have you considered trying a newer version of SMOKE? Perhaps there is a memory allocation issue causing the value to be zero that is not properly handled. Also, are you using a natively compiled version of SMOKE or one you downloaded? ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 11, 2025, 2:47am UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/5 "2025-09-11T02:47:11Z")
I am using the SMOKE v4.8.1 contained in the zip file from the UNCI Google Drive. All other sectors such as RPD/RPH/RPHO/RPP/RPS/RPV are finished for CONUS and CA, exceipt this one. I can try new version of SMOKE. Any suggestion on the specific version for the 2019ge platform? ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 11, 2025, 3:39pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/6 "2025-09-11T15:39:55Z")
I tried SMOKEv4.9 precompiled executbile, and got the same results. Is there any option to overide this warining like [2016 NEI platform: Mobile sector error: grid cell temperature out of range](https://forum.cmascenter.org/t/2016-nei-platform-mobile-sector-error-grid-cell-temperature-out-of-range/1457)? ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 11, 2025, 9:40pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/7 "2025-09-11T21:40:36Z")
One more thing. the Value of -459.67 is absolutel zero in Fahrenheit. Is it possible there is a conversion error if MCIP to SMOKE? MCIP has the temperature in K, may 0 for missing value? ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [September 11, 2025, 9:53pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/8 "2025-09-11T21:53:14Z")
We agree with this being absolute 0 and did not find this issue when we ran SMOKE with the same data, so are wondering if there could be a data download error, or an error in the compiled version of SMOKE running on your computer. If you scan the data with a netCDF data inspection tool, do you see 0 in there for the temperature data? ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 12, 2025, 1:29am UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/9 "2025-09-12T01:29:13Z")
I don’t think it is caused by data corruption, because I have this error for all days in June 2019. Second, I tried another MCIP dataset using WRF simulations conducted in our group, but found the similar errors. Lastly, the same MCIP inputs are successufly used to conduct 12US1 RPD/H/HO/P/V/S runs and California RPH/H0/P/V/S runs. The only problem happened in ca\_adj\_RPD. Is it possible the eftables of California are corrupted during data upload or transfer? ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [September 12, 2025, 7:42pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/10 "2025-09-12T19:42:24Z")
Hello again. We recall that there were some segmentation faults cropping up prior to SMOKE v5.1. Can you try using the latest version of SMOKE (5.2.1) to see if you still have the error? If the error still occurs, we could re-examine the CA emisison factors. ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 13, 2025, 1:50am UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/11 "2025-09-13T01:50:46Z")
I tried to use SMOKE v5.1, and it stopped at the same location without showing the -459.67 error. The command line shows the following error. Seems like the temperature still has problem. forrtl: severe (408): fort: (3): Subscript #2 of the array MTMP\_INVT has value 0 which is less than the lower bound of 1 Image PC Routine Line Source movesmrg 000000000041ADEA movesmrg 1123 movesmrg.f movesmrg 00000000004080BD Unknown Unknown Unknown libc-2.28.so 0000145F54C327E5 \_\_libc\_start\_main Unknown Unknown movesmrg 0000000000407FDE Unknown Unknown Unknown 6747.576u 15.814s 2:09:49.39 86.8% 0+0k 389600+199064io 0pf+0w now checking log file /data/chemstg99/haohe/2019v1/2019ge\_cb6\_19k/intermed/onroad\_ca\_adj/RPD/logs/movesmrg\_RPD\_onroad\_ca\_adj\_jun\_2019ge\_cb6\_19k\_20190601\_12US1\_cmaq\_cb6ae7.log * * * - ERROR detected in logfile: - /data/chemstg99/haohe/2019v1/2019ge\_cb6\_19k/intermed/onroad\_ca\_adj/RPD/logs/movesmrg\_RPD\_onroad\_ca\_adj\_jun\_2019ge\_cb6\_19k\_20190601\_12US1\_cmaq\_cb6ae7.log * * * ERROR: detected in movesmrg ERROR: Running smk\_run for part 4 for 20190601 ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [September 15, 2025, 12:27pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/12 "2025-09-15T12:27:56Z")
Can you try setting MTMP\_OUTPUT\_YN = N and let us know if that helps ---
**Author:** ![haohe.umcp](https://avatars.discourse-cdn.com/v4/letter/h/b19c9b/32.png) [@haohe.umcp](https://forum.cmascenter.org/u/haohe.umcp)\ **Post date:** [September 17, 2025, 12:36pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/14 "2025-09-17T12:36:01Z")
Set MTMP\_OUTPUT\_YN = N works and solve the problem! I searched online but didn’t find the explanation about this option. Can you explain what function it controls? Thanks! ---
**Author:** ![eyth.alison](https://avatars.discourse-cdn.com/v4/letter/e/7ab992/32.png) [@eyth.alison](https://forum.cmascenter.org/u/eyth.alison)\ **Post date:** [September 17, 2025, 12:58pm UTC](https://forum.cmascenter.org/t/grid-cell-temperature-out-of-range/5992/15 "2025-09-17T12:58:02Z")
When MTMP\_OUTPUT\_YN = Y, Temporal will output additional intermediate files which support the generation of emissions reports via Smkreport such as hourly reports. It must require additional data that triggered this error. We are so glad to hear that the problem is fixed! Hopefully tracking it down has had some useful side effects. Using a newer version of SMOKE is a good idea for a variety of reasons because it includes various bug fixes and feature additions as well.