# Could not read LUFRAC\_01 from GRID\_CRO\_2D in CMAQv5.2.1 **URL:** \ **Category:** MCIP\ **Created:** [February 9, 2021, 1:34pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060 "2021-02-09T13:34:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![skunwar](https://avatars.discourse-cdn.com/v4/letter/s/9f8e36/32.png) [@skunwar](https://forum.cmascenter.org/u/skunwar)\ **Post date:** [February 9, 2021, 1:34pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060/1 "2021-02-09T13:34:49Z")
I am trying to run CMAQv5.2.1 with emissions input from **2016fh\_16j** and WRFv3.9.1.1 (processed by MCIPv5.1), and I get this abort error right in the beginning: ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/b/bd42cc7c203f7ac47ed3420f9735e3c56e88db20.png) MCIPv5.1 gives LUFRAC\_CRO output file with the variable LUFRAC variable in 40 layers (from NLCD40 land use of WRF), and the default runscript of CMAQv5.2.1 does not read in LUFRAC\_CRO file. MCIPv5.1 does not provide the LUFRAC\_01 variable in GRIDCRO2D file. Should I use an earlier MCIP version which does that - if so, which version of MCIP would output desired LUFRAC\_01 variable? ---
**Author:** ![tlspero](https://avatars.discourse-cdn.com/v4/letter/t/bb73d2/32.png) [@tlspero](https://forum.cmascenter.org/u/tlspero)\ **Post date:** [February 9, 2021, 2:00pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060/2 "2021-02-09T14:00:23Z")
@skunwar – MCIPv4.5 will provide the LUFRAC\_xx fields in the GRIDCRO2D file. If you want to keep using MCIPv5.1, you can run your data through MCIPv4.5 for one time step to create the GRIDCRO2D file with all of the LUFRAC\_xx fields that you need. –Tanya ---
**Author:** ![skunwar](https://avatars.discourse-cdn.com/v4/letter/s/9f8e36/32.png) [@skunwar](https://forum.cmascenter.org/u/skunwar)\ **Post date:** [February 9, 2021, 6:18pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060/3 "2021-02-09T18:18:29Z")
Worked perfectly - thanks for the trick! ---
**Author:** ![msospedra](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@msospedra](https://forum.cmascenter.org/u/msospedra)\ **Post date:** [March 8, 2021, 7:11pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060/4 "2021-03-08T19:11:27Z")
Hi there, I am having the same problem. I am running CMAQv5.3.2 and I get the same error regarding missing LUFRAC\_XX fields. However, because my WRF fields are generated using WRF4.1.1, this workaround doesn’t work for me. MCIP4.3 or 4.5 do not support this WRF version. Is there any other option? Also, why MCIP5 does not generate LUFRAC fields even though CMAQ requires them? is there any specific reason? (maybe CMAQ is transitioning towards not needing LUFRAC in the future?) Or are there any specific CMAQ settings that do not require LUFRAC\_XX? Thanks, Marc ---
**Author:** ![msospedra](https://avatars.discourse-cdn.com/v4/letter/m/ac91a4/32.png) [@msospedra](https://forum.cmascenter.org/u/msospedra)\ **Post date:** [March 8, 2021, 10:46pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060/5 "2021-03-08T22:46:09Z")
Hi all, It turns out that I was using one sample run script (run\_cctm\_2010\_4CALIF1.csh) that had the definition of the LUFRAC\_CRO file commented out: #setenv LUFRAC\_CRO $METpath/LUFRAC\_CRO\_${YYYYMMDD}.nc With this undefined, CMAQ was checking GRIDCRO2D for the LUFRAC\_XX fields. Once I uncommented this out, and because I had the LUFRAC\_CRO generated with MCIP5, CMAQ seems to be working. Marc ---
**Author:** ![Alpha\_Su](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.cmascenter.org/alpha_su/32/2795_2.png) [@Alpha\_Su](https://forum.cmascenter.org/u/Alpha_Su)\ **Post date:** [December 18, 2022, 3:07pm UTC](https://forum.cmascenter.org/t/could-not-read-lufrac-01-from-grid-cro-2d-in-cmaqv5-2-1/2060/6 "2022-12-18T15:07:03Z")
Thank you! the solution help me out. 😀