-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node ID numbering changes mean imod-qgis timeseries plot doesn't fetch the right data #1306
Comments
Do you see this going wrong? I thought the code was already adopted for this: Ribasim/ribasim_qgis/widgets/dataset_widget.py Lines 321 to 329 in f43010b
|
I think you're referring to something else. I mean these lines, essentially: I don't think the keys match the feature IDs. I.e. we're creating a mapping of node_id => dataframe. Then we're searching for feature id's, which aren't node ID's. The reason I mention this is because I was getting weird selections. |
Ok right, so in imod-qgis there are the implicit assumptions that |
Indeed. I think the unfortunate thing is it required imod-qgis changes, and a new release of the plugin for people to use it. |
Yeah it's quite bad. How about #1316 as a temporary fix? |
The idea was that the Node table `fid` would not be used anymore, but #1306 showed that is unfortunately not yet the case. So this changes the `fid` after it is initially written to be equal to the `node_id`. Any users should still not rely on the `fid`, because this is only temporary. This is like #1311 but now also catching non unique node IDs on `model.write`. It also provides a temporary fix to #1306. It's not great, but I feel that especially #1306 is bad enough to warrant a quick fix. This would've been a bit cleaner to implement using #1312 to avoid having to read and re-write the Node table, but that PR still has issues we don't understand, so best not to wait on that. ![image](https://github.com/Deltares/Ribasim/assets/4471859/3efc2f8c-6be5-459d-929a-7ce8568fca3d)
Fixed by this: Deltares/imod-qgis#79 |
I think #1306 is important enough to warrant a quick release.
Previously, the node feature ID was equal to the
node_id
. This meant that we could directly use the feature id to locate timeseries in the result dataframes.Because
node_id
is no identical to the feature ID, the timeseries plot will either not find the results (because the FID doesn't exists as a node_id), or it will show the wrong timeseries.It only goes well if your model node_id matches the feature ID as before.
The text was updated successfully, but these errors were encountered: