nens / 3di-modeller-interface-installer Goto Github PK

Activate Python Macros in QGIS: Settings -> Options -> General -> Enable Macros and set it on Always

the profile is missing the plugins.lizard.net/plugins.xml repo
this means that for every bug fix we need to create a new installer instead of that users can update the plugin directly from the plugin window.

Does this:
https://twitter.com/juergenefischer/status/1406990156431859716?s=27

mean that we need to rewrite the installer creation process?

https://nelenschuurmans-my.sharepoint.com/:w:/g/personal/jonas_vanschrojenstein_nelen-schuurmans_nl/EeGZMH0BicRPl7UKYWyisrkBGbxZXKL-D4D2jfAssB5AAg?e=9nA08a

Excerpt from the document above:

The current implementation for schematizing breaches is confusing, difficult to explain and difficult to use in practice. Reasons for this is that many steps are needed to create a breach, it is not very visual (not what you see is what you get) and changing unrelated parts of the schematization often required recreating all existing breaches.

This document proposes a new way of schematizing breaches that should solve those problems.

This proposal has been set up with the assumption that no (major) changes to the computational core are required. It does not include 2D/2D breaches.

The schematisation of breaches is related to how 1D/2D connections are schematised in general. This is especially relevant for “double connected”.

User story / requirements

Modellers want to be able to:

• Add breaches by drawing it on the map canvas
• Add breaches automatically at specified intervals along a levee
• Add breaches automatically at specific point locations on a levee
• When adding breaches automatically, specify which breaches and levees should be taken into consideration by the algorithm
• Add breaches in at one side or both sides in case there are levees at both sides of the channel
• Be able to choose where the breach connects to the 2D domain
• See on the map canvas how a breach connects channels to the 2D domain
• See on the map canvas how the schematization of the breach is interpreted when generating the computational grid
• Label breaches with a name or code that stays the same from one revision to the next
• Change other part of the schematization without having to re-create the breaches

[User stories that may require changes to computational core:]

Add a breach over a levee that has a boundary condition at the upstream side instead of a channel

Option 1 System admin installs 3Di Modeller Interface, users install profile on first use

• Installer also creates shortcuts in user profile (move from first install option to second install section), with correct arguments (--profile-folder "C:...\user.name\blablabla")

Option 2 Include option to "install for all users" in installer

• Research options for this in windows installers; would this work correctly with references to profile folders etc.?

Option 3 Ask Wolf how this is done for Nelen & Schuurmans Consultancy

• ...

Option 999: Use 'public' profile on windows, QGIS user profile for each user (not preferred)

Short-term workaround, like option 1: admin installs 3Di MI; copies shortcut to public or shared location, user copies the .lnk file and changes --profile-folder argument to the correct value for that user

After installation, the app is known to Windows as "3DiModellerInterface 3.xx" Please change this to "3Di Modeller Interface 3.xx", so that users can find the app in windows if they type "3Di Modeller Interface" in the search bar

If a user just downloads and runs the modeller interface installer, its python environment contains a (old) version of the threedi-api-client python package. This breaks the 3Di Models & Simulations plugin.

This is not 100% clear to me, but I have the impression that this is due to some configuration in the installer itself (not in one of the plugins). Please remove this python package from the installer.

The 3Di Modeller Interface changes several QGIS settings. Some of these settings are required for correct behaviour of our plugins (e.g. for handling scientific notations of very small floats).

This is currently implemented by installing a pre-configured user profile called 'default'. However, if a user creates a new user profile, these customizations are not applied to that new user profile; the settings for a new user profile are read from (in my case) "C:\Program Files\3DiModellerInterface 3.22\apps\qgis-ltr\resources\qgis_global_settings.ini". This is documented here: https://docs.qgis.org/3.22/en/docs/user_manual/introduction/qgis_configuration.html#deploying-qgis-within-an-organization

I propose to change our implementation in such a way that all the settings we now set in qgis.ini are moved to qgis_global_settings.ini

Suggested solution is to include some QT global settings in the .bat file that start QGIS

@benvanbasten-ns please add details on the solution you had in mind to this ticket

De Installer van de 3Di Modeller Interface zegt dat ie afkomstig is van 'Unknown Publisher'; dit komt niet heel veilig over, dit zou '3Di Water Management' moeten zijn

Het is als je de .exe wilt uitvoeren.

https://xd.adobe.com/view/c3aadbca-cffb-4ea3-47d4-55e2bfad3c3c-b59b/?fullscreen

https://github.com/haubourg/custom-osgeo4w-qgis

De installer voor QGIS 3.28 is deze week gereleased. Deze versie wordt in februari de nieuwe Long Term Release. Ik zou graag een MI installer willen hebben op basis van QGIS 3.28, zodat van nov t/m februari getest kan worden of alles naar behoren werkt.

Deze versie kan dan in maart 2023 gereleased worden.

is it possible to include this plugin in the modeller interface profile?

https://github.com/threedi/beta-plugins/tree/master/import_hydx

@RichardB9
What needs to happen to make that possible?

Because the new MI Installer installs QGIS in quiet mode, users are not shown the relevant license agreements. It would be good to show this.

E.g. the current production version is based on 3.22.7, while the latest LTR is 3.22.12. This way, we miss backported bugfixes that are rolled out after the release of the LTR.