k.ko100v wrote: ↑28 Jul 2022, 09:39
"2.2 These parts should be exported as separate stl files with 1 unit = 1m."
Is this rule still valid? When I export my CAD files with 1 unit = 1m, they are becoming ridiculously small compare to the mandatory parts, when loaded in MFlow. When they are exported with 1 unit = 1mm everything is fine.
The old MAND filed from 2020 are still smaller than the currents, when loaded together in MFlow.
Are you all exporting the CAD files with 1 unit = 1m?
Yes, the rule is valid. It is not one that will easily get you a penalty though.
For this season, I first exported the supplied stl files in this wrong dimension. I assumed everyone tuned their stl import settings and did not want to change it anymore.
samuel_l25 wrote: ↑28 Jul 2022, 22:13
EngJH wrote: ↑28 Jul 2022, 13:14
Hello everyone,
first time for me competing here and looking forward to the first race although I dont expect too much against you all. Nonetheless will be a great learning experience and already had quite some fun with the development of my car for the first race.
samuel_l25 wrote: ↑24 Jul 2022, 12:06
I can 'Build Case' which it does do. When I click 'Run Case' I get that line of text in the command window (although doesn't show in the MFlow.log) then nothing else happens even after waiting 40 minutes.
I have just tried running a 2020 MVRC based car that I made last year and it surprisingly works using MFlow_2207d...
Shark tutorial also works with MFlow_2207d.
Im having a similar (or same) problem as Samuel.
When I try to run the case in MFlow 2207e I get the message:
"MFlow.py:882: DeprecationWarning: QProcess.startDetached(const QString & command) is deprecated"
Maybe you have already solved the problem and can tell me what you did? So I can see whether its for me the same issue.
Thanks in advance!
Not yet, could possibly be either my computers specs or the geometry not being fully closed.
"MFlow.py:882: DeprecationWarning: QProcess.startDetached(const QString & command) is deprecated"
This is just a warning and can be ignored. I will try to deactivate it in the next release.
Why you guys cannot run, is currently beyond me. Please keep these things in mind. MFlow creates a case for the open source CFD solver OpenFOAM. With Mflow you can create the case, it then needs to get run. You can do this manually or with MFlow. The CFD case itself is quite complicated. It creates a mesh, using the stl files. This can take very long, maybe an hour or two. And during some periods, you will not see much happening, depending on your system. You could monitor memory usage, as this step likely will use the most on your computer. If you are out of memory, not much will be happening...
The next major step is solving the CFD case as such. This takes the most time. You simply have to wait. Depending on your computer maybe even a full day. In MFlow there is a setting to specify how many CPU cores can be used.
After that there are a few additional step to help with post-processing. When that is done, you can use MFlow to create a nice report.
Doing it the first time is not super easy and you might have certain expectations on how long everything takes. Even on a good computer, you will be waiting a few hours.
The support forum is still broken, as I did not want to run the major upgrade the page needs to fix it, right before a race, so you will have to wait another few days for that. If you have problems, please make you case, including log files available to me.
