Add flow rate to simulation view

[khani3s]

WIP

Add Flow rate to simulation view

Flow Rate (AKA volumetric flow rate, volume flow rate, rate of fluid flow, volume velocity or volumetric speed) is used defined on 3dp as line width * thickness * feedrate. The unit is mm³/s

Is useful to check if your printing inside your hot end/extruder limits.

This implementation is based on #9289 and does not take into account (I think) material_flow.

TODO

• Define the name of the view (currently is just Flow)
• Add to I18n
• Build
• CI test pass

I need some guide of how to test this on my machine (Ubuntu 18.04.5 LTS).
I tried the "docker way" and after reading all the doc multiple times (cura-build-enviroment, cura-build, cura, wiki) I can't figure out how to build it and generate the AppImage.
I follow the CI build steps and got the same build output but I couldn't find out a way to get the binary for testing on my local machine.
I already invested +8 hours on the "build"

[nallath]

Oh, you don't need to make the actual appimage. I just test Cura when running it from source. In 99% of the cases running it from source is the same as the appimage / binary.

In the few cases that it isn't, we have a automatic build system that spits out nightlies and which gets used & tested by our QA engineers.

[jellespijker]

Hi @khani3s I was wondering if you're still stuck and if that is the case how I could help you. I kinda like what you're doing here, sot it would be great if we could merge it.

[jellespijker]

I think you're almost there. If you implement the following fixes in the code, you should have something working. See the image below.

I would suggest that you name it Flow rate instead of Flow and it might be a good idea to merge master into your own branch again since there were many changes in between your PR and now.

Don't worry about setting up the complete build environment, if it runs from source it will most likely run in our builds as well and we have the automatic tests to catch errors as well.

Btw it looks like something is a bit off with the max flow rate calculation. A flow of 26 mm3/s is very high

[khani3s]

I finally managed to run the code.

https://github.com/Ultimaker/Cura/wiki/Running-Cura-from-Source-on-Ubuntu

python3 cura_app.py
(...)
QQmlApplicationEngine failed to load component
file:///media/felipe/Backup/backup/3dp/cura2/Cura/resources/qml/Cura.qml:388 Type Cura.PrintSetupSelector unavailable
file:///media/felipe/Backup/backup/3dp/cura2/Cura/cura/../resources/qml/PrintSetupSelector/PrintSetupSelector.qml:33 Type PrintSetupSelectorContents unavailable
file:///media/felipe/Backup/backup/3dp/cura2/Cura/cura/../resources/qml/PrintSetupSelector/PrintSetupSelectorContents.qml:74 Type CustomPrintSetup unavailable
file:///media/felipe/Backup/backup/3dp/cura2/Cura/resources/qml/PrintSetupSelector/Custom/CustomPrintSetup.qml:285 Type Cura.SettingView unavailable
file:///media/felipe/Backup/backup/3dp/cura2/Cura/cura/../resources/qml/Settings/SettingView.qml:157 Type SettingVisibilityPresetsMenu unavailable
file:///media/felipe/Backup/backup/3dp/cura2/Cura/resources/qml/Menus/SettingVisibilityPresetsMenu.qml:5 module "QtQuick.Controls" version 2.11 is not installed
(...)

For documentation purposes:

The version of PyQT listed on the wiki was wrong.
I solved the problem by editing requirements.txt and removing pywin32 and installing the dependencies with:

sudo pip3 install -r requirements.txt

[fieldOfView]

What version of PyQt and Qt have you installed?

[fieldOfView]

I think you stumbled across a "typo" or mistake. According to the qtquick documentation, module "QtQuick.Controls" version 2.11 does not exist yet, and the file should actually be using module "QtQuick.Controls" version 2.4. It is interesting though that you are the first to stumble into this as something that stops Cura from loading.

[fieldOfView]

I have created #9799 to fix the version issue.

[khani3s]

I was using the Qt recommended here:

https://github.com/Ultimaker/Cura/wiki/Running-Cura-from-Source-on-Ubuntu

PyQt5==5.10

The requirements.txt version solved the problem:

PyQt5==5.15.2

[khani3s]

Btw it looks like something is a bit off with the max flow rate calculation. A flow of 26 mm3/s is very high

I notice that too. And after debugging I think that is related to the "Fill Gaps lines".
If you set "Fill Gaps Between Walls" to "Nowhere" the flow goes it a normal range.
On another model I found a single point with a high value on the gaps.

[khani3s]

[nallath]

I was using the Qt recommended here:

https://github.com/Ultimaker/Cura/wiki/Running-Cura-from-Source-on-Ubuntu

PyQt5==5.10

The requirements.txt version solved the problem:

PyQt5==5.15.2

Whoops. I've updated the documentation.

[nallath]

I've managed to get a bit of a weird result

My guess is that it's caused by the min & the max being the same.

[khani3s]

@nallath could you send me that project?

[nallath]

UMS3_tetrahedron.zip

The issue only occurs if you only show the helpers.

[Ghostkeeper]

Oh, I think that visualisation bug is because of this recently merged pull request: #9498

[nallath]

The fix suggested by @Ghostkeeper fixes it, so i've merged this!

Github is however not quite understanding that :S ( But fear not; it is in the next release!)