James Tomlinson
James Tomlinson
@BaptisteFrancois this is a known issue with a circular reference when loading parameters - see https://github.com/pywr/pywr/issues/380 for the original report and also #641 is the eventual branch that will fix...
I think you can give it a name key as part of its definition: `"name": "my parameter"`
Can you provide a cut down version of a model that experiences this problem?
Can you give me the full traceback of the error? It fails when you include a recorder for the area in your model? I do wonder if this is the...
Can you try defining everything in the "parameters" section? I don't think you will need to set the area in attribute of the reservoir node.
> product of the reservoir area and an evaporation rate defined in a dataframe parameter Is this a custom parameter? Instead of using the reservoir area directly, make it use...
@BaptisteFrancois I've had a look at this. I can see the issue is in fact #380. And happens because, 1. `don_pedro_area` parameter needs to be defined in the parameters section...
Hi @aiduran, Pywr currently requires all data to be units of V and V/day. You can use m3, Mm3 or Ml but all flows must be entered as per day...
Model has a name and description. So that should be easy enough.
You didn't like it printing the model's title?