# Running WBDUST module as a standalone program?

**URL:** <https://forum.cmascenter.org/t/running-wbdust-module-as-a-standalone-program/2098>\
**Category:** Ancillary Inputs\
**Created:** [February 19, 2021, 3:00pm UTC](https://forum.cmascenter.org/t/running-wbdust-module-as-a-standalone-program/2098 "2021-02-19T15:00:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![skunwar](https://avatars.discourse-cdn.com/v4/letter/s/9f8e36/32.png) [@skunwar](https://forum.cmascenter.org/u/skunwar)\
**Post date:** [February 19, 2021, 3:00pm UTC](https://forum.cmascenter.org/t/running-wbdust-module-as-a-standalone-program/2098/1 "2021-02-19T15:00:30Z")

</div>

Is it possible to run the WBDUST inline option of CMAQ as a standalone program independent of CCTM.exe? If that is difficult to implement, would it be possible to turn everything else off in CCTM.exe (either at compilation or while running) except WBDUST option?

---

<div class="post-metadata">

**Author:** ![foley.kristen](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@foley.kristen](https://forum.cmascenter.org/u/foley.kristen)\
**Post date:** [February 22, 2021, 4:18pm UTC](https://forum.cmascenter.org/t/running-wbdust-module-as-a-standalone-program/2098/2 "2021-02-22T16:18:36Z")

</div>

We have not tried either of these options with our own internal testing and so do not have any guidance on the difficulty or robustness of either approach.