# \#fest-c

**URL:** https://forum.cmascenter.org/tag/fest-c/69.md

[Latest](https://forum.cmascenter.org/latest.md) · [Categories](https://forum.cmascenter.org/categories.md) · [Tags](https://forum.cmascenter.org/tags.md)

---

## [Error with generateBeld4Data / computeGridLandUse\_beld4](https://forum.cmascenter.org/t/error-with-generatebeld4data-computegridlanduse-beld4/6290)

<div class="topic-metadata">

**Author:** [@mkharkey](https://forum.cmascenter.org/u/mkharkey)\
**Replies:** 0\
**Last updated:** [October 8, 2026, 7:05pm UTC](https://forum.cmascenter.org/t/error-with-generatebeld4data-computegridlanduse-beld4/6290 "2026-10-08T19:05:16Z")

</div>

Hello, it looks like even with enough RAM and recompiling the SA tools (version 4.4), I’m having trouble with generateBeld4Data. I’m running it through the FEST-C interface (version 1.4); the run script is generated thr…

---

## [Error with compute\_EPICSiteData](https://forum.cmascenter.org/t/error-with-compute-epicsitedata/6283)

<div class="topic-metadata">

**Author:** [@mkharkey](https://forum.cmascenter.org/u/mkharkey)\
**Replies:** 1\
**Last updated:** [September 16, 2026, 9:13pm UTC](https://forum.cmascenter.org/t/error-with-compute-epicsitedata/6283 "2026-09-16T21:13:15Z")

</div>

Hello, I’m working with FEST-C version 1.4, installed on a linux machine with Spatial Allocator version 4.4. When running the crop site info generation step from the GUI, the process just stops (no output files written)…
