-
The initial state: as I said, through the initial state of the (derived) state variables - which for the ASU model is the M vector.
So, I would assume: M[X_BH], M[X_BA], M[S_S], M[X_S] for ASM1.
As for the top-level interface variables, or the integrator settings, I don't see what is the relevance to this particular issue
-
You supply substrate through an input file at a set time (over a short time period) right?
So I assume, you only need to set the initial state of your batch reactor. This is done by setting the initial conditions of S and X - as masses in WEST, so if you are dealing with concentrations, you need to convert your data. Then it all depends on what category you are using: if it's a custom category, with perhaps only S and X as components, it's straight-forward. Otherwise, you need to distribute "substrate" and "biomass" over the relevant species.
-
What do you mean by "data import"? Are you referring to an input file; or to (experimental) data e.g. that are to be plotted on a graph?
And by "batch reactor"? There's no batch reactor as such in the WEST library, so I assume you are using e.g. an ASU tank with either no input (and the initial concentration of substrate and biomass inputted as initial conditions) or with a concentrated input (i.e. a spike).
Your other questions are also difficult to answer, because they are too generic and may depend on the category you are using.
Please provide more details about your test case.
-
Then I would definitely inspect all the derived state variables for one seems to be NAN.
If you cannot identify the problem, please send your case to mikebydhi
-
I meant: the "wwtp.base.msl" file.
It is part of the standard WEST library.
The declaration of the OBJ M should be at around line 96.
-
The error message is actually quite clear: it suggests that a derivative is NAN which is typically the result of a division by zero.
If you are using a custom Category, you may have not initialized the M vector - which can be done in the base.msl file where M is defined (around line 96), or at the level of the project (the first option being obviously more effective).
Should this not help, you may need to carefully check all derived state variables and identify the culprit(s).
-
Then, send us the case. One last check: make sure you are using the release version (build date Dec 16 2013, 22h01)
-
No: it should be available anyway - in fact, the "manipulated" is the "to" variable, in your case on the splitter block.
-
In WEST 2014, you first need to create a top-level interface variable (right-click on canvas -> context menu) of the appropriate type and causality.
The new variable will then be available in the drop-down of your Input block and you can create the link to the manipulated variable of the splitter.
-
Indeed very strange. Will you please send us (mikebydhi) your text file, as is?
We can continue this discussion through the usual technical support channel.
Should anything relevant for other users emerge, we'll post it back here.