Hi Ligross,
I must admit I am ignorant of architecture of code and data storage, I figured this was an easy problem once you had the model created and the criticality search function defined, and that this was one of the main purposes of a criticality function (following depletion), but clearly there is something I don’t understand. Thinking this, I added a little bit of code to pass in the materials.xml that I exported from the results into the parametrized model, as you can see from this post I made here helping someone with a similar issue,
This worked for a simplified model I had of only a 2 by 2 infinite array of CANDU fuel, but when I tried to use my full CANDU model it gives me the STOD error.
So something is getting corrupted or confused during the model building. It might have to do with how I have my model build dynamically. It gives this error even outside of the criticality search function during a normal transport run. I tried to troubleshoot and find which float could be incorrect, but I couldn’t find anything, everything looks normal even looking at the hidden code. At this point, I will probably just make a simplified function that evaluates the k-eff and how close it is to criticality, which will keep running transports and evaluating the result as if someone was manually adjusting the concentration, without using a parametrized model, since for my case I am modifying a variable that has a simple relationship with k-eff (boron is a strong poison, especially absorption, so increasing concentration will always lower the k-eff) therefore there shouldn’t be issues with converging.