cpdmulde

Hi,

Indeed, the changing of the [i]#ifdef statements[/i] did not solve the problem. I went through my model .msl file and found the weirdest typo: a '+' sitting in the middle of an otherwise empty line. Removing this also got rid of the problem. Still weird it does not pick this up as a syntax error though.

With regards to other possible causes, would you then suggest to got through the model implementation and double-check every equation left hand side, Filip? Just in case other users ever bump into the same error message.

Best and thanks for your help!

Hi Enrico,

Thanks for the answer and the nice tip at the end, I think I found the source of the error (due to technical problems, I cannot check at this time, I will confirm in this thread once I can); I was using an [i]#ifdef StandardCategoryModels[/i] at the beginning of my class definition, while I'm only calculating state variables for an own custom version of ASM2d, and not for other models. I've changed this to the relevant [i]#ifdef ASM2dChemTemp[/I]. If this wasn't the source of the error, it would have probably popped up sooner or later.

Thanks for the help!

Hi Enrico,

I am indeed working in .msl-files and using the 'normal' WEST Model Editor. I'm running the 2018dev version of WEST though.
If with coupled-model you mean that my model would under the hood contain multiple tanks or other submodels, then no, I'm not using a coupled-model (not using coupling <- {}, or connecting variables/parameters in any other way).

One more 'unconventional' thing I do is calculate the interface.Outflow variables explicitly, and not through a FOREACH statement, e.g.:

[i]interface.Outflow[S_I] = -interface.Inflow[S_I]
interface.Outflow[S_O] = -interface.Inflow[S_O][/i]
etc...

instead of

[i]{FOREACH Comp_Index IN {IndexOfSolvent .. IndexOfLastSolubleComponent}:
      interface.Outflow_Unfiltered[Comp_Index] = - interface.Inflow[Comp_Index] * state.f_Out_Unfiltered
                - interface.Backwash * interface.Inflow_Backwash[Comp_Index];
    };[/i]

Could the problem hide somewhere in there? Just trying to narrow down which piece of code I best start checking when looking for the source of the error.

Hi,

I'm building a new version of the sand filtration model currently present in the default Library. I was able to implement what I wanted, checking along the way for syntax and other errors in the new .msl file and the new CLASS that I created. When I open my WEST project, add the sand filter block and change the properties of the block to use the model I want, I get the following error when trying to run a dynamic simulation:

[i]System error: Error in tree structure[/I]

Since I've never encountered this error and since it's also not very instructive in telling me where to look, I was wondering if anyone has some experience with this error message and has possibly found a solution for it.

Thanks in advance,
Chaïm

Hi,

I currently have a similar issue, trying to run the MBBR model in WEST2018dev, but it is very slow, also in steady state simulations. It takes about a minute to simulate roughly 0.002 days. Could you share the solution here as well Enrico?

Best regards,
Chaïm

Hi Sovanna,

Just FYI, we have Python code that does something similar indeed: it calls tornado and runs a WEST project file. We've been able to parallelise simulations this way, something you were also trying to achieve I guess. I you're interested in more information, you can always contact me!

Best regards,
Chaïm

I've tried both suggestions, thank you for those.
Still doesn't work though, so I'm contacting MIKE, adding both project folder and library.

Thanks for your time!

Chaïm

Hello,

When working with my model, running a steady state simulation worked before. I changed some things, along which the name of the output file, the time interval to write data to the output file, and the stop time of the steady state simulation. I might have changed some control parameters as well, but I can't quite recall.
After these changes, WEST throws the error as shown in attachment, completely out of the blue. Very inconvenient as well, because it keeps popping up when clicking OK, making that I have to force WEST to shut down, open it again, change something, and see if it worked. It hasn't so far, so I've done this a couple of times already, kind of tedious.
I've tried running a dynamic simulation (so without first running steady state) and that works.

Any idea what the error message might mean?

Best,
Chaïm

Dear Enrico,

Upon opening the included .msl-file in wwtp.base.msl (wwtp.VolumeASMConversionModel.body.msl) and expanding all files this includes in the Includes tab, no red 'X's are shown. I have no idea what file would be missing, but I did notice (as you can see in one of the previously attached figures), that the "no such file or directory" is thrown for KOSIM.BlockLib.xml..cpp.msl, i.e. a file with two dots between xml and cpp.

I was also surprised to see an absolute path in the model library, which doesn't seem like good practice from my predecessors, as it limits the reuse possibilities of the library. This concerns the model library WESTforKOSIM that is used for courses on integrated modelling at BIOMATH.

Could this maybe be due to upgrading to WEST2016?

I hope this provides some more information.

Hi,

I'm posting this here since I can't seem to be able to acces the Tornado forum on userarea.west.mikebydhi.com.
I've been using a model, constructed and working in WEST2014, in WEST2016 for some time as well already, and everything runs as planned, i.e. no errors or bugs. When today I reopened the model however, I tried to change a control parameter and got the error message displayed in the attached figure. When hitting OK, and trying to do anything else (click on anything, close...), the same message pops up, executing the action after I hit OK again.
Saving, closing and reopening works, and the new parameter value is in place.

Anyone that can help me avoid having to save, close and reopen the model for every parameter change?
Thanks!