Versions:
Three errors/warnings in a row are issued upon clicking the Run button in DoE. After selecting not to save a diagnostic report for each of them, the runs do start as expected, even if there seems to be some issues with the GUI and choice of local queue. So not a fatal bug, only scary.
It seems the error happens when points are excluded after the import, meaning inside the plot or design table.
Are you running MFiX from Nodeworks? If so, I am shocked that still works.
Well, first I’m launching MFiX, then I go via the Nodeworks tab at the bototm after the case has been setup, much like what is described in the examples. Should this not work? Or are there better ways?
I am just surprised that it still works at all. It probably hasn’t been tested by @onlyjus or myself in 7 years
But all the talk about Nodeworks MFiX plugin and so on, isn’t that exactly this? I don’t get that this should be incorrect while there still is public documentation on it, and not very old Nodeworks releases.
Nodeworks has not been under active development since 2017. Yes, Justin keeps fixing issues when they arise sporadically when someone uses it. I’m not saying that you are doing anything wrong, I’m just shocked that it still works.
