# Machine Learning in Ignition using MATLAB

**URL:** <https://forum.inductiveautomation.com/t/machine-learning-in-ignition-using-matlab/56053>\
**Category:** Module Development\
**Tags:** machinelearning, ignition79\
**Created:** [February 11, 2022, 11:38pm UTC](https://forum.inductiveautomation.com/t/machine-learning-in-ignition-using-matlab/56053 "2022-02-11T23:38:19Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 18, 2022, 10:03pm UTC](https://forum.inductiveautomation.com/t/machine-learning-in-ignition-using-matlab/56053/4 "2022-02-18T22:03:21Z")

</div>

So, showing the whole thing is not on the table. Sorry. But one utility class I wrote will help you through the trickiest part of it:

[FieldClassBuilder.java](https://www.automation-pros.com/streamer/FieldClassBuilder.java) (Note the MIT License.)

This builder will assemble any desired classes from anywhere in your module, including any dynamically loaded classes you might access, into a _ **generated** _ class with a public static final field for each supplied class.

The output from `build()` is suitable for use with `ScriptManager.addScriptModule()` in your various hook classes.

I recommend Google’s `ClassPath` utilities (which are distributed with Ignition) to enumerate classes in dynamically loaded jars.

(Moving this topic to Module Development…)

---

_[View the full topic](https://forum.inductiveautomation.com/t/machine-learning-in-ignition-using-matlab/56053)._