# Apparent error running SMOKE test case

**URL:** <https://forum.cmascenter.org/t/apparent-error-running-smoke-test-case/4155>\
**Category:** Run Errors and Warnings\
**Created:** [June 7, 2023, 11:21pm UTC](https://forum.cmascenter.org/t/apparent-error-running-smoke-test-case/4155 "2023-06-07T23:21:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DLyder](https://avatars.discourse-cdn.com/v4/letter/d/7bcc69/32.png) [@DLyder](https://forum.cmascenter.org/u/DLyder)\
**Post date:** [June 7, 2023, 11:21pm UTC](https://forum.cmascenter.org/t/apparent-error-running-smoke-test-case/4155/1 "2023-06-07T23:21:06Z")

</div>

Hello Everyone,  
I have just installed the SMOKE 4.9 package as per the instructions and everything seems to run. However, when I look at the biogenic log file (attached) it appears there is a problem opening a binary file. It is not clear to me from the log what the problem may be. I don’t think it is related to the Missing environment variable EXECUTION\_ID message but…?  
I am able to properly form bgts\_l.20200101.nf, b4gts\_s.20200101.ncf and soilout.20200102.ncf but not besi4\_norm\_emis,12US12.ncf or b3grd.2016v3.2022Apr20.12US1.ncf (though I am not expecting to form this given the provided met data is only for Jan 1, 2020).  
It seems things are working but the improperly opened binary file seems to be indicating otherwise?  
Thanks.  
David

 ![snapshot1](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/3/3cfba2e74e148c385edac83696b06a47bd941617.png)

---

<div class="post-metadata">

**Author:** ![cseppan](https://avatars.discourse-cdn.com/v4/letter/c/6de8d8/32.png) [@cseppan](https://forum.cmascenter.org/u/cseppan)\
**Post date:** [July 5, 2023, 6:58pm UTC](https://forum.cmascenter.org/t/apparent-error-running-smoke-test-case/4155/2 "2023-07-05T18:58:05Z")

</div>

Since the output files were created successfully (I’m assuming Tmpbeis4 completed normally), I’m not sure there’s any program error happening. From the screenshot, it’s hard to say where the strange characters are in the log file.
